From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v3 0/3] blk-mq: Fix a race between iterating over requests and freeing requests
Date: Thu, 25 Mar 2021 19:29:16 -0700 [thread overview]
Message-ID: <20210326022919.19638-1-bvanassche@acm.org> (raw)
Hi Jens,
This patch series fixes the race between iterating over requests and
freeing requests that has been reported by multiple different users over
the past two years. Please consider this patch series for kernel v5.13.
Thank you,
Bart.
Changes compared to v2:
- Converted the single v2 patch into a series of three patches.
- Switched from SRCU to a combination of RCU and semaphores.
Changes compared to v1:
- Reformatted patch description.
- Added Tested-by/Reviewed-by tags.
- Changed srcu_barrier() calls into synchronize_srcu() calls.
Bart Van Assche (3):
blk-mq: Move the elevator_exit() definition
blk-mq: Introduce atomic variants of the tag iteration functions
blk-mq: Fix races between iterating over requests and freeing requests
block/blk-core.c | 34 ++++++++++++++-
block/blk-mq-tag.c | 87 ++++++++++++++++++++++++++++++++++-----
block/blk-mq-tag.h | 8 ++--
block/blk-mq.c | 31 ++++++++++----
block/blk-mq.h | 1 +
block/blk.h | 11 +----
block/elevator.c | 9 ++++
drivers/scsi/hosts.c | 16 +++----
drivers/scsi/ufs/ufshcd.c | 4 +-
include/linux/blk-mq.h | 2 +
10 files changed, 160 insertions(+), 43 deletions(-)
next reply other threads:[~2021-03-26 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 2:29 Bart Van Assche [this message]
2021-03-26 2:29 ` [PATCH v3 1/3] blk-mq: Move the elevator_exit() definition Bart Van Assche
2021-03-26 2:29 ` [PATCH v3 2/3] blk-mq: Introduce atomic variants of the tag iteration functions Bart Van Assche
2021-03-26 2:29 ` [PATCH v3 3/3] blk-mq: Fix a race between iterating over requests and freeing requests Bart Van Assche
2021-03-26 8:44 ` Shinichiro Kawasaki
2021-03-29 1:33 ` Bart Van Assche
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=20210326022919.19638-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).