From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 00/11] Make all concurrent queue flag manipulations safe
Date: Thu, 8 Mar 2018 14:15:06 -0700 [thread overview]
Message-ID: <20180308211504.GB3932@kernel.dk> (raw)
In-Reply-To: <20180308011012.31522-1-bart.vanassche@wdc.com>
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
prev parent reply other threads:[~2018-03-08 21:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 1:10 [PATCH v2 00/11] Make all concurrent queue flag manipulations safe Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 01/11] block: Reorder the queue flag manipulation function definitions Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 02/11] block: Use the queue_flag_*() functions instead of open-coding these Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 03/11] block: Introduce blk_queue_flag_{set,clear,test_and_{set,clear}}() Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 04/11] block: Protect queue flag changes with the queue lock Bart Van Assche
2018-03-08 9:12 ` Johannes Thumshirn
2018-03-08 1:10 ` [PATCH v2 05/11] mtip32xx: Use the blk_queue_flag_*() functions Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 06/11] bcache: Use the blk_queue_flag_{set,clear}() functions Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 07/11] iscsi: Use blk_queue_flag_set() Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 08/11] target/tcm_loop: " Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 09/11] block: Use blk_queue_flag_*() in drivers instead of queue_flag_*() Bart Van Assche
2018-03-08 9:12 ` Johannes Thumshirn
2018-03-08 1:10 ` [PATCH v2 10/11] block: Complain if queue_flag_(set|clear)_unlocked() is abused Bart Van Assche
2018-03-08 1:10 ` [PATCH v2 11/11] block: Move the queue_flag_*() functions from a public into a private header file Bart Van Assche
2018-03-08 21:15 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180308211504.GB3932@kernel.dk \
--to=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.