From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, horms@kernel.org, eric.dumazet@gmail.com,
syzbot+1fcd957a82e3a1baa94d@syzkaller.appspotmail.com,
jiri@nvidia.com
Subject: Re: [PATCH net] team: better TEAM_OPTION_TYPE_STRING validation
Date: Thu, 13 Feb 2025 16:50:35 +0000 [thread overview]
Message-ID: <173946543582.1295234.1199639571668692011.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250212134928.1541609-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 12 Feb 2025 13:49:28 +0000 you wrote:
> syzbot reported following splat [1]
>
> Make sure user-provided data contains one nul byte.
>
> [1]
> BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:633 [inline]
> BUG: KMSAN: uninit-value in string+0x3ec/0x5f0 lib/vsprintf.c:714
> string_nocheck lib/vsprintf.c:633 [inline]
> string+0x3ec/0x5f0 lib/vsprintf.c:714
> vsnprintf+0xa5d/0x1960 lib/vsprintf.c:2843
> __request_module+0x252/0x9f0 kernel/module/kmod.c:149
> team_mode_get drivers/net/team/team_core.c:480 [inline]
> team_change_mode drivers/net/team/team_core.c:607 [inline]
> team_mode_option_set+0x437/0x970 drivers/net/team/team_core.c:1401
> team_option_set drivers/net/team/team_core.c:375 [inline]
> team_nl_options_set_doit+0x1339/0x1f90 drivers/net/team/team_core.c:2662
> genl_family_rcv_msg_doit net/netlink/genetlink.c:1115 [inline]
> genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]
> genl_rcv_msg+0x1214/0x12c0 net/netlink/genetlink.c:1210
> netlink_rcv_skb+0x375/0x650 net/netlink/af_netlink.c:2543
> genl_rcv+0x40/0x60 net/netlink/genetlink.c:1219
> netlink_unicast_kernel net/netlink/af_netlink.c:1322 [inline]
> netlink_unicast+0xf52/0x1260 net/netlink/af_netlink.c:1348
> netlink_sendmsg+0x10da/0x11e0 net/netlink/af_netlink.c:1892
> sock_sendmsg_nosec net/socket.c:718 [inline]
> __sock_sendmsg+0x30f/0x380 net/socket.c:733
> ____sys_sendmsg+0x877/0xb60 net/socket.c:2573
> ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2627
> __sys_sendmsg net/socket.c:2659 [inline]
> __do_sys_sendmsg net/socket.c:2664 [inline]
> __se_sys_sendmsg net/socket.c:2662 [inline]
> __x64_sys_sendmsg+0x212/0x3c0 net/socket.c:2662
> x64_sys_call+0x2ed6/0x3c30 arch/x86/include/generated/asm/syscalls_64.h:47
> do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
Here is the summary with links:
- [net] team: better TEAM_OPTION_TYPE_STRING validation
https://git.kernel.org/netdev/net/c/5bef3ac184b5
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:[~2025-02-13 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 13:49 [PATCH net] team: better TEAM_OPTION_TYPE_STRING validation Eric Dumazet
2025-02-12 14:56 ` Jiri Pirko
2025-02-13 16:50 ` 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=173946543582.1295234.1199639571668692011.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+1fcd957a82e3a1baa94d@syzkaller.appspotmail.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.