From: syzbot <syzbot+b3ba2408ce0c74bb9230@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] [io-uring?] KASAN: use-after-free Read in io_wq_worker_wake
Date: Mon, 13 Mar 2023 07:32:24 -0700 [thread overview]
Message-ID: <000000000000bd527205f6c8fa41@google.com> (raw)
In-Reply-To: <000000000000f0fb6005f1cfc17f@google.com>
syzbot suspects this issue was fixed by commit:
commit e6db6f9398dadcbc06318a133d4c44a2d3844e61
Author: Jens Axboe <axboe@kernel.dk>
Date: Sun Jan 8 17:39:17 2023 +0000
io_uring/io-wq: only free worker if it was allocated for creation
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113a76fac80000
start commit: 1fe4fd6f5cad Merge tag 'xfs-6.2-fixes-2' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8b79b14037065d92
dashboard link: https://syzkaller.appspot.com/bug?extid=b3ba2408ce0c74bb9230
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1388e5f2480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127f1aa4480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: io_uring/io-wq: only free worker if it was allocated for creation
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-03-13 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 7:31 [syzbot] KASAN: use-after-free Read in io_wq_worker_wake syzbot
2023-01-09 14:58 ` Jens Axboe
2023-01-09 19:33 ` syzbot
2023-01-09 17:56 ` syzbot
2023-03-13 14:32 ` syzbot [this message]
2023-03-13 14:38 ` [syzbot] [io-uring?] " 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=000000000000bd527205f6c8fa41@google.com \
--to=syzbot+b3ba2408ce0c74bb9230@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.