From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+8836466a79f4175961b0@syzkaller.appspotmail.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in set_task_ioprio
Date: Mon, 20 Dec 2021 20:34:40 -0700 [thread overview]
Message-ID: <7ded6b2a-1f95-73a2-c074-2841dd5aaf96@kernel.dk> (raw)
In-Reply-To: <000000000000c70eef05d39f42a5@google.com>
On 12/20/21 8:04 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 07f8c60fe60f Add linux-next specific files for 20211220
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1355d295b00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2060504830b9124a
> dashboard link: https://syzkaller.appspot.com/bug?extid=8836466a79f4175961b0
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12058fcbb00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17141adbb00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+8836466a79f4175961b0@syzkaller.appspotmail.com
#syz test git://git.kernel.dk/linux-block for-next
--
Jens Axboe
next prev parent reply other threads:[~2021-12-21 3:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 3:04 [syzbot] general protection fault in set_task_ioprio syzbot
2021-12-21 3:34 ` Jens Axboe [this message]
2021-12-21 5:21 ` syzbot
2021-12-21 9:52 ` syzbot
2021-12-21 10:44 ` 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=7ded6b2a-1f95-73a2-c074-2841dd5aaf96@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+8836466a79f4175961b0@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