{"push_id":943570804,"size":5,"distinct_size":5,"ref":"refs/heads/v1.2.18-maint","head":"74909e9648366f9fc6cd7a29a71791d29f04ff7f","before":"d5ef3cbb2cdc3dd497b00228512d7936c34a9cc3","commits":[{"sha":"39953c18d134b6be629e8aa94a6fcedc6440fcb7","author":{"email":"7cd45ff6ad1fb7cf556a02797d774247851499f8@redhat.com","name":"Cole Robinson"},"message":"build: predictably generate systemtap tapsets (bz 1173641)\n\nThe generated output is dependent on perl hashtable ordering, which\ngives different results for i686 and x86_64. Fix this by sorting\nthe hash keys before iterating over them\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1173641\n(cherry picked from commit a1edb05c6028470aa24b74aa0f8d5fb5a181128a)","distinct":true,"url":"https://api.github.com/repos/libvirt/libvirt/commits/39953c18d134b6be629e8aa94a6fcedc6440fcb7"},{"sha":"4a4c73d21760eb15aa966f982cec8157afaadfca","author":{"email":"7cd45ff6ad1fb7cf556a02797d774247851499f8@redhat.com","name":"Cole Robinson"},"message":"rpc: socket: Minor cleanups\n\n- Add some debugging\n- Make the loop dependent only on retries\n- Make it explicit that connect(2) success exits the loop\n- Invert the error checking logic\n\n(cherry picked from commit f102c7146ed7f6e04af0ad3bce302476239f2502)","distinct":true,"url":"https://api.github.com/repos/libvirt/libvirt/commits/4a4c73d21760eb15aa966f982cec8157afaadfca"},{"sha":"2e4d173b49949615c9820e495ae16352ac55c585","author":{"email":"7cd45ff6ad1fb7cf556a02797d774247851499f8@redhat.com","name":"Cole Robinson"},"message":"rpc: socket: Explicitly error if we exceed retry count\n\nWhen we autolaunch libvirtd for session URIs, we spin in a retry\nloop waiting for the daemon to start and the connect(2) to succeed.\n\nHowever if we exceed the retry count, we don't explicitly raise an\nerror, which can yield a slew of different error messages elsewhere\nin the code.\n\nExplicitly raise the last connect(2) failure if we run out of retries.\n\n(cherry picked from commit 8da02d528068942303923fc4f935e77cccac9c7c)","distinct":true,"url":"https://api.github.com/repos/libvirt/libvirt/commits/2e4d173b49949615c9820e495ae16352ac55c585"},{"sha":"40df40f35a2c9a63cb42353824691f11eed41254","author":{"email":"7cd45ff6ad1fb7cf556a02797d774247851499f8@redhat.com","name":"Cole Robinson"},"message":"rpc: socket: Don't repeatedly attempt to launch daemon\n\nOn every socket connect(2) attempt we were re-launching session\nlibvirtd, up to 100 times in 5 seconds.\n\nThis understandably caused some weird load races and intermittent\nqemu:///session startup failures\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1271183\n(cherry picked from commit 2eb7a975756d05a5b54ab4acf60083beb6161ac6)","distinct":true,"url":"https://api.github.com/repos/libvirt/libvirt/commits/40df40f35a2c9a63cb42353824691f11eed41254"},{"sha":"74909e9648366f9fc6cd7a29a71791d29f04ff7f","author":{"email":"62bdf77dc47919a4d59a91822129d14633cfca81@redhat.com","name":"Jiri Denemark"},"message":"security: Do not restore kernel and initrd labels\n\nKernel/initrd files are essentially read-only shareable images and thus\nshould be handled in the same way. We already use the appropriate label\nfor kernel/initrd files when starting a domain, but when a domain gets\ndestroyed we would remove the labels which would make other running\ndomains using the same files very unhappy.\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=921135\n\nSigned-off-by: Jiri Denemark <jdenemar@redhat.com>\n(cherry picked from commit 68acc701bd449481e3206723c25b18fcd3d261b7)","distinct":true,"url":"https://api.github.com/repos/libvirt/libvirt/commits/74909e9648366f9fc6cd7a29a71791d29f04ff7f"}]}