From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>
Cc: "Kuniyuki Iwashima" <kuniyu@amazon.com>,
"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 20:39:03 +0200 [thread overview]
Message-ID: <b66b1d4a-50c5-4e0e-98a9-a21a4eb6aab7@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYtzjP_EOjDFZYwTMjv5f3AK2pA_E6mk_mU5FQcZgo_qXQ@mail.gmail.com>
On Sat, May 27, 2023, at 20:02, Naresh Kamboju wrote:
> On Sat, 27 May 2023 at 15:03, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Sat, May 27, 2023, at 05:49, Kuniyuki Iwashima wrote:
>> 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).
>
> I will send out an update to ignore the 'int3' trap email reports.
Just to clarify: what I meant was ignoring the old reports with
qemu-7.2 but not any new ones that come from qemu-8.0.
Arnd
prev parent reply other threads:[~2023-05-27 18:41 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
2023-05-27 18:02 ` Naresh Kamboju
2023-05-27 18:39 ` Arnd Bergmann [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=b66b1d4a-50c5-4e0e-98a9-a21a4eb6aab7@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®