From: Jens Axboe <[email protected]>
To: Palash Oswal <[email protected]>
Cc: [email protected], [email protected],
Hillf Danton <[email protected]>,
Pavel Begunkov <[email protected]>,
[email protected]
Subject: Re: BUG: soft lockup in corrupted
Date: Fri, 5 Mar 2021 07:11:16 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAGyP=7eHKPdST4sVEKQZ9fZEhoT5MOMH2FZjzXVb6_SzSwGaAg@mail.gmail.com>
On Mar 4, 2021, at 10:06 PM, Palash Oswal <[email protected]> wrote:
>
> Hello,
>
> I was running syzkaller and I found the following issue :
> Head Commit : 27e543cca13fab05689b2d0d61d200a83cfb00b6 ( v5.11.2 )
> Git Tree : stable
>
> Console logs:
> watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [syz-executor497:423]
> Modules linked in:
> CPU: 0 PID: 423 Comm: syz-executor497 Not tainted 5.11.2 #13
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1 04/01/2014
> RIP: 0010:__io_cqring_events fs/io_uring.c:1732 [inline]
> RIP: 0010:io_cqring_events fs/io_uring.c:2399 [inline]
> RIP: 0010:io_should_wake fs/io_uring.c:7190 [inline]
> RIP: 0010:io_cqring_wait fs/io_uring.c:7283 [inline]
> RIP: 0010:__do_sys_io_uring_enter+0x6b9/0x1040 fs/io_uring.c:9389
> Code: 00 00 e8 ea 9a cd ff 31 ff 44 89 e6 e8 30 9d cd ff 45 85 e4 0f
> 85 5c 08 00 00 e8 d2 9a cd ff 48 8b 5d c0 48 8b 83 c0 00 00 00 <8b> 88
> 80 00 00 00 8b 83 00 02 00 00 29 c8 8b 4d c8 89 c7 89 85 78
> watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [syz-executor497:416]
> RSP: 0018:ffffc900001efe58 EFLAGS: 00000293
https://git.kernel.dk/cgit/linux-block/commit/?h=io_uring-5.12&id=701b8b187525e3b90cbcab4dbc073f42dbcc4059
—
Jens Axboe
prev parent reply other threads:[~2021-03-05 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 5:06 BUG: soft lockup in corrupted Palash Oswal
2021-03-05 14:11 ` Jens Axboe [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 \
[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