[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231207024024.GU1674809@ZenIV>
Date: Thu, 7 Dec 2023 02:40:24 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Dave Chinner <david@...morbit.com>
Cc: linux-fsdevel@...r.kernel.org, linux-block@...r.kernel.org,
linux-cachefs@...hat.com, dhowells@...hat.com,
gfs2@...ts.linux.dev, dm-devel@...ts.linux.dev,
linux-security-module@...r.kernel.org, selinux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 03/11] vfs: Use dlock list for superblock's inode list
On Wed, Dec 06, 2023 at 05:05:32PM +1100, Dave Chinner wrote:
> @@ -303,6 +303,7 @@ static void destroy_unused_super(struct super_block *s)
> super_unlock_excl(s);
> list_lru_destroy(&s->s_dentry_lru);
> list_lru_destroy(&s->s_inode_lru);
> + free_dlock_list_heads(&s->s_inodes);
> security_sb_free(s);
> put_user_ns(s->s_user_ns);
> kfree(s->s_subtype);
Umm... Who's going to do that on normal umount?
Powered by blists - more mailing lists