From: syzbot <syzbot+953a33deaf38c66a915e@syzkaller•appspotmail.com>
To: benjamin.tissoires@redhat•com, changbin.du@intel•com,
christian.brauner@ubuntu•com, daniel@iogearbox•net,
davem@davemloft•net, edumazet@google•com, hkallweit1@gmail•com,
jikos@kernel•org, kuba@kernel•org, linux-input@vger•kernel.org,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
syzkaller-bugs@googlegroups•com, yajun.deng@linux•dev
Subject: Re: [syzbot] general protection fault in hidraw_release
Date: Wed, 02 Feb 2022 02:17:08 -0800 [thread overview]
Message-ID: <000000000000f82ecc05d706513d@google.com> (raw)
In-Reply-To: <0000000000000560cc05d4bce058@google.com>
syzbot has bisected this issue to:
commit e4b8954074f6d0db01c8c97d338a67f9389c042f
Author: Eric Dumazet <edumazet@google•com>
Date: Tue Dec 7 01:30:37 2021 +0000
netlink: add net device refcount tracker to struct ethnl_req_info
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15179fa8700000
start commit: 9f7fb8de5d9b Merge tag 'spi-fix-v5.17-rc2' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17179fa8700000
console output: https://syzkaller.appspot.com/x/log.txt?x=13179fa8700000
kernel config: https://syzkaller.appspot.com/x/.config?x=3e56c9b92aaaee24
dashboard link: https://syzkaller.appspot.com/bug?extid=953a33deaf38c66a915e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15fff530700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=106469f0700000
Reported-by: syzbot+953a33deaf38c66a915e@syzkaller•appspotmail.com
Fixes: e4b8954074f6 ("netlink: add net device refcount tracker to struct ethnl_req_info")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2022-02-02 10:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000000560cc05d4bce058@google.com>]
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=000000000000f82ecc05d706513d@google.com \
--to=syzbot+953a33deaf38c66a915e@syzkaller$(echo .)appspotmail.com \
--cc=benjamin.tissoires@redhat$(echo .)com \
--cc=changbin.du@intel$(echo .)com \
--cc=christian.brauner@ubuntu$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=jikos@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-input@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=yajun.deng@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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