From: patchwork-bot+netdevbpf@kernel.org
To: Jian Wen <wenjianhn@gmail.com>
Cc: jiri@mellanox.com, aleksander.lobakin@intel.com,
edumazet@google.com, davem@davemloft.net, wenjian1@xiaomi.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] devlink: use kvzalloc() to allocate devlink instance resources
Date: Fri, 29 Mar 2024 19:30:33 +0000 [thread overview]
Message-ID: <171174063324.18563.6675369360892435443.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240327082128.942818-1-wenjian1@xiaomi.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 Mar 2024 16:21:28 +0800 you wrote:
> During live migration of a virtual machine, the SR-IOV VF need to be
> re-registered. It may fail when the memory is badly fragmented.
>
> The related log is as follows.
>
> Mar 1 18:54:12 kernel: hv_netvsc 6045bdaa-c0d1-6045-bdaa-c0d16045bdaa eth0: VF slot 1 added
> ...
> Mar 1 18:54:13 kernel: kworker/0:0: page allocation failure: order:7, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0
> Mar 1 18:54:13 kernel: CPU: 0 PID: 24006 Comm: kworker/0:0 Tainted: G E 5.4...x86_64 #1
> Mar 1 18:54:13 kernel: Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018
> Mar 1 18:54:13 kernel: Workqueue: events work_for_cpu_fn
> Mar 1 18:54:13 kernel: Call Trace:
> Mar 1 18:54:13 kernel: dump_stack+0x8b/0xc8
> Mar 1 18:54:13 kernel: warn_alloc+0xff/0x170
> Mar 1 18:54:13 kernel: __alloc_pages_slowpath+0x92c/0xb2b
> Mar 1 18:54:13 kernel: ? get_page_from_freelist+0x1d4/0x1140
> Mar 1 18:54:13 kernel: __alloc_pages_nodemask+0x2f9/0x320
> Mar 1 18:54:13 kernel: alloc_pages_current+0x6a/0xb0
> Mar 1 18:54:13 kernel: kmalloc_order+0x1e/0x70
> Mar 1 18:54:13 kernel: kmalloc_order_trace+0x26/0xb0
> Mar 1 18:54:13 kernel: ? __switch_to_asm+0x34/0x70
> Mar 1 18:54:13 kernel: __kmalloc+0x276/0x280
> Mar 1 18:54:13 kernel: ? _raw_spin_unlock_irqrestore+0x1e/0x40
> Mar 1 18:54:13 kernel: devlink_alloc+0x29/0x110
> Mar 1 18:54:13 kernel: mlx5_devlink_alloc+0x1a/0x20 [mlx5_core]
> Mar 1 18:54:13 kernel: init_one+0x1d/0x650 [mlx5_core]
> Mar 1 18:54:13 kernel: local_pci_probe+0x46/0x90
> Mar 1 18:54:13 kernel: work_for_cpu_fn+0x1a/0x30
> Mar 1 18:54:13 kernel: process_one_work+0x16d/0x390
> Mar 1 18:54:13 kernel: worker_thread+0x1d3/0x3f0
> Mar 1 18:54:13 kernel: kthread+0x105/0x140
> Mar 1 18:54:13 kernel: ? max_active_store+0x80/0x80
> Mar 1 18:54:13 kernel: ? kthread_bind+0x20/0x20
> Mar 1 18:54:13 kernel: ret_from_fork+0x3a/0x50
>
> [...]
Here is the summary with links:
- [net-next,v2] devlink: use kvzalloc() to allocate devlink instance resources
https://git.kernel.org/netdev/net-next/c/730fffce4fd2
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:[~2024-03-29 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 8:21 [PATCH net-next v2] devlink: use kvzalloc() to allocate devlink instance resources Jian Wen
2024-03-27 10:15 ` Alexander Lobakin
2024-03-28 1:42 ` Jian Wen
2024-03-29 1:49 ` Jakub Kicinski
2024-03-29 19:30 ` 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=171174063324.18563.6675369360892435443.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=wenjian1@xiaomi.com \
--cc=wenjianhn@gmail.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;
as well as URLs for NNTP newsgroup(s).