Re: [PATCH V6 00/10] null_blk: fix init/exit races and memleaks

Jens Axboe <[email protected]>
Newsgroups org.kernel.vger.linux-block
Message-ID <178683847329.1984298.4609905343090788312.b4-ty@b4>
On Sat, 25 Jul 2026 10:24:59 +0800, Zizhi Wo wrote:
> This series fixes several issues in null_blk around lock initialization,
> memory leaks, concurrent configfs access, and module init/exit.
> 
> See the individual patch descriptions for details.
> 
> Changes since v5:
> - Add a new patch converting the file-scope mutex users to gaurd(mutex).
> - Simplify the last two patches accordingly.
> https://lore.kernel.org/all/[email protected]/
> 
> [...]

Applied, thanks!

[01/10] null_blk: use DEFINE_MUTEX for the file-scope mutex
        commit: 017dac7670909eaea3eb36e6b3b5a8be9ce0a14d
[02/10] null_blk: register configfs subsystem after creating default devices
        commit: c9d293d6bb0575fcb1f3408129453187e2a28a4e
[03/10] null_blk: move unregister_blkdev() after destroying dev in null_exit()
        commit: 4ec26e8885161ce15b66957be638a08d786035cb
[04/10] null_blk: free global tag_set on init error path
        commit: 5a1c5ff3a49ba93a1fd0b70537e7a0164071760d
[05/10] null_blk: free zones array on device power-off
        commit: 2a6357a9b935a34f5508618fee8a7fffbf7722a8
[06/10] null_blk: clean up null_del_dev() to use cached dev pointer
        commit: 5bce98f9e76f62386a3264b9782afb4dac99f31f
[07/10] null_blk: reject per-device queue resize for shared tag set
        commit: 1cdfe2fa62b48728a9b436fbbd3dbe4c11593e24
[08/10] null_blk: convert file-scope mutex users to guard(mutex)
        commit: e3ef4b1b76d6721067259577ab5df54a173d9341
[09/10] null_blk: serialize configfs attribute stores with the lock
        commit: 7e7fff51808237703a3a1df6dd5cae1dfd1db86d
[10/10] null_blk: serialize configfs attribute shows with the lock
        commit: 2cd9e14abece86d790c2117276ff49173b735b61

Best regards,
-- 
Jens Axboe
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.