From: Florian Westphal <fw@strlen.de>
To: Kajetan Puchalski <kajetan.puchalski@arm.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Mel Gorman <mgorman@suse.de>,
lukasz.luba@arm.com, dietmar.eggemann@arm.com,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, stable@vger.kernel.org,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [Regression] stress-ng udp-flood causes kernel panic on Ampere Altra
Date: Fri, 1 Jul 2022 22:01:10 +0200 [thread overview]
Message-ID: <20220701200110.GA15144@breakpoint.cc> (raw)
In-Reply-To: <Yr7WTfd6AVTQkLjI@e126311.manchester.arm.com>
Kajetan Puchalski <kajetan.puchalski@arm.com> wrote:
> While running the udp-flood test from stress-ng on Ampere Altra (Mt.
> Jade platform) I encountered a kernel panic caused by NULL pointer
> dereference within nf_conntrack.
>
> The issue is present in the latest mainline (5.19-rc4), latest stable
> (5.18.8), as well as multiple older stable versions. The last working
> stable version I found was 5.15.40.
Do I need a special setup for conntrack?
No crashes after more than one hour of stress-ng on
1. 4 core amd64 Fedora 5.17 kernel
2. 16 core amd64, linux stable 5.17.15
3. 12 core intel, Fedora 5.18 kernel
4. 3 core aarch64 vm, 5.18.7-200.fc36.aarch64
I used standard firewalld ruleset for all of these and manually tuned
conntrack settings to make sure the early evict path (as per backtrace)
gets exercised.
next prev parent reply other threads:[~2022-07-01 20:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 11:11 [Regression] stress-ng udp-flood causes kernel panic on Ampere Altra Kajetan Puchalski
2022-07-01 11:42 ` [Regression] stress-ng udp-flood causes kernel panic on Ampere Altra #forregzbot Thorsten Leemhuis
2022-07-01 20:01 ` Florian Westphal [this message]
2022-07-02 11:08 ` [Regression] stress-ng udp-flood causes kernel panic on Ampere Altra Kajetan Puchalski
2022-07-02 11:54 ` Willy Tarreau
2022-07-02 20:56 ` Florian Westphal
2022-07-04 9:22 ` Kajetan Puchalski
2022-07-04 10:53 ` Kajetan Puchalski
2022-07-05 10:53 ` Kajetan Puchalski
2022-07-05 10:57 ` Will Deacon
2022-07-05 11:07 ` Will Deacon
2022-07-05 11:24 ` Will Deacon
2022-07-05 15:29 ` Kajetan Puchalski
2022-07-06 10:39 ` Kajetan Puchalski
2022-07-06 12:02 ` Florian Westphal
2022-07-06 12:18 ` Peter Zijlstra
2022-07-06 12:22 ` Will Deacon
2022-07-06 12:40 ` Florian Westphal
2022-07-06 14:50 ` [PATCH nf v3] netfilter: conntrack: fix crash due to confirmed bit load reordering Florian Westphal
2022-07-07 8:19 ` Will Deacon
2022-07-07 18:59 ` Florian Westphal
2022-07-07 10:17 ` Thorsten Leemhuis
2022-07-11 16:34 ` Kajetan Puchalski
2022-07-06 14:00 ` [Regression] stress-ng udp-flood causes kernel panic on Ampere Altra Peter Zijlstra
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=20220701200110.GA15144@breakpoint.cc \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dietmar.eggemann@arm.com \
--cc=edumazet@google.com \
--cc=kadlec@netfilter.org \
--cc=kajetan.puchalski@arm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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).