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] KASAN: use-after-free Read in io_wq_worker_wake
Date: Mon, 09 Jan 2023 09:56:18 -0800 [thread overview]
Message-ID: <000000000000f328e405f1d87b38@google.com> (raw)
In-Reply-To: <000000000000f0fb6005f1cfc17f@google.com>
syzbot has bisected this issue to:
commit af82425c6a2d2f347c79b63ce74fca6dc6be157f
Author: Jens Axboe <axboe@kernel.dk>
Date: Mon Jan 2 23:49:46 2023 +0000
io_uring/io-wq: free worker if task_work creation is canceled
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12cda5d2480000
start commit: 1fe4fd6f5cad Merge tag 'xfs-6.2-fixes-2' of git://git.kern..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11cda5d2480000
console output: https://syzkaller.appspot.com/x/log.txt?x=16cda5d2480000
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
Reported-by: syzbot+b3ba2408ce0c74bb9230@syzkaller.appspotmail.com
Fixes: af82425c6a2d ("io_uring/io-wq: free worker if task_work creation is canceled")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-09 18:06 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 [this message]
2023-03-13 14:32 ` [syzbot] [io-uring?] " syzbot
2023-03-13 14:38 ` 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=000000000000f328e405f1d87b38@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.