From: Antony Antony <antony.antony@secunet.com>
To: David Howells <dhowells@redhat.com>
Cc: Antony Antony <antony@phenome.org>,
Christian Brauner <brauner@kernel.org>,
Eric Van Hensbergen <ericvh@kernel.org>,
"Latchesar Ionkov" <lucho@ionkov.net>,
Dominique Martinet <asmadeus@codewreck.org>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Sedat Dilek <sedat.dilek@gmail.com>,
Maximilian Bosch <maximilian@mbosch.me>,
<regressions@lists.linux.dev>, <v9fs@lists.linux.dev>,
<netfs@lists.linux.dev>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Antony Antony <antony.antony@secunet.com>
Subject: Re: [REGRESSION] 9pfs issues on 6.12-rc1
Date: Wed, 23 Oct 2024 21:38:39 +0200 [thread overview]
Message-ID: <ZxlQv5OXjJUbkLah@moon.secunet.de> (raw)
In-Reply-To: <3327438.1729678025@warthog.procyon.org.uk>
On Wed, Oct 23, 2024 at 11:07:05 +0100, David Howells wrote:
> Hi Antony,
>
> I think the attached should fix it properly rather than working around it as
> the previous patch did. If you could give it a whirl?
Yes this also fix the crash.
Tested-by: Antony Antony <antony.antony@secunet.com>
thanks,
-antony
next prev parent reply other threads:[~2024-10-23 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D4LHHUNLG79Y.12PI0X6BEHRHW@mbosch.me>
[not found] ` <c3eff232-7db4-4e89-af2c-f992f00cd043@leemhuis.info>
[not found] ` <D4LNG4ZHZM5X.1STBTSTM9LN6E@mbosch.me>
[not found] ` <CA+icZUVkVcKw+wN1p10zLHpO5gqkpzDU6nH46Nna4qaws_Q5iA@mail.gmail.com>
[not found] ` <ZxFQw4OI9rrc7UYc@Antony2201.local>
2024-10-23 10:07 ` [REGRESSION] 9pfs issues on 6.12-rc1 David Howells
2024-10-23 19:38 ` Antony Antony [this message]
2025-06-12 22:24 ` Ryan Lahfa
2025-06-27 5:44 ` Christian Theune
2025-06-27 6:44 ` Dominique Martinet
2025-06-27 8:19 ` Christian Theune
2025-06-27 10:00 ` David Howells
2025-06-27 10:33 ` Ryan Lahfa
2025-08-10 17:57 ` Arnout Engelen
2025-08-11 0:57 ` asmadeus
2025-08-11 7:43 ` Dominique Martinet
2025-08-11 12:43 ` Arnout Engelen
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=ZxlQv5OXjJUbkLah@moon.secunet.de \
--to=antony.antony@secunet.com \
--cc=antony@phenome.org \
--cc=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=maximilian@mbosch.me \
--cc=netfs@lists.linux.dev \
--cc=regressions@lists.linux.dev \
--cc=sedat.dilek@gmail.com \
--cc=v9fs@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