From: syzbot <syzbot+de1c7d68a10e3f123bdd@syzkaller.appspotmail.com>
To: cratiu@nvidia.com, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, kuba@kernel.org, kuniyu@amazon.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, sdf@fomichev.me,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] general protection fault in rtnl_create_link
Date: Sun, 13 Apr 2025 20:07:06 -0700 [thread overview]
Message-ID: <67fc7bda.050a0220.2970f9.03b2.GAE@google.com> (raw)
In-Reply-To: <20250414023048.44721-1-kuniyu@amazon.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
Tested on:
commit: 8c941f14 Merge branch 'there-are-some-bugfix-for-hibmc..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=15bab398580000
kernel config: https://syzkaller.appspot.com/x/.config?x=eecd7902e39d7933
dashboard link: https://syzkaller.appspot.com/bug?extid=de1c7d68a10e3f123bdd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1661c0cc580000
next prev parent reply other threads:[~2025-04-14 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 2:14 [syzbot] [net?] general protection fault in rtnl_create_link syzbot
2025-04-14 2:30 ` Kuniyuki Iwashima
2025-04-14 3:07 ` syzbot [this message]
2025-04-14 17:37 ` Jakub Kicinski
2025-04-14 18:01 ` Kuniyuki Iwashima
2025-04-14 18:15 ` Jakub Kicinski
2025-04-14 18:23 ` Kuniyuki Iwashima
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=67fc7bda.050a0220.2970f9.03b2.GAE@google.com \
--to=syzbot+de1c7d68a10e3f123bdd@syzkaller.appspotmail.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--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 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.