[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230809220545.1308228-1-hch@lst.de>
Date: Wed, 9 Aug 2023 15:05:32 -0700
From: Christoph Hellwig <hch@....de>
To: Al Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>
Cc: Namjae Jeon <linkinjeon@...nel.org>,
Sungjong Seo <sj1557.seo@...sung.com>,
"Theodore Ts'o" <tytso@....edu>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Konstantin Komarov <almaz.alexandrovich@...agon-software.com>,
"Darrick J. Wong" <djwong@...nel.org>,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
ntfs3@...ts.linux.dev, linux-xfs@...r.kernel.org
Subject: s_fs_info and ->kill_sb revisited v2
Hi all,
this series is against the VFS vfs.super branch does two slightly
related things:
- move closing of the external devices in ext4 and xfs from ->put_super
into ->kill_sb so that this isn't done under s_umount which creates
lock ordere reversal
- move freeing the private dta in s_fs_info into ->kill_sb for file systems
that pass it in through the fs_context, as otherwise we could leak it
before fill_super is called (this is something new on the vfs.super
branch because of the changed place where blkdev_get is called)
Changes since v1:
- keep the invalidate_bdev call in XFS and actually document it
- minor whitespace fixes
Powered by blists - more mailing lists