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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250717110410.GA15870@lst.de>
Date: Thu, 17 Jul 2025 13:04:10 +0200
From: Christoph Hellwig <hch@....de>
To: Christian Brauner <brauner@...nel.org>
Cc: Zizhi Wo <wozizhi@...wei.com>, hch@....de, 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

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?