On Wed, Mar 07 2018, Bart Van Assche wrote:
> Hello Jens,
> 
> As you probably know there is considerable confusion in the block
> layer core and in block drivers about how to protect queue flag
> changes against concurrent modifications. Some code protects these
> changes with the queue lock, other code uses atomic operations and
> some code does not protect queue flag changes against concurrent
> changes at all. Hence this patch series that protects all queue flag
> changes consistently with the queue lock and that removes functions
> that are not safe in a concurrent context from the public block layer
> header files.
> 
> Please consider these patches for kernel v4.17.
> 
> Note: it may be a good idea to postpone patch 11 until after the
> kernel v4.17 merge window to avoid merge conflicts.

Applied for 4.17. Not too worried about a conflict with that patch, so
applied 11/11 as well.

-- 
Jens Axboe

Reply via email to