From: syzbot <syzbot+00e15cda746c5bc70e24@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, deller@gmx.de,
gregkh@linuxfoundation.org, hdanton@sina.com,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] WARNING in io_ring_exit_work
Date: Mon, 29 May 2023 00:58:39 -0700 [thread overview]
Message-ID: <0000000000005b688105fcd074af@google.com> (raw)
In-Reply-To: <0000000000005225a605bd97fa64@google.com>
syzbot suspects this issue was fixed by commit:
commit d808459b2e31bd5123a14258a7a529995db974c8
Author: Helge Deller <deller@gmx.de>
Date: Thu Feb 16 08:09:38 2023 +0000
io_uring: Adjust mapping wrt architecture aliasing requirements
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=145bb249280000
start commit: 7c6984405241 Merge tag 'iommu-fixes-v6.2-rc3' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2b6ecad960fc703e
dashboard link: https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d5e97e480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1407c8da480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: io_uring: Adjust mapping wrt architecture aliasing requirements
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-05-29 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 19:08 [syzbot] WARNING in io_ring_exit_work syzbot
2021-08-06 7:02 ` syzbot
2021-08-06 9:20 ` Pavel Begunkov
2021-08-06 10:33 ` syzbot
2021-08-06 15:21 ` syzbot
2023-05-29 7:58 ` syzbot [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=0000000000005b688105fcd074af@google.com \
--to=syzbot+00e15cda746c5bc70e24@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=deller@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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.