From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <syzbot+e0bd4e4815a910c0daa8@syzkaller.appspotmail.com>
Cc: <alex.aring@gmail.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-wpan@vger.kernel.org>,
<miquel.raynal@bootlin.com>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>, <stefan@datenfreihafen.org>,
<syzkaller-bugs@googlegroups.com>, <kuniyu@amazon.com>
Subject: Re: [syzbot] [wpan?] WARNING in cfg802154_switch_netns (2)
Date: Tue, 13 Aug 2024 12:52:44 -0700 [thread overview]
Message-ID: <20240813195244.23260-1-kuniyu@amazon.com> (raw)
In-Reply-To: <000000000000f4a1b7061f9421de@google.com>
From: syzbot <syzbot+e0bd4e4815a910c0daa8@syzkaller.appspotmail.com>
Date: Tue, 13 Aug 2024 10:42:25 -0700
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: ee9a43b7cfe2 Merge tag 'net-6.11-rc3' of git://git.kernel...
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=13da25d3980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e8a2eef9745ade09
> dashboard link: https://syzkaller.appspot.com/bug?extid=e0bd4e4815a910c0daa8
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
kstrdup() failed due to fault injection.
We may want to change the WARN_ON(1) in these functions
to net_warn_ratelimited() as we do so in do_setlink().
* __dev_change_net_namespace
* cfg802154_switch_netns
* cfg80211_switch_netns()
[ 141.438766][ T8054] FAULT_INJECTION: forcing a failure.
[ 141.438766][ T8054] name failslab, interval 1, probability 0, space 0, times 0
[ 141.453868][ T8054] CPU: 1 UID: 0 PID: 8054 Comm: syz.0.839 Not tainted 6.11.0-rc2-syzkaller-00111-gee9a43b7cfe2 #0
[ 141.464514][ T8054] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
[ 141.474602][ T8054] Call Trace:
[ 141.477906][ T8054] <TASK>
[ 141.480854][ T8054] dump_stack_lvl+0x241/0x360
[ 141.507418][ T8054] should_fail_ex+0x3b0/0x4e0
[ 141.512110][ T8054] should_failslab+0xac/0x100
[ 141.516785][ T8054] __kmalloc_node_track_caller_noprof+0xda/0x440
[ 141.523098][ T8054] ? device_rename+0xb5/0x1b0
[ 141.527767][ T8054] kstrdup+0x3a/0x80
[ 141.531651][ T8054] device_rename+0xb5/0x1b0
[ 141.536142][ T8054] cfg802154_switch_netns+0x1df/0x390
[ 141.541523][ T8054] nl802154_wpan_phy_netns+0x13d/0x210
[ 141.546984][ T8054] genl_rcv_msg+0xb14/0xec0
[...]
[ 141.801010][ T8054] </TASK>
[ 141.865238][ T8054] ------------[ cut here ]------------
[ 141.871127][ T8054] WARNING: CPU: 1 PID: 8054 at net/ieee802154/core.c:258 cfg802154_switch_netns+0x37f/0x390
next prev parent reply other threads:[~2024-08-13 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 17:42 syzbot
2024-08-13 19:52 ` Kuniyuki Iwashima [this message]
[not found] <AS4PR10MB5766C0B97CCA5D2A1D2F8CD0F5862@AS4PR10MB5766.EURPRD10.PROD.OUTLOOK.COM>
2024-08-13 17:56 ` syzbot
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=20240813195244.23260-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.org \
--cc=syzbot+e0bd4e4815a910c0daa8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@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
all inboxes | Powered by JetHome®