Linux block layer
 help / color / mirror / Atom feed
From: Yu Kuai <yukuai1@huaweicloud.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
	Yu Kuai <yukuai1@huaweicloud.com>,
	ming.lei@redhat.com, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	yi.zhang@huawei.com, yangerkun@huawei.com,
	johnny.chenyi@huawei.com, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH for-6.18/block 08/10] blk-mq: fix potential deadlock while nr_requests grown
Date: Tue, 9 Sep 2025 15:37:50 +0800	[thread overview]
Message-ID: <628d9525-dcef-2aaa-3434-64c7cdc0fb23@huaweicloud.com> (raw)
In-Reply-To: <484c552e-462f-488f-90bf-18fe5042f1bb@linux.ibm.com>

Hi,

在 2025/09/09 14:39, Nilay Shroff 写道:
> 
> 
> On 9/8/25 11:45 AM, Yu Kuai wrote:
>> From: Yu Kuai <yukuai3@huawei.com>
>>
>> Allocate and free sched_tags while queue is freezed can deadlock[1],
>> this is a long term problem, hence allocate memory before freezing
>> queue and free memory after queue is unfreezed.
>>
>> [1] https://lore.kernel.org/all/0659ea8d-a463-47c8-9180-43c719e106eb@linux.ibm.com/
>> Fixes: e3a2b3f931f5 ("blk-mq: allow changing of queue depth through sysfs")
>>
>> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
> [...]
> [...]
> 
>> diff --git a/block/blk-sysfs.c b/block/blk-sysfs.c
>> index 7ea15bf68b4b..a0a7ebad378f 100644
>> --- a/block/blk-sysfs.c
>> +++ b/block/blk-sysfs.c
>> @@ -64,11 +64,12 @@ static ssize_t queue_requests_show(struct gendisk *disk, char *page)
>>   static ssize_t
>>   queue_requests_store(struct gendisk *disk, const char *page, size_t count)
>>   {
>> -	unsigned long nr;
>> -	int ret, err;
>> -	unsigned int memflags;
>>   	struct request_queue *q = disk->queue;
>>   	struct blk_mq_tag_set *set = q->tag_set;
>> +	struct elevator_tags *et = NULL;
>> +	unsigned int memflags;
>> +	unsigned long nr;
>> +	int ret;
>>   
>>   	ret = queue_var_store(&nr, page, count);
>>   	if (ret < 0)
>> @@ -90,16 +91,24 @@ queue_requests_store(struct gendisk *disk, const char *page, size_t count)
>>   		goto unlock;
>>   	}
>>   
>> +	if (q->elevator && nr > q->elevator->et->nr_requests) {
>> +		/* allocate memory before freezing queue to prevent deadlock */
>> +		et = blk_mq_alloc_sched_tags(set, q->nr_hw_queues, nr);
>> +		if (!et) {
>> +			ret = -ENOMEM;
>> +			goto unlock;
>> +		}
>> +	}
>> +
> I think we should add a comment above explaining why is it safe
> to access q->elevator without holding ->elevator_lock.
> 

I already access q->elevator to check input nr from patch 4, and that's
why I add comments to explain switching elevator is serialized, is this
enough?

Thanks,
Kuai

> Thanks,
> --Nilay
> .
> 


  reply	other threads:[~2025-09-09  7:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08  6:15 [PATCH for-6.18/block 00/10] cleanup and fixes for updating nr_requests Yu Kuai
2025-09-08  6:15 ` [PATCH for-6.18/block 01/10] blk-mq: remove useless checking in queue_requests_store() Yu Kuai
2025-09-09 11:34   ` Nilay Shroff
2025-09-08  6:15 ` [PATCH for-6.18/block 02/10] blk-mq: remove useless checkings in blk_mq_update_nr_requests() Yu Kuai
2025-09-09 11:35   ` Nilay Shroff
2025-09-08  6:15 ` [PATCH for-6.18/block 03/10] blk-mq: check invalid nr_requests in queue_requests_store() Yu Kuai
2025-09-09 11:36   ` Nilay Shroff
2025-09-08  6:15 ` [PATCH for-6.18/block 04/10] blk-mq: convert to serialize updating nr_requests with update_nr_hwq_lock Yu Kuai
2025-09-09  6:29   ` Nilay Shroff
2025-09-09  6:38     ` Yu Kuai
2025-09-09  6:52       ` Nilay Shroff
2025-09-09  7:16         ` Yu Kuai
2025-09-09  9:26           ` Nilay Shroff
2025-09-09  9:36             ` Yu Kuai
2025-09-09 10:11               ` Nilay Shroff
2025-09-09 10:42                 ` Yu Kuai
2025-09-09 11:32                   ` Nilay Shroff
2025-09-09 11:40   ` Nilay Shroff
2025-09-08  6:15 ` [PATCH for-6.18/block 05/10] blk-mq: cleanup shared tags case in blk_mq_update_nr_requests() Yu Kuai
2025-09-09 11:58   ` Nilay Shroff
2025-09-08  6:15 ` [PATCH for-6.18/block 06/10] blk-mq: split bitmap grow and resize " Yu Kuai
2025-09-09 12:18   ` Nilay Shroff
2025-09-09 16:39     ` Yu Kuai
2025-09-10  6:30       ` Nilay Shroff
2025-09-10  6:42         ` Yu Kuai
2025-09-08  6:15 ` [PATCH for-6.18/block 07/10] blk-mq-sched: add new parameter nr_requests in blk_mq_alloc_sched_tags() Yu Kuai
2025-09-09 12:19   ` Nilay Shroff
2025-09-08  6:15 ` [PATCH for-6.18/block 08/10] blk-mq: fix potential deadlock while nr_requests grown Yu Kuai
2025-09-09  6:39   ` Nilay Shroff
2025-09-09  7:37     ` Yu Kuai [this message]
2025-09-09  9:36       ` Nilay Shroff
2025-09-09 12:21   ` Nilay Shroff
2025-09-10  7:46   ` Yu Kuai
2025-09-08  6:15 ` [PATCH for-6.18/block 09/10] blk-mq: remove blk_mq_tag_update_depth() Yu Kuai
2025-09-09 12:35   ` Nilay Shroff
2025-09-08  6:15 ` [PATCH for-6.18/block 10/10] blk-mq: fix stale nr_requests documentation Yu Kuai
2025-09-09 12:35   ` Nilay Shroff

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=628d9525-dcef-2aaa-3434-64c7cdc0fb23@huaweicloud.com \
    --to=yukuai1@huaweicloud.com \
    --cc=axboe@kernel.dk \
    --cc=johnny.chenyi@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=nilay@linux.ibm.com \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.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