search for: l296

...t, so I don't understand why any operation on BPF programs is not permitted. I've dug into libvirt's code a bit to see what is throwing this error and it boils down to <https://github.com/libvirt/libvirt/blob/7d608469621a3fda72dff2a89308e68cc9fb4c9a/src/util/vircgroupv2devices.c#L292-L296> and <https://github.com/libvirt/libvirt/blob/02bf7cc68bfc76242f02d23e73cad36618f3f790/src/util/virbpf.c#L54> but I have no clue what that syscall is doing, so that's where my debugging capability basically ends. Maybe this is something as simple as setting the right ACL somewhere. I...

...other cases we've had to change sscanf uses to strto* etc which is much more difficult to use correctly. Just look at how much code is required to wrap strto* functions to use them safely: https://github.com/libguestfs/nbdkit/blob/b23f4f53cf71326f1dba481f64f7f182c20fa3dc/server/public.c#L113-L296 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests....

It has long been known that the C specification of *scanf() leaves behavior undefined for things like int i; sscanf("9999999999999999", "%i", &i); C11 7.21.6.2 P12 "Matches an optionally signed integer, whose format is the same as expected for the subject sequence of the strtol function with the value 0 for the base argument." C11 7.21.6.2 P10 "If this

...; > operation on BPF programs is not permitted. I've dug into libvirt's code > > > a bit to see what is throwing this error and it boils down to > > > <https://github.com/libvirt/libvirt/blob/7d608469621a3fda72dff2a89308e68cc9fb4c9a/src/util/vircgroupv2devices.c#L292-L296> > > > and > > > <https://github.com/libvirt/libvirt/blob/02bf7cc68bfc76242f02d23e73cad36618f3f790/src/util/virbpf.c#L54> > > > but I have no clue what that syscall is doing, so that's where my > > > debugging capability basically ends. > > &gt...

...filmaj/207ab3c09f5b881d83b1 > [2] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L226-L253 > [3] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L257-L266 > [4] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L296 > [5] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L302 > [6] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L685 > [7] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L752-L799 > [8] > https://gist....

...[1] https://gist.github.com/filmaj/207ab3c09f5b881d83b1 [2] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L226-L253 [3] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L257-L266 [4] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L296 [5] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L302 [6] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L685 [7] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L752-L799 [8] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#f...

Further followups! We are correlating DEBUG-level output from libvirt with the libvirt 1.2.2 code to try to figure out what libvirt is doing under the hood. Even though we have the log level set to 1 (info) in our libvirtd.conf, we are not seeing the VIR_DEBUG() [1] statements being printed out. There are tons of other presumably-debug lines of output showing up in our log. We are sort of

...ration on BPF programs is not permitted. I've dug into libvirt's code > > > > a bit to see what is throwing this error and it boils down to > > > > <https://github.com/libvirt/libvirt/blob/7d608469621a3fda72dff2a89308e68cc9fb4c9a/src/util/vircgroupv2devices.c#L292-L296> > > > > and > > > > <https://github.com/libvirt/libvirt/blob/02bf7cc68bfc76242f02d23e73cad36618f3f790/src/util/virbpf.c#L54> > > > > but I have no clue what that syscall is doing, so that's where my > > > > debugging capability basically...