From: syzbot <syzbot+85ede281798faf736677@syzkaller.appspotmail.com>
To: balbi@kernel.org, gregkh@linuxfoundation.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
mcgrof@kernel.org, syzkaller-bugs@googlegroups.com,
vvs@openvz.org
Subject: Re: [syzbot] [usb?] kernel BUG in register_netdevice
Date: Wed, 19 Aug 2026 23:59:05 -0700 [thread overview]
Message-ID: <6a86a5b9.4d75e56a.c9a88.0036.GAE@google.com> (raw)
In-Reply-To: <6a6a966c.86abc875.e5c3d.0053.GAE@google.com>
syzbot has bisected this issue to:
commit 425b9c7f51c98443db71ad679893725483b21196
Author: Vasily Averin <vvs@openvz.org>
Date: Mon May 2 12:15:51 2022 +0000
memcg: accounting for objects allocated for new netdevice
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1212ba25580000
start commit: e8bf40d15402 Merge tag 'chrome-platform-firmware-v7.3' of ..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1112ba25580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1612ba25580000
kernel config: https://syzkaller.appspot.com/x/.config?x=46f568dd8d795f6
dashboard link: https://syzkaller.appspot.com/bug?extid=85ede281798faf736677
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156b2549580000
Reported-by: syzbot+85ede281798faf736677@syzkaller.appspotmail.com
Fixes: 425b9c7f51c9 ("memcg: accounting for objects allocated for new netdevice")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2026-08-20 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 0:10 [syzbot] [usb?] kernel BUG in register_netdevice syzbot
2026-08-15 3:17 ` syzbot
2026-08-20 6:59 ` syzbot [this message]
2026-08-20 7:06 ` Greg KH
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=6a86a5b9.4d75e56a.c9a88.0036.GAE@google.com \
--to=syzbot+85ede281798faf736677@syzkaller.appspotmail.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vvs@openvz.org \
/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