From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "J. R. Okajima" <hooanon05g@gmail.com>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] acl updates for v6.2 #forregzbot
Date: Mon, 2 Jan 2023 08:25:46 +0100 [thread overview]
Message-ID: <e713f86b-1a05-c416-9415-e02fbd95f308@leemhuis.info> (raw)
In-Reply-To: <25986.1672603666@jrobl>
On 01.01.23 21:07, J. R. Okajima wrote:
> Thorsten Leemhuis:
>> Thanks for the report. To be sure below issue doesn't fall through the
>> cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
>> tracking bot:
>
> Hold it!
> I'm not sure whether this is a regression or a bugfix. Or even it maybe
> a problem on my side. I'm still struggling to find out the reproducible
> way.
Don't worry about that, it's way easier to keep track of a potential
regression by just adding it to the tracking and later removing it, if
it turns out to not be a regression.
BTW, xfstests found a acl issue on ext4, too:
https://lore.kernel.org/lkml/202212291509.704a11c9-oliver.sang@intel.com/
I have no idea at all if this might be related, as this is not my area
of expertise, I just thought you might want to know about that.
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
Did I miss something or do something stupid? Then reply and tell me:
https://linux-regtracking.leemhuis.info/about/#stupid
prev parent reply other threads:[~2023-01-02 7:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:19 [GIT PULL] acl updates for v6.2 Christian Brauner
2022-12-13 2:56 ` Linus Torvalds
2022-12-13 9:09 ` Christian Brauner
2022-12-13 3:49 ` pr-tracker-bot
2022-12-27 15:27 ` J. R. Okajima
2022-12-27 18:31 ` Christian Brauner
2022-12-27 23:54 ` hooanon05g
2023-01-04 0:57 ` hooanon05g
2023-01-04 10:04 ` Linux kernel regression tracking (#info)
2023-01-04 10:14 ` Christian Brauner
2023-01-04 10:26 ` Thorsten Leemhuis
2023-01-04 10:37 ` Christian Brauner
2022-12-28 8:40 ` [GIT PULL] acl updates for v6.2 #forregzbot Thorsten Leemhuis
2023-01-01 20:07 ` J. R. Okajima
2023-01-02 7:25 ` 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=e713f86b-1a05-c416-9415-e02fbd95f308@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=hooanon05g@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).