From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic in netif_rx_internal after v6 pings between netns
Date: Mon, 22 Jan 2024 09:28:04 -0800 [thread overview]
Message-ID: <20240122092804.3535b652@kernel.org> (raw)
In-Reply-To: <5340b60d-a09a-4865-a648-d1a45e9e6d5f@kernel.org>
On Sat, 20 Jan 2024 18:53:50 +0100 Matthieu Baerts wrote:
> FYI, I managed to find a commit that seems to be causing the issue:
>
> 8e791f7eba4c ("x86/kprobes: Drop removed INT3 handling code")
>
> It is not clear why, but if I revert it, I can no longer reproduce the
> issue. I reported the issue to the patch's author and the x86's ML:
>
> https://lore.kernel.org/r/06cb540e-34ff-4dcd-b936-19d4d14378c9@kernel.org
>
> Thank you again for your help.
Hi Matthieu!
Somewhat related. What do you do currently to ignore crashes?
I was seeing a lot of:
https://netdev-2.bots.linux.dev/vmksft-net-mp/results/431181/vm-crash-thr0-2
So I hacked up this function to filter the crash from NIPA CI:
https://github.com/kuba-moo/nipa/blob/master/contest/remote/lib/vm.py#L50
It tries to get first 5 function names from the stack, to form
a "fingerprint". But I seem to recall a discussion at LPC's testing
track that there are existing solutions for generating fingerprints.
Are you aware of any?
(FWIW the crash from above seems to be gone on latest linux.git,
this night's CIs run are crash-free.)
next prev parent reply other threads:[~2024-01-22 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98724dcd-ddf3-4f78-a386-f966ffbc9528@kernel.org>
2024-01-16 19:17 ` Kernel panic in netif_rx_internal after v6 pings between netns Eric Dumazet
2024-01-16 21:15 ` Matthieu Baerts
2024-01-20 17:53 ` Matthieu Baerts
2024-01-22 17:28 ` Jakub Kicinski [this message]
2024-01-22 18:22 ` Matthieu Baerts
2024-01-22 18:36 ` Jakub Kicinski
2024-01-22 19:06 ` Matthieu Baerts
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=20240122092804.3535b652@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
/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).