From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, dsahern@kernel.org,
netdev@vger.kernel.org, edumazet@google.com,
syzkaller@googlegroups.com
Subject: Re: [PATCH net] ipv4: raw: lock the socket in raw_bind()
Date: Thu, 27 Jan 2022 14:20:09 +0000 [thread overview]
Message-ID: <164329320946.24382.9714626868081279512.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220127005116.1268532-1-eric.dumazet@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 26 Jan 2022 16:51:16 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> For some reason, raw_bind() forgot to lock the socket.
>
> BUG: KCSAN: data-race in __ip4_datagram_connect / raw_bind
>
> write to 0xffff8881170d4308 of 4 bytes by task 5466 on cpu 0:
> raw_bind+0x1b0/0x250 net/ipv4/raw.c:739
> inet_bind+0x56/0xa0 net/ipv4/af_inet.c:443
> __sys_bind+0x14b/0x1b0 net/socket.c:1697
> __do_sys_bind net/socket.c:1708 [inline]
> __se_sys_bind net/socket.c:1706 [inline]
> __x64_sys_bind+0x3d/0x50 net/socket.c:1706
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> [...]
Here is the summary with links:
- [net] ipv4: raw: lock the socket in raw_bind()
https://git.kernel.org/netdev/net/c/153a0d187e76
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-01-27 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 0:51 [PATCH net] ipv4: raw: lock the socket in raw_bind() Eric Dumazet
2022-01-27 14:20 ` 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=164329320946.24382.9714626868081279512.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.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;
as well as URLs for NNTP newsgroup(s).