From: Zizhi Wo <wozizhi@huaweicloud.com>
To: 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,
bvanassche@acm.org, linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yangerkun@huawei.com,
chengzhihao1@huawei.com
Subject: Re: [PATCH V5 0/9] null_blk: fix init/exit races and memleaks
Date: Fri, 24 Jul 2026 09:18:07 +0800 [thread overview]
Message-ID: <1d06cc3c-df97-46a3-a0fe-9e46ce6a813e@huaweicloud.com> (raw)
In-Reply-To: <20260714041805.1088702-1-wozizhi@huaweicloud.com>
friendly ping...
在 2026/7/14 12:17, Zizhi Wo 写道:
> From: Zizhi Wo <wozizhi@huawei.com>
>
> This series fixes several issues in null_blk around lock initialization,
> memory leaks, concurrent configfs access, and module init/exit.
>
> No functional changes to patches 1-4, 6, and 8-9.
>
> See the individual patch descriptions for details.
>
> Changes since v4:
> - Modified patch 5 to fix the check-and-deref race on dev->zones in
> zone_cond_store().
> - Simplified the fix in patch 7.
> https://lore.kernel.org/all/20260709100452.3520482-1-wozizhi@huaweicloud.com/
>
> Changes since v3:
> - Added patch 5 (zones array memleak) and patch 6 (cleanup).
> - Added patch 7 (NULL-ptr-deref on shared tag_set queue shrink).
> - Patch 9: reworked the fix from v3's patch 6 to take the file-scope
> lock in _store instead of scattering READ_ONCE/WRITE_ONCE.
> https://lore.kernel.org/all/20260708073917.2172392-1-wozizhi@huaweicloud.com/
>
> Changes since v2:
> - Dropped the lock rename patch; the rename and locking rework will be
> sent as a separate series (per Damien's suggestion).
> - Patch 3: fixed the tense in the commit message.
> - Patch 4: also update dev->NAME in the "!dev->nullb" path, which was
> previously lost.
> https://lore.kernel.org/all/20260707025542.1299859-1-wozizhi@huaweicloud.com/
>
> Changes since v1:
> - Added patches 4-6, and modify the lock name in patch 2.
> https://lore.kernel.org/all/20260706123507.3809871-1-wozizhi@huaweicloud.com/
>
> Zizhi Wo (9):
> null_blk: use DEFINE_MUTEX for the file-scope mutex
> null_blk: register configfs subsystem after creating default devices
> null_blk: move unregister_blkdev() after destroying dev in null_exit()
> null_blk: free global tag_set on init error path
> null_blk: free zones array on device power-off
> null_blk: clean up null_del_dev() to use cached dev pointer
> null_blk: reject per-device queue resize for shared tag set
> null_blk: serialize configfs attribute stores with device setup
> null_blk: serialize configfs attribute shows with the file-scope lock
>
> drivers/block/null_blk/main.c | 93 +++++++++++++++++++++--------------
> 1 file changed, 56 insertions(+), 37 deletions(-)
>
prev parent reply other threads:[~2026-07-24 1:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 4:17 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
2026-07-24 1:18 ` Zizhi Wo [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=1d06cc3c-df97-46a3-a0fe-9e46ce6a813e@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®