linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniil Lunev <dlunev@chromium.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 0/2] Prevent re-use of FUSE superblock after force unmount
Date: Wed, 11 May 2022 23:05:37 +1000	[thread overview]
Message-ID: <CAONX=-fQvBczRk2HV1GXBoypq7_QbUX9JXc2AuDMQ+-qfYW32A@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegtTP==oMm+LhvOkrxkPB973-Y80chbwYpXSiOAXBDhHJw@mail.gmail.com>

> I think it would be easiest to remove the super block from the
> type->fs_supers list.
I will try tomorrow and upload an updated patchset.
Thanks,
Daniil.

      reply	other threads:[~2022-05-11 13:05 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
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 [this message]

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='CAONX=-fQvBczRk2HV1GXBoypq7_QbUX9JXc2AuDMQ+-qfYW32A@mail.gmail.com' \
    --to=dlunev@chromium.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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).