From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-block@vger.kernel.org
Cc: hch@lst.de, ming.lei@redhat.com, dlemoal@kernel.org,
hare@suse.de, axboe@kernel.dk, lkp@intel.com, gjoyce@ibm.com
Subject: [PATCHv6 5/7] block: protect nr_requests update using q->elevator_lock
Date: Tue, 4 Mar 2025 15:52:34 +0530 [thread overview]
Message-ID: <20250304102551.2533767-6-nilay@linux.ibm.com> (raw)
In-Reply-To: <20250304102551.2533767-1-nilay@linux.ibm.com>
The sysfs attribute nr_requests could be simultaneously updated from
elevator switch/update or nr_hw_queue update code path. The update to
nr_requests for each of those code paths runs holding q->elevator_lock.
So we should protect access to sysfs attribute nr_requests using q->
elevator_lock instead of q->sysfs_lock.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
---
block/blk-sysfs.c | 10 +++++-----
include/linux/blkdev.h | 10 ++++++----
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/block/blk-sysfs.c b/block/blk-sysfs.c
index 1562e22877e1..f1fa57de29ed 100644
--- a/block/blk-sysfs.c
+++ b/block/blk-sysfs.c
@@ -55,9 +55,9 @@ static ssize_t queue_requests_show(struct gendisk *disk, char *page)
{
ssize_t ret;
- mutex_lock(&disk->queue->sysfs_lock);
+ mutex_lock(&disk->queue->elevator_lock);
ret = queue_var_show(disk->queue->nr_requests, page);
- mutex_unlock(&disk->queue->sysfs_lock);
+ mutex_unlock(&disk->queue->elevator_lock);
return ret;
}
@@ -76,16 +76,16 @@ queue_requests_store(struct gendisk *disk, const char *page, size_t count)
if (ret < 0)
return ret;
- mutex_lock(&q->sysfs_lock);
memflags = blk_mq_freeze_queue(q);
+ mutex_lock(&q->elevator_lock);
if (nr < BLKDEV_MIN_RQ)
nr = BLKDEV_MIN_RQ;
err = blk_mq_update_nr_requests(disk->queue, nr);
if (err)
ret = err;
+ mutex_unlock(&q->elevator_lock);
blk_mq_unfreeze_queue(q, memflags);
- mutex_unlock(&q->sysfs_lock);
return ret;
}
@@ -692,7 +692,6 @@ static struct attribute *blk_mq_queue_attrs[] = {
/*
* Attributes which are protected with q->sysfs_lock.
*/
- &queue_requests_entry.attr,
#ifdef CONFIG_BLK_WBT
&queue_wb_lat_entry.attr,
#endif
@@ -701,6 +700,7 @@ static struct attribute *blk_mq_queue_attrs[] = {
* q->sysfs_lock.
*/
&elv_iosched_entry.attr,
+ &queue_requests_entry.attr,
/*
* Attributes which don't require locking.
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 079bc2d00e22..ed8d139a4f5d 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -563,10 +563,12 @@ struct request_queue {
struct list_head flush_list;
/*
- * Protects against I/O scheduler switching, specifically when
- * updating q->elevator. To ensure proper locking order during
- * an elevator update, first freeze the queue, then acquire
- * ->elevator_lock.
+ * Protects against I/O scheduler switching, particularly when
+ * updating q->elevator. Since the elevator update code path may
+ * also modify q->nr_requests, this lock also protects the sysfs
+ * attribute nr_requests.
+ * To ensure proper locking order during an elevator update, first
+ * freeze the queue, then acquire ->elevator_lock.
*/
struct mutex elevator_lock;
--
2.47.1
next prev parent reply other threads:[~2025-03-04 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:22 [PATCHv6 0/7] block: fix lock order and remove redundant locking Nilay Shroff
2025-03-04 10:22 ` [PATCHv6 1/7] block: acquire q->limits_lock while reading sysfs attributes Nilay Shroff
2025-03-04 10:22 ` [PATCHv6 2/7] block: move q->sysfs_lock and queue-freeze under show/store method Nilay Shroff
2025-03-04 10:22 ` [PATCHv6 3/7] block: remove q->sysfs_lock for attributes which don't need it Nilay Shroff
2025-03-04 10:22 ` [PATCHv6 4/7] block: introduce a dedicated lock for protecting queue elevator updates Nilay Shroff
2025-03-04 10:22 ` Nilay Shroff [this message]
2025-03-04 10:22 ` [PATCHv6 6/7] block: protect wbt_lat_usec using q->elevator_lock Nilay Shroff
2025-03-17 13:40 ` kernel test robot
2025-03-18 13:43 ` Nilay Shroff
2025-03-25 7:08 ` Oliver Sang
2025-03-04 10:22 ` [PATCHv6 7/7] block: protect read_ahead_kb using q->limits_lock Nilay Shroff
2025-03-10 13:50 ` [PATCHv6 0/7] block: fix lock order and remove redundant locking Jens Axboe
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=20250304102551.2533767-6-nilay@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=gjoyce@ibm.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ming.lei@redhat.com \
/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