From: Jann Horn <[email protected]>
To: Jens Axboe <[email protected]>,
syzbot <[email protected]>
Cc: io-uring <[email protected]>,
linux-fsdevel <[email protected]>,
kernel list <[email protected]>,
syzkaller-bugs <[email protected]>,
Al Viro <[email protected]>
Subject: Re: INFO: trying to register non-static key in io_cqring_overflow_flush
Date: Thu, 28 Nov 2019 16:29:03 +0100 [thread overview]
Message-ID: <CAG48ez09ZN2v2rTvnSgybrZu7BAa28vcnkcOU=Z7549rbpqz1A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Thu, Nov 28, 2019 at 4:19 PM Jens Axboe <[email protected]> wrote:
> On 11/28/19 12:35 AM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: d7688697 Merge tag 'for-linus' of git://git.kernel.org/pub..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=145e5fcee00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=12f2051e3d8cdb3f
> > dashboard link: https://syzkaller.appspot.com/bug?extid=be9e13497969768c0e6e
> > compiler: clang version 9.0.0 (/home/glider/llvm/clang
> > 80fee25776c2fb61e74c1ecb1a523375c2500b69)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=146c517ae00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16550b12e00000
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: [email protected]
>
> This is the same as:
>
> [email protected]
syzbot listens to specific commands, see
<https://github.com/google/syzkaller/blob/master/docs/syzbot.md#status>
(linked in the report):
#syz dup: INFO: trying to register non-static key in io_cqring_ev_posted
prev parent reply other threads:[~2019-11-28 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 8:35 INFO: trying to register non-static key in io_cqring_overflow_flush syzbot
2019-11-28 15:18 ` Jens Axboe
2019-11-28 15:29 ` Jann Horn [this message]
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='CAG48ez09ZN2v2rTvnSgybrZu7BAa28vcnkcOU=Z7549rbpqz1A@mail.gmail.com' \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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