From: syzbot <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: Re: [syzbot] KASAN: use-after-free Read in create_worker_cb
Date: Mon, 29 Mar 2021 16:33:07 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: [email protected]
Tested on:
commit: 24996dbd io_uring: reg buffer overflow checks hardening
git tree: git://git.kernel.dk/linux-block for-5.13/io_uring
kernel config: https://syzkaller.appspot.com/x/.config?x=cbb3af9ca0d22f7a
dashboard link: https://syzkaller.appspot.com/bug?extid=099593561bbd1805b839
compiler:
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2021-03-29 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 19:54 [syzbot] KASAN: use-after-free Read in create_worker_cb syzbot
2021-03-29 19:56 ` Jens Axboe
2021-03-29 23:33 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox