From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kuniyuki Iwashima" <kuniyu@amazon.com>,
"Naresh Kamboju" <naresh.kamboju@linaro.org>
Cc: "Jakub Kicinski" <kuba@kernel.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"David S . Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, lkft-triage@lists.linaro.org,
"Xin Long" <lucien.xin@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
Netdev <netdev@vger.kernel.org>,
stable@vger.kernel.org, willemdebruijn.kernel@gmail.com
Subject: Re: selftests: net: udpgso_bench.sh: RIP: 0010:lookup_reuseport
Date: Sat, 27 May 2023 11:33:28 +0200 [thread overview]
Message-ID: <f0194cbe-eb5b-40ee-8723-1927ebddefc1@app.fastmail.com> (raw)
In-Reply-To: <20230527034922.5542-1-kuniyu@amazon.com>
On Sat, May 27, 2023, at 05:49, Kuniyuki Iwashima wrote:
> From: Jakub Kicinski <kuba@kernel.org>
> Date: Fri, 26 May 2023 20:16:07 -0700
>> On Wed, 24 May 2023 13:24:15 +0530 Naresh Kamboju wrote:
>> > While running selftests: net: udpgso_bench.sh on qemu-x86_64 the following
>> > kernel crash noticed on stable rc 6.3.4-rc2 kernel.
>>
>> Can you repro this or it's just a one-off?
>>
>> Adding some experts to CC.
>
> FWIW, I couldn't reproduce it on my x86_64 QEMU setup & 6.4.0-rc3
> at least 5 times, so maybe one-off ?
This looks like one of several spurious reports that lkft has produced
recently, where an 'int3' trap instruction is executed in a function
that is live-patched, but at a point where the int3 is not expected.
Anders managed to get a reproducer for one of these on his manchine
yesterday, and has narrowed it down to failing on qemu-7.2.2 but
not failing on qemu-8.0.
The current theory right now is that this is a qemu bug when
dealing with self-modifying x86 code that has been fixed in
qemu-8.0 already, and my suggestion would be to ignore all bugs
found by lkft that involve an 'int3' trap, and instead change
the lkft setup to use either qemu-8.0 or run the test systems
in kvm (which would also be much faster and save resources).
Someone still needs to get to the bottom of this bug to see
if it's in qemu or in the kernel livepatching code, but I'm
sure it has nothing to do with the ipv6 stack.
Arnd
next prev parent reply other threads:[~2023-05-27 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 7:54 Naresh Kamboju
2023-05-27 3:16 ` Jakub Kicinski
2023-05-27 3:49 ` Kuniyuki Iwashima
2023-05-27 9:33 ` Arnd Bergmann [this message]
2023-05-27 18:02 ` Naresh Kamboju
2023-05-27 18:39 ` Arnd Bergmann
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=f0194cbe-eb5b-40ee-8723-1927ebddefc1@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lucien.xin@gmail.com \
--cc=martin.lau@linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
/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®