{"push_id":779270887,"size":3,"distinct_size":3,"ref":"refs/heads/v1.2.19-maint","head":"e0025d2967bbe3f283937216c9e2c12b6e9d1010","before":"66c5f02b961ee4b47d56b0c7dcb09a31f2c738f3","commits":[{"sha":"3468542f06f6f5dc94defa1603c6a6adea3e2da8","author":{"email":"87558058f6f829e5ec976c8ef960720af4ff9c7d@redhat.com","name":"John Ferlan"},"message":"virfile: Introduce virFileUnlink\n\nIn an NFS root-squashed environment the 'vol-delete' command will fail to\n'unlink' the target volume since it was created under a different uid:gid.\n\nThis code continues the concepts introduced in virFileOpenForked and\nvirDirCreate[NoFork] with respect to running the unlink command under\nthe uid/gid of the child. Unlike the other two, don't retry on EACCES\n(that's why we're here doing this now).\n\n(cherry picked from commit 35847860f65f92e444db9730e00cdaef45198e0c)","distinct":true,"url":"https://api.github.com/repos/libvirt/libvirt/commits/3468542f06f6f5dc94defa1603c6a6adea3e2da8"},{"sha":"8b1d84e640f1a6e6ebb47caf23a664e2f651b32d","author":{"email":"87558058f6f829e5ec976c8ef960720af4ff9c7d@redhat.com","name":"John Ferlan"},"message":"storage: Handle failure from refreshVol\n\nCommit id '155ca616' added the 'refreshVol' API. In an NFS root-squash\nenvironment it was possible that if the just created volume from XML wasn't\nproperly created with the right uid/gid and/or mode, then the followup\nrefreshVol will fail to open the volume in order to get the allocation/\ncapacity values. This would leave the volume still on the server and\ncause a libvirtd crash because 'voldef' would be in the pool list, but\nthe cleanup code would free it.\n\n(cherry picked from commit db9277a39bc364806e8d3e08a08fc128d59b7094)","distinct":true,"url":"https://api.github.com/repos/libvirt/libvirt/commits/8b1d84e640f1a6e6ebb47caf23a664e2f651b32d"},{"sha":"e0025d2967bbe3f283937216c9e2c12b6e9d1010","author":{"email":"87558058f6f829e5ec976c8ef960720af4ff9c7d@redhat.com","name":"John Ferlan"},"message":"storage: Correct the 'mode' check\n\nCommit id '7c2d65dde2' changed the default value of mode to be -1 if not\nsupplied in the XML, which should cause creation of the volume using the\ndefault mode of VIR_STORAGE_DEFAULT_VOL_PERM_MODE; however, the check\nmade was whether mode was '0' or not to use default or provided value.\n\nThis patch fixes the issue to check if the 'mode' was provided in the XML\nand use that value.\n\n(cherry picked from commit 691dd388aee99f8b06177540303b690586d5f5b3)","distinct":true,"url":"https://api.github.com/repos/libvirt/libvirt/commits/e0025d2967bbe3f283937216c9e2c12b6e9d1010"}]}