Re: [PATCH 13/13] iotests/298: cover the preallocation races

[Kevin Wolf <kwolf@redhat.com>]

Am 30.09.2026 um 18:49 hat Denis V. Lunev geschrieben:
> From: Denis V. Lunev <den@openvz.org>
> 
> Three cases the filter has to get right, all deterministic: a write the
> preallocation cannot reach goes through without waiting for it, a write
> into the range it covers does not, and a write zeroes over data written
> inside that range is not skipped as already zero.
> 
> The second one cannot wait for the write to finish, because that is
> what it is checking does not happen, and the data survives either way:
> a preallocation that finds the write still in flight gives up. It asks
> whether the write got past the filter at all instead, by leaving a
> breakpoint below it.
> 
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Kevin Wolf <kwolf@redhat.com>
> CC: Hanna Reitz <hreitz@redhat.com>
> CC: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> CC: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>

What does launching the requests in different iothreads contribute here?
If it's completely deterministic and every request is suspended when
another one is active, shouldn't a single-threaded test trigger the same
cases?

I'm not asking you to change the test code, but I'd like to have the
commit message tell what difference the iothreads make here.

Kevin