From: Zizhi Wo <wozizhi@huaweicloud.com>
To: Bart Van Assche <bvanassche@acm.org>,
Zizhi Wo <wozizhi@huaweicloud.com>,
axboe@kernel.dk, dlemoal@kernel.org, nilay@linux.ibm.com,
kch@nvidia.com, johannes.thumshirn@wdc.com, kbusch@kernel.org,
linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yangerkun@huawei.com,
chengzhihao1@huawei.com
Subject: Re: [PATCH V5 9/9] null_blk: serialize configfs attribute shows with the file-scope lock
Date: Sat, 25 Jul 2026 09:27:03 +0800 [thread overview]
Message-ID: <26340aba-b93c-47d2-b648-2cf732e884d5@huaweicloud.com> (raw)
In-Reply-To: <30c062e3-1f8b-43a9-8c85-4bc86cd74336@acm.org>
在 2026/7/25 5:16, Bart Van Assche 写道:
>
> On 7/13/26 9:18 PM, Zizhi Wo wrote:
>> diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/
>> main.c
>> index 67cd32d28887..c8487a630e1a 100644
>> --- a/drivers/block/null_blk/main.c
>> +++ b/drivers/block/null_blk/main.c
>> @@ -345,8 +345,14 @@ static ssize_t nullb_device_bool_attr_store(bool
>> *val, const char *page,
>> static ssize_t \
>> nullb_device_##NAME##_show(struct config_item *item, char *page) \
>> { \
>> - return nullb_device_##TYPE##_attr_show( \
>> + ssize_t ret; \
>> + \
>> + mutex_lock(&lock); \
>> + ret = nullb_device_##TYPE##_attr_show( \
>> to_nullb_device(item)->NAME, page); \
>> + mutex_unlock(&lock); \
>> + \
>> + return ret; \
>> } \
>> static ssize_t \
>> nullb_device_##NAME##_store(struct config_item *item, const char
>> *page, \
>> @@ -479,7 +485,13 @@ NULLB_DEVICE_ATTR(badblocks_partial_io, bool, NULL);
>> static ssize_t nullb_device_power_show(struct config_item *item,
>> char *page)
>> {
>> - return nullb_device_bool_attr_show(to_nullb_device(item)->power,
>> page);
>> + ssize_t ret;
>> +
>> + mutex_lock(&lock);
>> + ret = nullb_device_bool_attr_show(to_nullb_device(item)->power,
>> page);
>> + mutex_unlock(&lock);
>> +
>> + return ret;
>> }
>
> The above changes would be much more elegant if guard()() would be used
> instead of explicit mutex_lock() and mutex_unlock() calls.
>
> Thanks,
>
> Bart.
Thanks Bart. Will switch to using guard() in the next version :)
Thanks,
Zizhi Wo
next prev parent reply other threads:[~2026-07-25 1:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 4:17 [PATCH V5 0/9] null_blk: fix init/exit races and memleaks Zizhi Wo
2026-07-14 4:17 ` [PATCH V5 1/9] null_blk: use DEFINE_MUTEX for the file-scope mutex Zizhi Wo
2026-07-14 4:17 ` [PATCH V5 2/9] null_blk: register configfs subsystem after creating default devices Zizhi Wo
2026-07-14 4:17 ` [PATCH V5 3/9] null_blk: move unregister_blkdev() after destroying dev in null_exit() Zizhi Wo
2026-07-14 4:18 ` [PATCH V5 4/9] null_blk: free global tag_set on init error path Zizhi Wo
2026-07-14 4:18 ` [PATCH V5 5/9] null_blk: free zones array on device power-off Zizhi Wo
2026-07-15 14:14 ` Nilay Shroff
2026-07-24 21:08 ` Bart Van Assche
2026-07-14 4:18 ` [PATCH V5 6/9] null_blk: clean up null_del_dev() to use cached dev pointer Zizhi Wo
2026-07-24 21:08 ` Bart Van Assche
2026-07-14 4:18 ` [PATCH V5 7/9] null_blk: reject per-device queue resize for shared tag set Zizhi Wo
2026-07-15 13:42 ` Nilay Shroff
2026-07-24 21:09 ` Bart Van Assche
2026-07-14 4:18 ` [PATCH V5 8/9] null_blk: serialize configfs attribute stores with device setup Zizhi Wo
2026-07-24 21:13 ` Bart Van Assche
2026-07-25 1:22 ` Zizhi Wo
2026-07-14 4:18 ` [PATCH V5 9/9] null_blk: serialize configfs attribute shows with the file-scope lock Zizhi Wo
2026-07-24 21:16 ` Bart Van Assche
2026-07-25 1:27 ` Zizhi Wo [this message]
2026-07-24 1:18 ` [PATCH V5 0/9] null_blk: fix init/exit races and memleaks Zizhi Wo
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=26340aba-b93c-47d2-b648-2cf732e884d5@huaweicloud.com \
--to=wozizhi@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chengzhihao1@huawei.com \
--cc=dlemoal@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nilay@linux.ibm.com \
--cc=yangerkun@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
all inboxes | Powered by JetHome®