From: Matthieu Baerts <matttbe@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: 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: Sat, 20 Jan 2024 18:53:50 +0100 [thread overview]
Message-ID: <5340b60d-a09a-4865-a648-d1a45e9e6d5f@kernel.org> (raw)
In-Reply-To: <65c4f6a2-207f-45e0-9ec3-bad81a05b196@kernel.org>
Hi Eric,
On 16/01/2024 22:15, Matthieu Baerts wrote:
> Hi Eric,
>
> Thank you for your quick reply!
>
> 16 Jan 2024 20:17:40 Eric Dumazet <edumazet@google.com>:
>> On Tue, Jan 16, 2024 at 7:36 PM Matthieu Baerts <matttbe@kernel.org> wrote:
>>> Our MPTCP CIs recently hit some kernel panics when validating the -net
>>> tree + 2 pending MPTCP patches. This is on top of e327b2372bc0 ("net:
>>> ravb: Fix dma_addr_t truncation in error case").
>>>
>>> It looks like these panics are not related to MPTCP. That's why I'm
>>> sharing that here:
>>
>> Indeed, this seems an x86 issue to me (jump labels ?)
>
> Thank you, good point!
>
> (I don't know why I always think there is no x86 issue :) )
>
>> are all stack
>> traces pointing to the same issue ?
>
> I think so.
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.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-01-20 17:53 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 ` Eric Dumazet
2024-01-16 21:15 ` Matthieu Baerts
2024-01-20 17:53 ` Matthieu Baerts [this message]
2024-01-22 17:28 ` Jakub Kicinski
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=5340b60d-a09a-4865-a648-d1a45e9e6d5f@kernel.org \
--to=matttbe@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.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
Powered by JetHome