All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6805087452d72929404e@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_cqring_event_overflow
Date: Thu, 12 Jan 2023 18:51:18 -0800	[thread overview]
Message-ID: <000000000000c7bf6a05f21c4e23@google.com> (raw)
In-Reply-To: <746dc294-385c-3ebb-6b8e-7e01e9d54df5@gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+6805087452d72929404e@syzkaller.appspotmail.com

Tested on:

commit:         7b9484d4 io_uring: lock overflowing for IOPOLL
git tree:       https://github.com/isilence/linux.git overflow-lock
console output: https://syzkaller.appspot.com/x/log.txt?x=177064a6480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5bdd5369dfff2192
dashboard link: https://syzkaller.appspot.com/bug?extid=6805087452d72929404e
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2023-01-13  2:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 10:20 [syzbot] WARNING in io_cqring_event_overflow syzbot
2023-01-12 10:37 ` Pavel Begunkov
2023-01-12 10:56   ` syzbot
2023-01-12 15:27     ` Jens Axboe
2023-01-12 18:11     ` Pavel Begunkov
2023-01-13  2:51       ` syzbot [this message]
2023-01-13  3:10       ` 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=000000000000c7bf6a05f21c4e23@google.com \
    --to=syzbot+6805087452d72929404e@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.