From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, kuni1840@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v1 net 0/2] raw/ping: Fix locking in /proc/net/{raw,icmp}.
Date: Wed, 05 Apr 2023 02:00:19 +0000 [thread overview]
Message-ID: <168066001903.10193.5947973039322866412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230403194959.48928-1-kuniyu@amazon.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 3 Apr 2023 12:49:57 -0700 you wrote:
> The first patch fixes a NULL deref for /proc/net/raw and second one fixes
> the same issue for ping sockets.
>
> The first patch also converts hlist_nulls to hlist, but this is because
> the current code uses sk_nulls_for_each() for lockless readers, instead
> of sk_nulls_for_each_rcu() which adds memory barrier, but raw sockets
> does not use the nulls marker nor SLAB_TYPESAFE_BY_RCU in the first place.
>
> [...]
Here is the summary with links:
- [v1,net,1/2] raw: Fix NULL deref in raw_get_next().
https://git.kernel.org/netdev/net/c/0a78cf7264d2
- [v1,net,2/2] ping: Fix potentail NULL deref for /proc/net/icmp.
https://git.kernel.org/netdev/net/c/ab5fb73ffa01
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:[~2023-04-05 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 19:49 [PATCH v1 net 0/2] raw/ping: Fix locking in /proc/net/{raw,icmp} Kuniyuki Iwashima
2023-04-03 19:49 ` [PATCH v1 net 1/2] raw: Fix NULL deref in raw_get_next() Kuniyuki Iwashima
2023-04-04 1:46 ` Eric Dumazet
2023-04-04 2:46 ` Jason Xing
2023-04-04 4:07 ` Eric Dumazet
2023-04-04 6:56 ` Jason Xing
2023-04-04 7:23 ` Eric Dumazet
2023-04-04 7:34 ` Jason Xing
2023-04-03 19:49 ` [PATCH v1 net 2/2] ping: Fix potentail NULL deref for /proc/net/icmp Kuniyuki Iwashima
2023-04-04 1:47 ` Eric Dumazet
2023-04-05 2: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=168066001903.10193.5947973039322866412.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.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 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.