From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?0JLQsNGC0L7RgNC+0L/QuNC9INCQ0L3QtNGA0LXQuSA8YS52YXRvcm9waW5AY3Jw?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
=?utf-8?b?dC5ydT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
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, VenkatKumar.Duvvuru@Emulex.Com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, stable@vger.kernel.org
Subject: Re: [PATCH net] be2net: pass wrb_params in case of OS2BMC
Date: Thu, 20 Nov 2025 16:10:07 +0000 [thread overview]
Message-ID: <176365500794.1690915.6904445190938491859.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251119105015.194501-1-a.vatoropin@crpt.ru>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Nov 2025 10:51:12 +0000 you wrote:
> From: Andrey Vatoropin <a.vatoropin@crpt.ru>
>
> be_insert_vlan_in_pkt() is called with the wrb_params argument being NULL
> at be_send_pkt_to_bmc() call site. This may lead to dereferencing a NULL
> pointer when processing a workaround for specific packet, as commit
> bc0c3405abbb ("be2net: fix a Tx stall bug caused by a specific ipv6
> packet") states.
>
> [...]
Here is the summary with links:
- [net] be2net: pass wrb_params in case of OS2BMC
https://git.kernel.org/netdev/net/c/7d277a7a5857
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-11-20 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 10:51 [PATCH net] be2net: pass wrb_params in case of OS2BMC Ваторопин Андрей
2025-11-20 16:10 ` 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=176365500794.1690915.6904445190938491859.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?0JLQsNGC0L7RgNC+0L/QuNC9INCQ0L3QtNGA0LXQuSA8YS52YXRvcm9waW5AY3Jw?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc==?utf-8?b?dC5ydT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=VenkatKumar.Duvvuru@Emulex.Com \
--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=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.com \
--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