From: patchwork-bot+netdevbpf@kernel.org
To: Douglas Anderson <dianders@chromium.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, git@apitzsch.eu, bjorn@mork.no,
dober6023@gmail.com, hayeswang@realtek.com, jflf_kernel@gmx.com,
svenva@chromium.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] r8152: Add __GFP_NOWARN to big allocations
Date: Sat, 08 Apr 2023 03:20:17 +0000 [thread overview]
Message-ID: <168092401746.26294.3498569400410508226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230406171411.1.I84dbef45786af440fd269b71e9436a96a8e7a152@changeid>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Apr 2023 17:14:26 -0700 you wrote:
> When memory is a little tight on my system, it's pretty easy to see
> warnings that look like this.
>
> ksoftirqd/0: page allocation failure: order:3, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0
> ...
> Call trace:
> dump_backtrace+0x0/0x1e8
> show_stack+0x20/0x2c
> dump_stack_lvl+0x60/0x78
> dump_stack+0x18/0x38
> warn_alloc+0x104/0x174
> __alloc_pages+0x588/0x67c
> alloc_rx_agg+0xa0/0x190 [r8152 ...]
> r8152_poll+0x270/0x760 [r8152 ...]
> __napi_poll+0x44/0x1ec
> net_rx_action+0x100/0x300
> __do_softirq+0xec/0x38c
> run_ksoftirqd+0x38/0xec
> smpboot_thread_fn+0xb8/0x248
> kthread+0x134/0x154
> ret_from_fork+0x10/0x20
>
> [...]
Here is the summary with links:
- r8152: Add __GFP_NOWARN to big allocations
https://git.kernel.org/netdev/net/c/5cc33f139e11
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:[~2023-04-08 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 0:14 [PATCH] r8152: Add __GFP_NOWARN to big allocations Douglas Anderson
2023-04-07 6:24 ` Hayes Wang
2023-04-08 3:20 ` 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=168092401746.26294.3498569400410508226.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=dober6023@gmail.com \
--cc=edumazet@google.com \
--cc=git@apitzsch.eu \
--cc=hayeswang@realtek.com \
--cc=jflf_kernel@gmx.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=svenva@chromium.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).