All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Bernd Schubert <bschubert@ddn.com>,
	linux-fsdevel@vger.kernel.org,
	Jeffle Xu <jefflexu@linux.alibaba.com>,
	Dharmendra Singh <dsingh@ddn.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	German Maglione <gmaglione@redhat.com>,
	Sergio Lopez <slp@redhat.com>
Subject: Re: [PATCH] fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT flag
Date: Tue, 26 Apr 2022 09:24:51 -0400	[thread overview]
Message-ID: <Ymfyo9W6rLsIQm20@redhat.com> (raw)
In-Reply-To: <CAJfpegv3UfJbzkXTk0V80hiY-d4hRBbrn67DMnTR6Svw8+11cw@mail.gmail.com>

On Tue, Apr 26, 2022 at 03:13:50PM +0200, Miklos Szeredi wrote:
> On Tue, 26 Apr 2022 at 15:01, Vivek Goyal <vgoyal@redhat.com> wrote:
> 
> > Agree that it probably is a nice change if we had introduced this in the
> > beginning itself. Its like extra saftey net. But now if we add it, it
> > will break things which is not nice. So at this point of time, it probably
> > is better to fix fuse servers instead and set ->flags2 to zero, IMHO.
> 
> I think the question is whether the "unfixed" virtiofsd
> implementations made it into any sort of release or not.

Existing unfixed versions are already released in various releses. C version
of virtiofsd is already being used in RHEL8 release and some fedora releases.
And rust version of virtiofsd is supposed to be in RHEL9 beta.

Hence if we change it now, it is possible older virtiofsd (unfixed one)
is running on host and trying to boot a newer guest kernel and that
leads to breaking things.

Thanks
Vivek

> 
> If not, then I think it's fine to break unreleased versions, since
> they are ephemeral anyway.

> 
> Thanks,
> Miklos
> 


      reply	other threads:[~2022-04-26 13:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 11:53 [PATCH] fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT flag Bernd Schubert
2022-04-21 15:36 ` Miklos Szeredi
2022-04-21 16:28   ` Bernd Schubert
2022-04-24  8:29   ` Vivek Goyal
     [not found]     ` <DM5PR1901MB20375D0CF53C5F7D338154D0B5F99@DM5PR1901MB2037.namprd19.prod.outlook.com>
2022-04-24 11:32       ` JeffleXu
2022-04-25  8:09     ` Miklos Szeredi
2022-04-26 13:01       ` Vivek Goyal
2022-04-26 13:13         ` Miklos Szeredi
2022-04-26 13:24           ` Vivek Goyal [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=Ymfyo9W6rLsIQm20@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=bschubert@ddn.com \
    --cc=dgilbert@redhat.com \
    --cc=dsingh@ddn.com \
    --cc=gmaglione@redhat.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=slp@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.