From: patchwork-bot+netdevbpf@kernel.org
To: Michal Schmidt <mschmidt@redhat.com>
Cc: ajit.khaparde@broadcom.com, sriharsha.basavapatna@broadcom.com,
somnath.kotur@broadcom.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, razor@blackwall.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] benet: fix BUG when creating VFs
Date: Tue, 05 Aug 2025 00:30:27 +0000 [thread overview]
Message-ID: <175435382749.1400451.18307396008220746943.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250801101338.72502-1-mschmidt@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 1 Aug 2025 12:13:37 +0200 you wrote:
> benet crashes as soon as SRIOV VFs are created:
>
> kernel BUG at mm/vmalloc.c:3457!
> Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
> CPU: 4 UID: 0 PID: 7408 Comm: test.sh Kdump: loaded Not tainted 6.16.0+ #1 PREEMPT(voluntary)
> [...]
> RIP: 0010:vunmap+0x5f/0x70
> [...]
> Call Trace:
> <TASK>
> __iommu_dma_free+0xe8/0x1c0
> be_cmd_set_mac_list+0x3fe/0x640 [be2net]
> be_cmd_set_mac+0xaf/0x110 [be2net]
> be_vf_eth_addr_config+0x19f/0x330 [be2net]
> be_vf_setup+0x4f7/0x990 [be2net]
> be_pci_sriov_configure+0x3a1/0x470 [be2net]
> sriov_numvfs_store+0x20b/0x380
> kernfs_fop_write_iter+0x354/0x530
> vfs_write+0x9b9/0xf60
> ksys_write+0xf3/0x1d0
> do_syscall_64+0x8c/0x3d0
>
> [...]
Here is the summary with links:
- [net] benet: fix BUG when creating VFs
https://git.kernel.org/netdev/net/c/5a40f8af2ba1
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:[~2025-08-05 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 10:13 Michal Schmidt
2025-08-01 10:24 ` Nikolay Aleksandrov
2025-08-05 0:20 ` Jakub Kicinski
2025-08-05 12:52 ` Michal Schmidt
2025-08-05 0: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=175435382749.1400451.18307396008220746943.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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
all inboxes | Powered by JetHome®