From: patchwork-bot+netdevbpf@kernel.org
To: Maciej W. Rozycki <macro@orcam.me.uk>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] FDDI: defxx: Rate-limit memory allocation errors
Date: Tue, 31 Mar 2026 02:00:06 +0000 [thread overview]
Message-ID: <177492240604.2055536.1918723401028996049.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2603291236590.60268@angie.orcam.me.uk>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 29 Mar 2026 13:32:25 +0100 (BST) you wrote:
> Prevent the system from becoming unstable or unusable due to a flood of
> memory allocation error messages under memory pressure, e.g.:
>
> [...]
> fddi0: Could not allocate receive buffer. Dropping packet.
> fddi0: Could not allocate receive buffer. Dropping packet.
> fddi0: Could not allocate receive buffer. Dropping packet.
> fddi0: Could not allocate receive buffer. Dropping packet.
> rcu: INFO: rcu_sched self-detected stall on CPU
> rcu: 0-...!: (332 ticks this GP) idle=255c/1/0x40000000 softirq=16420123/16420123 fqs=0
> rcu: (t=2103 jiffies g=35680089 q=4 ncpus=1)
> rcu: rcu_sched kthread timer wakeup didn't happen for 2102 jiffies! g35680089 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
> rcu: Possible timer handling issue on cpu=0 timer-softirq=12779658
> rcu: rcu_sched kthread starved for 2103 jiffies! g35680089 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
> rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior.
> rcu: RCU grace-period kthread stack dump:
> task:rcu_sched state:I stack:0 pid:14 tgid:14 ppid:2 flags:0x00004000
> Call Trace:
> __schedule+0x258/0x580
> schedule+0x19/0xa0
> schedule_timeout+0x4a/0xb0
> ? hrtimers_cpu_dying+0x1b0/0x1b0
> rcu_gp_fqs_loop+0xb1/0x450
> rcu_gp_kthread+0x9d/0x130
> kthread+0xb2/0xe0
> ? rcu_gp_init+0x4a0/0x4a0
> ? kthread_park+0x90/0x90
> ret_from_fork+0x2d/0x50
> ? kthread_park+0x90/0x90
> ret_from_fork_asm+0x12/0x20
> entry_INT80_32+0x10d/0x10d
> CPU: 0 UID: 500 PID: 21895 Comm: 31370.exe Not tainted 6.13.0-dirty #2
>
> [...]
Here is the summary with links:
- [net-next] FDDI: defxx: Rate-limit memory allocation errors
https://git.kernel.org/netdev/net-next/c/7fae6616704a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-31 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 12:32 [PATCH net-next] FDDI: defxx: Rate-limit memory allocation errors Maciej W. Rozycki
2026-03-30 12:46 ` Andrew Lunn
2026-03-31 2:00 ` patchwork-bot+netdevbpf [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=177492240604.2055536.1918723401028996049.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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