Am 10.03.2021 um 16:51 hat Peter Maydell geschrieben: > On Fri, 19 Feb 2021 at 22:38, Peter Maydell <peter.mayd...@linaro.org> wrote: > > > > On Mon, 15 Feb 2021 at 10:41, Kevin Wolf <kw...@redhat.com> wrote: > > > > > > Am 07.12.2020 um 18:20 hat Stefan Hajnoczi geschrieben: > > > > v2: > > > > * Add abrt handler that terminates qemu-storage-daemon to > > > > vhost-user-blk-test. No more orphaned processes on test failure. > > > > [Peter] > > > > * Fix sector number calculation in vhost-user-blk-server.c > > > > * Introduce VIRTIO_BLK_SECTOR_BITS/SIZE to make code clearer [Max] > > > > * Fix vhost-user-blk-server.c blk_size double byteswap > > > > * Fix vhost-user-blk blkcfg->num_queues endianness [Peter] > > > > * Squashed cleanups into Coiby vhost-user-blk-test commit so the code > > > > is > > > > easier to review > > > > > > > > The vhost-user-blk server test was already in Michael Tsirkin's recent > > > > vhost > > > > pull request, but was dropped because it exposed vhost-user regressions > > > > (b7c1bd9d7848 and the Based-on tag below). Now that the vhost-user > > > > regressions > > > > are fixed we can re-introduce the test case. > > > > > > > > This series adds missing input validation that led to a Coverity > > > > report. The > > > > virtio-blk read, write, discard, and write zeroes commands need to check > > > > sector/byte ranges and other inputs. This solves the issue Peter > > > > Maydell raised > > > > in "[PATCH for-5.2] block/export/vhost-user-blk-server.c: Avoid > > > > potential > > > > integer overflow". > > > > > > > > Merging just the input validation patches would be possible too, but I > > > > prefer > > > > to merge the corresponding tests so the code is exercised by the CI. > > > > > > Is this series still open? I don't see it in master. > > > > The Coverity issue is still unfixed, at any rate... > > Ping^2 ! I'd like to get us down to no outstanding Coverity issues for the > 6.0 release, and this (CID 1435956) is one of the handful still unfixed.
You pulled a newer version of this series (minus the tests that caused CI failures on some older OSes) earlier today, so I assume this is fixed now. Kevin
