Obviously NACK to applying this PULL given the patchew reported mess up I did with tests. Not sure why patchew never gave any complaint when the original patch was posted & reviewed :-(
On Wed, Mar 20, 2019 at 05:41:47PM +0000, Daniel P. Berrangé wrote: > The following changes since commit 62a172e6a77d9072bb1a18f295ce0fcf4b90a4f2: > > Update version for v4.0.0-rc0 release (2019-03-19 17:17:22 +0000) > > are available in the Git repository at: > > https://github.com/berrange/qemu tags/filemon-next-pull-request > > for you to fetch changes up to 9c8cc692ccda6912e46a4b13c4bbcd42df3e8673: > > filemon: fix watch IDs to avoid potential wraparound issues (2019-03-20 > 17:03:29 +0000) > > ---------------------------------------------------------------- > Fix watch uniqueness and protect against guest triggered > integer wraparound clashes in watches. > > ---------------------------------------------------------------- > > Daniel P. Berrangé (3): > tests: refactor file monitor test to make it more understandable > filemon: ensure watch IDs are unique to QFileMonitor scope > filemon: fix watch IDs to avoid potential wraparound issues > > authz/listfile.c | 2 +- > hw/usb/dev-mtp.c | 10 +- > include/authz/listfile.h | 2 +- > include/qemu/filemonitor.h | 16 +- > tests/test-util-filemonitor.c | 626 +++++++++++++++++----------------- > util/filemonitor-inotify.c | 26 +- > util/filemonitor-stub.c | 4 +- > util/trace-events | 6 +- > 8 files changed, 337 insertions(+), 355 deletions(-) > > -- > 2.20.1 > Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
