From: patchwork-bot+netdevbpf@kernel.org
To: Jamie Bainbridge <jamie.bainbridge@gmail.com>
Cc: aelior@marvell.com, manishc@marvell.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, ariel.elior@cavium.com,
manish.chopra@cavium.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] qede: confirm skb is allocated before using
Date: Wed, 06 Apr 2022 14:20:13 +0000 [thread overview]
Message-ID: <164925481303.16469.8192990223353492835.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b86829347bc923c3b48487a941925292f103588d.1649210237.git.jamie.bainbridge@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 6 Apr 2022 21:19:19 +1000 you wrote:
> qede_build_skb() assumes build_skb() always works and goes straight
> to skb_reserve(). However, build_skb() can fail under memory pressure.
> This results in a kernel panic because the skb to reserve is NULL.
>
> Add a check in case build_skb() failed to allocate and return NULL.
>
> The NULL return is handled correctly in callers to qede_build_skb().
>
> [...]
Here is the summary with links:
- [net] qede: confirm skb is allocated before using
https://git.kernel.org/netdev/net/c/4e910dbe3650
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-04-06 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 11:19 [PATCH net] qede: confirm skb is allocated before using Jamie Bainbridge
2022-04-06 1:58 ` Jamie Bainbridge
2022-04-06 14:20 ` patchwork-bot+netdevbpf [this message]
2022-04-07 6:02 ` Jakub Kicinski
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=164925481303.16469.8192990223353492835.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aelior@marvell.com \
--cc=ariel.elior@cavium.com \
--cc=davem@davemloft.net \
--cc=jamie.bainbridge@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.chopra@cavium.com \
--cc=manishc@marvell.com \
--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