From: patchwork-bot+netdevbpf@kernel.org
To: Karsten Graul <kgraul@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, hca@linux.ibm.com,
alibuda@linux.alibaba.com
Subject: Re: [PATCH net 0/3] net/smc: fixes 2022-04-08
Date: Tue, 12 Apr 2022 01:40:13 +0000 [thread overview]
Message-ID: <164972761322.2554.16742103046786911320.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220408151035.1044701-1-kgraul@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 8 Apr 2022 17:10:32 +0200 you wrote:
> Please apply the following patches to netdev's net tree.
>
> Patch 1 fixes two usages of snprintf() with non null-terminated
> string which results into an out-of-bounds read.
> Pach 2 fixes a syzbot finding where a pointer check was missed
> before the call to dev_name().
> Patch 3 fixes a crash when already released memory is used as
> a function pointer.
>
> [...]
Here is the summary with links:
- [net,1/3] net/smc: use memcpy instead of snprintf to avoid out of bounds read
https://git.kernel.org/netdev/net/c/b1871fd48efc
- [net,2/3] net/smc: Fix NULL pointer dereference in smc_pnet_find_ib()
https://git.kernel.org/netdev/net/c/d22f4f977236
- [net,3/3] net/smc: Fix af_ops of child socket pointing to released memory
https://git.kernel.org/netdev/net/c/49b7d376abe5
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-04-12 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 15:10 [PATCH net 0/3] net/smc: fixes 2022-04-08 Karsten Graul
2022-04-08 15:10 ` [PATCH net 1/3] net/smc: use memcpy instead of snprintf to avoid out of bounds read Karsten Graul
2022-04-08 15:10 ` [PATCH net 2/3] net/smc: Fix NULL pointer dereference in smc_pnet_find_ib() Karsten Graul
2022-04-08 15:10 ` [PATCH net 3/3] net/smc: Fix af_ops of child socket pointing to released memory Karsten Graul
2022-04-11 8:38 ` D. Wythe
2022-04-12 1:40 ` 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=164972761322.2554.16742103046786911320.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@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