From: syzbot <syzbot+8836466a79f4175961b0@syzkaller.appspotmail.com>
To: axboe@kernel.dk, changbin.du@intel.com,
christian.brauner@ubuntu.com, daniel@iogearbox.net,
davem@davemloft.net, edumazet@google.com, hkallweit1@gmail.com,
kuba@kernel.org, linux-block@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 set_task_ioprio
Date: Tue, 21 Dec 2021 01:52:08 -0800 [thread overview]
Message-ID: <00000000000066073805d3a4f598@google.com> (raw)
In-Reply-To: <000000000000c70eef05d39f42a5@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=10620fcdb00000
start commit: 07f8c60fe60f Add linux-next specific files for 20211220
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=12620fcdb00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14620fcdb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2060504830b9124a
dashboard link: https://syzkaller.appspot.com/bug?extid=8836466a79f4175961b0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12058fcbb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17141adbb00000
Reported-by: syzbot+8836466a79f4175961b0@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
next parent reply other threads:[~2021-12-21 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000c70eef05d39f42a5@google.com>
2021-12-21 9:52 ` syzbot [this message]
2021-12-21 10:44 ` [syzbot] general protection fault in set_task_ioprio Eric Dumazet
2021-12-21 15:25 ` Jens Axboe
2021-12-21 16:03 ` Eric Dumazet
2021-12-21 16:30 ` Jens Axboe
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=00000000000066073805d3a4f598@google.com \
--to=syzbot+8836466a79f4175961b0@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=changbin.du@intel.com \
--cc=christian.brauner@ubuntu.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yajun.deng@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).