From: Kent Overstreet <kent.overstreet@linux.dev>
To: Eric Van Hensbergen <eric.vanhensbergen@linux.dev>
Cc: v9fs@lists.linux.dev
Subject: Re: new 9p kasan splat in 6.9
Date: Wed, 10 Apr 2024 13:02:49 -0400 [thread overview]
Message-ID: <ahtzctuhy25ptcztbbzmbjhkrh3sjpsjz4ixvrtmpl64iq4hej@vox2llmlv5im> (raw)
In-Reply-To: <29d9bb670a489a38dc9112e21dcf73d44b67d2f6@linux.dev>
On Wed, Apr 10, 2024 at 11:43:44AM +0000, Eric Van Hensbergen wrote:
> I'm having a hard time reproducing the
>
> April 1, 2024 at 8:27 PM, "Eric Van Hensbergen" <eric.vanhensbergen@linux.dev> wrote:
> >
> > April 1, 2024 at 8:12 PM, "Kent Overstreet" <kent.overstreet@linux.dev> wrote:
> > >
> > > Any other details you can give me from your environment (how is
> > > 9p mounted, is this qemu?, etc.)?
> > > It's qemu, standard mount options:
> > >
> > > host /host 9p rw,relatime,access=client,trans=virtio 0 0
> > >
> >
>
> I'm continuing to have a hard time reproducing on my test system -
> I've added a bunch of BUG_ON to the code to catch where I thought
> potential problems might be and have not tripped across any of them.
> Can I get two pieces of data:
> a) which 9P CONFIG options are enabled in your kernel?
$ grep 9P ktest-out/kernel_build.x86_64/.config
CONFIG_NET_9P=y
CONFIG_NET_9P_FD=y
CONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_DEBUG is not set
CONFIG_9P_FS=y
# CONFIG_9P_FS_POSIX_ACL is not set
# CONFIG_9P_FS_SECURITY is not set
> b) what is the underlying file system on the server
ext4
> c) what version of qemu are you running
QEMU emulator version 8.2.1 (Debian 1:8.2.1+ds-1)
> I'm going to try to spend all day today chasing this down, I may
> revert anyways if I can't reproduce since there's clearly degraded
> behavior -- I'd just feel better about it if I understood what the
> problem was. In your reverted version that doesn't experience the
> problem, was it just the last two patches that you reverted or the
> whole series?
Whole series. I've tested each revert individually, but unfortunately
the bug is so sporadic that none of them jumped out as the culprit (and
I'm running 1600 tests on each commit).
I don't have a way to tell my CI "run this test x number of times" or
I'd try to give you better information.
next prev parent reply other threads:[~2024-04-10 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 5:33 new 9p kasan splat in 6.9 Kent Overstreet
2024-04-02 0:02 ` Eric Van Hensbergen
2024-04-02 0:07 ` Kent Overstreet
2024-04-02 0:33 ` Eric Van Hensbergen
2024-04-02 1:12 ` Kent Overstreet
2024-04-02 1:27 ` Eric Van Hensbergen
2024-04-02 1:34 ` Kent Overstreet
2024-04-10 11:43 ` Eric Van Hensbergen
2024-04-10 17:02 ` Kent Overstreet [this message]
2024-04-10 18:17 ` Eric Van Hensbergen
2024-04-15 13:48 ` Eric Van Hensbergen
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=ahtzctuhy25ptcztbbzmbjhkrh3sjpsjz4ixvrtmpl64iq4hej@vox2llmlv5im \
--to=kent.overstreet@linux.dev \
--cc=eric.vanhensbergen@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.