[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <afe378bf254f6c4ac73bb55be3fa7422f2da3f5f.camel@linaro.org>
Date: Fri, 27 Oct 2023 14:39:01 +0100
From: André Draszik <andre.draszik@...aro.org>
To: Miklos Szeredi <mszeredi@...hat.com>
Cc: Linux regressions mailing list <regressions@...ts.linux.dev>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Paul Lawrence <paullawrence@...gle.com>,
Daniel Rosenberg <drosen@...gle.com>,
Alessio Balsini <balsini@...roid.com>,
Amir Goldstein <amir73il@...il.com>,
Bernd Schubert <bschubert@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2] Revert "fuse: Apply flags2 only when userspace set
the FUSE_INIT_EXT"
On Fri, 2023-10-27 at 15:24 +0200, Miklos Szeredi wrote:
> On Fri, Oct 27, 2023 at 3:14 PM André Draszik
> <andre.draszik@...aro.org> wrote:
>
> > The patch in question has broken all users that use the higher
> > flags
> > and that don't use your version of libfuse, not just Android.
> > You're
> > filtering them out now when you didn't at the time that those
> > ('official) high flags were added. There are a couple more high
> > flags
> > than just the one that Android added.
>
> Okay. Where are all those users?
That's not the point. The point is the kernel<->user API has rendered
them too non-working.
> Why haven't they reported this?
Again, not the point. If I was to ask my crystal ball, Android is
trying to track the upstream kernel closely, others might not and might
not have bumped into this issue yet. Still, not the point.
Cheers,
A.
Powered by blists - more mailing lists