From: Dominique Martinet <asmadeus@codewreck.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"kdevops@lists.linux.dev" <kdevops@lists.linux.dev>
Subject: Re: 9p KASAN splat
Date: Tue, 5 Mar 2024 09:11:14 +0900 [thread overview]
Message-ID: <ZeZjInbYNkpLPPkz@codewreck.org> (raw)
In-Reply-To: <D56DE98B-F6F1-4B38-A736-20B7E8B247FE@oracle.com>
Hi Chuck,
Chuck Lever III wrote on Mon, Mar 04, 2024 at 05:29:24PM +0000:
> While testing linux-next (20240304) under kdevops, I see
> this KASAN splat, seems 100% reproducible:
Thanks for the report -- there's already a fix for it but we've been
sitting on it for a while, sorry:
https://lkml.kernel.org/r/20240202121531.2550018-1-lizhi.xu@windriver.com
I've pinged Eric yesterday to take the patch as the problem is in his
-next tree; hopefully he'll be able to have a look soon but until then
please apply the patch directly.
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2024-03-05 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 17:29 9p KASAN splat Chuck Lever III
2024-03-05 0:11 ` Dominique Martinet [this message]
2024-03-05 18:08 ` Chuck Lever III
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=ZeZjInbYNkpLPPkz@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=chuck.lever@oracle.com \
--cc=ericvh@kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lucho@ionkov.net \
/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).