From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, error27@gmail.com, caleb.connolly@linaro.com,
elder@kernel.org, kernel-janitors@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: ipa: avoid a null pointer dereference
Date: Fri, 18 Nov 2022 12:00:25 +0000 [thread overview]
Message-ID: <166877282570.14131.14093782729381689956.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221116223718.137175-1-elder@linaro.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 16 Nov 2022 16:37:18 -0600 you wrote:
> Dan Carpenter reported that Smatch found an instance where a pointer
> which had previously been assumed could be null (as indicated by a
> null check) was later dereferenced without a similar check.
>
> In practice this doesn't lead to a problem because currently the
> pointers used are all non-null. Nevertheless this patch addresses
> the reported problem.
>
> [...]
Here is the summary with links:
- [net-next] net: ipa: avoid a null pointer dereference
https://git.kernel.org/netdev/net-next/c/15b4f993d12b
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:[~2022-11-18 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 22:37 [PATCH net-next] net: ipa: avoid a null pointer dereference Alex Elder
2022-11-18 12:00 ` 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=166877282570.14131.14093782729381689956.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=caleb.connolly@linaro.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.