From: Christian Brauner <brauner@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Will Deacon <will@kernel.org>,
ericvh@kernel.org, lucho@ionkov.net, asmadeus@codewreck.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
oss@crudebyte.com, v9fs@lists.linux.dev,
linux-kernel@vger.kernel.org, oleg@redhat.com, keirf@google.com,
regressions@lists.linux.dev
Subject: Re: VFS regression with 9pfs ("Lookup would have caused loop")
Date: Fri, 25 Oct 2024 17:29:14 +0200 [thread overview]
Message-ID: <20241025-aberglaube-gerissen-5e1a9da4fffc@brauner> (raw)
In-Reply-To: <20241025-ungewiss-zersplittern-c124bc48be5c@brauner>
On Fri, Oct 25, 2024 at 05:25:47PM +0200, Christian Brauner wrote:
> On Tue, Oct 15, 2024 at 08:07:10PM +0200, Thorsten Leemhuis wrote:
> > Hi Will! Top-posting for once, to make this easily accessible to everyone.
> >
> > Thx for bringing this to my attention. I had hoped that Eric might reply
> > and waited a bit, but that did not happen. I kind of expected that, as
> > he seems to be somewhat afk, as the last mail from him on lore is from
> > mid-September; and in the weeks before that he did not post much either.
> > Hmmm. :-/
> >
> > CCed Christian and Al, maybe they might be able to help directly or
> > indirectly somehow. If not, we likely need to get Linus involved to
> > decide if we want to at least temporarily revert the changes you mentioned.
>
> Sorry, I'm just getting to this thread now as I'm still out with a
> fscking case of the flu.
> /me reads...
Ok, so this seems handled already. Great.
prev parent reply other threads:[~2024-10-25 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 10:05 Will Deacon
2024-10-09 15:34 ` Will Deacon
2024-10-15 18:07 ` Thorsten Leemhuis
2024-10-16 9:39 ` asmadeus
2024-10-22 15:01 ` Will Deacon
2024-10-22 23:00 ` Dominique Martinet
2024-10-23 7:22 ` Linux regression tracking (Thorsten Leemhuis)
2024-10-23 15:14 ` Will Deacon
2024-10-25 15:25 ` Christian Brauner
2024-10-25 15:29 ` Christian Brauner [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=20241025-aberglaube-gerissen-5e1a9da4fffc@brauner \
--to=brauner@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=keirf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=oleg@redhat.com \
--cc=oss@crudebyte.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=v9fs@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=will@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®