linux-kernel - Re: [bug report] A filesystem abnormal mount issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7337feb6-73ac-47b8-9a74-d579167ba438@huawei.com>
Date: Thu, 17 Jul 2025 19:49:54 +0800
From: Zizhi Wo <wozizhi@...wei.com>
To: Christoph Hellwig <hch@....de>, Christian Brauner <brauner@...nel.org>
CC: <jack@...e.com>, <axboe@...nel.dk>, <linux-fsdevel@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <yukuai3@...wei.com>, <yangerkun@...wei.com>
Subject: Re: [bug report] A filesystem abnormal mount issue



在 2025/7/17 19:04, Christoph Hellwig 写道:
> On Thu, Jul 17, 2025 at 11:39:01AM +0200, Christian Brauner wrote:
>> As long as you use the new mount api you should pass
>> FSCONFIG_CMD_CREATE_EXCL which will refuse to mount if a superblock for
>> the device already exists. IOW, it ensure that you cannot silently reuse
>> a superblock.
>>
>> Other than that I think a blkdev_get_no_open(dev, false) after
>> lookup_bdev() should sort the issue out. Christoph?
> 
> Or just check for GD_DEAD before the mount proceeds?


This is indeed concise and effective enough. Thank you for your
suggestion.

Thanks,
Zizhi Wo