From: "Linux regression tracking #adding (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "André Draszik" <git@andred.net>, linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org,
"André Draszik" <andre.draszik@linaro.org>,
"Bernd Schubert" <bschubert@ddn.com>,
"Miklos Szeredi" <mszeredi@redhat.com>,
stable@vger.kernel.org,
"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: [RESEND PATCH] Revert "fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT"
Date: Sun, 22 Oct 2023 15:35:14 +0200 [thread overview]
Message-ID: <fd1edea6-5512-48fb-a5d1-e25ebdc56904@leemhuis.info> (raw)
In-Reply-To: <20230904133321.104584-1-git@andred.net>
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
On 04.09.23 15:33, André Draszik wrote:
> From: André Draszik <andre.draszik@linaro.org>
>
> This reverts commit 3066ff93476c35679cb07a97cce37d9bb07632ff.
>
> This patch breaks all existing userspace by requiring updates as
> mentioned in the commit message, which is not allowed.
>
> Revert to restore compatibility with existing userspace
> implementations.
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:
#regzbot ^introduced 3066ff93476c35679cb07a97cce37d9bb07632
#regzbot title fuse: creating new files, or reading existing files in i
Android, now returns -EFAULT
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.
Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-10-22 13:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 13:33 André Draszik
2023-09-04 13:41 ` Miklos Szeredi
2023-09-04 14:21 ` André Draszik
2023-09-04 14:45 ` Bernd Schubert
2023-10-18 11:15 ` [PATCH v2] " André Draszik
2023-10-18 11:39 ` Bernd Schubert
2023-10-18 11:46 ` André Draszik
2023-10-18 11:52 ` Bernd Schubert
2023-10-18 14:26 ` André Draszik
2023-10-18 14:40 ` Bernd Schubert
2023-10-18 15:51 ` Bernd Schubert
2023-10-25 11:30 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-25 13:17 ` Miklos Szeredi
2023-10-26 5:28 ` Thorsten Leemhuis
2023-10-27 10:40 ` Greg Kroah-Hartman
[not found] ` <CAOssrKfNkMmHB2oHHO8gWbzDX27vS--e9dZoh_Mjv-17mSUTBw@mail.gmail.com>
[not found] ` <2023102740-think-hatless-ab87@gregkh>
[not found] ` <CAOssrKd-O1JKEPzvnM1VkQ0-oTpDv0RfY6B5oF5p63AtQ4HoqA@mail.gmail.com>
[not found] ` <2023102757-cornflake-pry-e788@gregkh>
2023-10-27 18:23 ` Miklos Szeredi
[not found] ` <689f677b84b484636b673b362b17a6501a056968.camel@linaro.org>
[not found] ` <CAOssrKfP+t-cy322ujizQofgZkPZsBu1H4+zfbWNEFCmTsXwug@mail.gmail.com>
[not found] ` <afe378bf254f6c4ac73bb55be3fa7422f2da3f5f.camel@linaro.org>
[not found] ` <CAOssrKeJB7BZ7fA6Uqo6rHohybmgovc6rVwDeHbegvweSyZeeA@mail.gmail.com>
2023-11-01 12:36 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-08 10:31 ` André Draszik
2023-11-08 12:18 ` Miklos Szeredi
2023-12-06 14:03 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-22 13:35 ` Linux regression tracking #adding (Thorsten Leemhuis) [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=fd1edea6-5512-48fb-a5d1-e25ebdc56904@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=andre.draszik@linaro.org \
--cc=bschubert@ddn.com \
--cc=git@andred.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®