From: Pavel Begunkov <[email protected]>
To: Palash Oswal <[email protected]>,
[email protected], [email protected]
Subject: Re: [RFC] Patch for null-ptr-deref read in io_uring_create 5.11.12
Date: Mon, 19 Apr 2021 11:33:34 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAGyP=7cWH6PsO=gbF0owuSXV7D18LgK=jP+wiPN-Q=VM29vKTg@mail.gmail.com>
On 4/17/21 8:56 AM, Palash Oswal wrote:
> Hello,
>
> I have been trying to decipher a bug that my local syzkaller instance
> discovered in the v5.11.12 stable tree. I have more details in [1].
> Could someone please review.
Can be, what is the hash of last commit you used? stable 5.11 is different
now, I'd guess it was fixed by
commit 0298ef969a110ca03654f0cea9b50e3f3b331acc
Author: Pavel Begunkov <[email protected]>
Date: Mon Mar 8 13:20:57 2021 +0000
io_uring: clean R_DISABLED startup mess
>
> [1] https://oswalpalash.com/exploring-null-ptr-deref-io-uring-submit/
> Signed-off-by: Palash Oswal <[email protected]>
> ---
> fs/io_uring.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 8b4213de9e08..00b35079b91a 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -8995,7 +8995,7 @@ static void io_disable_sqo_submit(struct io_ring_ctx *ctx)
> {
> mutex_lock(&ctx->uring_lock);
> ctx->sqo_dead = 1;
> - if (ctx->flags & IORING_SETUP_R_DISABLED)
> + if (ctx->flags & IORING_SETUP_R_DISABLED && ctx->sq_data)
> io_sq_offload_start(ctx);
> mutex_unlock(&ctx->uring_lock);
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-04-19 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 7:56 [RFC] Patch for null-ptr-deref read in io_uring_create 5.11.12 Palash Oswal
2021-04-19 10:33 ` Pavel Begunkov [this message]
2021-04-19 11:10 ` Palash Oswal
2021-04-19 11:22 ` Pavel Begunkov
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] \
/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