From: Christoph Hellwig <hch@infradead.org>
To: Daniil Lunev <dlunev@chromium.org>
Cc: linux-fsdevel@vger.kernel.org, fuse-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 1/2] fs/super: Add a flag to mark super block defunc
Date: Wed, 11 May 2022 07:54:14 -0700 [thread overview]
Message-ID: <YnvOFt3sC/XLJj05@infradead.org> (raw)
In-Reply-To: <20220511113050.1.Ifc059f4eca1cce3e2cc79818467c94f65e3d8dde@changeid>
On Wed, May 11, 2022 at 11:30:56AM +1000, Daniil Lunev wrote:
> File system can mark a block "defunc" in order to prevent matching
> against it in a new mount.
Why use a bool instead of using s_iflags?
Also I suspect we should never reuse a force mounted superblock,
but at least for block devices we should also not allow allocating
a new one for that case but just refuse the mount.
next prev parent reply other threads:[~2022-05-11 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 1:30 [PATCH 0/2] Prevent re-use of FUSE superblock after force unmount Daniil Lunev
2022-05-11 1:30 ` [PATCH 1/2] fs/super: Add a flag to mark super block defunc Daniil Lunev
2022-05-11 14:50 ` Theodore Ts'o
2022-05-11 14:54 ` Christoph Hellwig [this message]
2022-05-11 21:33 ` Daniil Lunev
2022-05-11 1:30 ` [PATCH 2/2] FUSE: Mark super block defunc on force unmount Daniil Lunev
2022-05-11 7:07 ` [PATCH 0/2] Prevent re-use of FUSE superblock after " Miklos Szeredi
2022-05-11 7:36 ` Daniil Lunev
2022-05-11 7:54 ` Miklos Szeredi
2022-05-11 9:37 ` Daniil Lunev
2022-05-11 10:34 ` Miklos Szeredi
2022-05-11 11:19 ` Daniil Lunev
2022-05-11 11:38 ` Bernd Schubert
2022-05-11 12:28 ` Miklos Szeredi
2022-05-11 13:05 ` Daniil Lunev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YnvOFt3sC/XLJj05@infradead.org \
--to=hch@infradead.org \
--cc=dlunev@chromium.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).