All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7df055631cd1be4586fd@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in io_sync_cancel
Date: Wed, 21 Dec 2022 08:10:29 -0800	[thread overview]
Message-ID: <00000000000084d53b05f058cabc@google.com> (raw)
In-Reply-To: <7c89b1c8-f012-3965-ab77-3bc19b3cedaa@kernel.dk>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in corrupted

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P5778 } 2634 jiffies s: 2893 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):


Tested on:

commit:         071531e9 io_uring/cancel: mark task running before re-..
git tree:       git://git.kernel.dk/linux.git io_uring-6.2
console output: https://syzkaller.appspot.com/x/log.txt?x=13042ae8480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2edd87fe5cbdf43f
dashboard link: https://syzkaller.appspot.com/bug?extid=7df055631cd1be4586fd
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Note: no patches were applied.

  reply	other threads:[~2022-12-21 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21  6:03 [syzbot] WARNING in io_sync_cancel syzbot
2022-12-21 14:15 ` Jens Axboe
2022-12-21 15:17   ` syzbot
2022-12-21 15:44     ` Jens Axboe
2022-12-21 16:10       ` syzbot [this message]
2022-12-21 20:41         ` Jens Axboe
2022-12-22  5:52           ` syzbot
2022-12-22 16:45             ` Jens Axboe
     [not found] <20221221072129.1698-1-hdanton@sina.com>
2022-12-21  9:04 ` syzbot

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=00000000000084d53b05f058cabc@google.com \
    --to=syzbot+7df055631cd1be4586fd@syzkaller.appspotmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.