public inbox for [email protected]
 help / color / mirror / Atom feed
From: Aleksandr Nogikh <[email protected]>
To: syzbot <[email protected]>
Cc: [email protected], [email protected],
	[email protected], [email protected],
	[email protected]
Subject: Re: [syzbot] [io-uring?] KASAN: use-after-free Read in io_worker_get
Date: Wed, 15 Mar 2023 13:17:23 +0100	[thread overview]
Message-ID: <CANp29Y4WhUTNjUF1BPKDcSzUFx4Jb2uMHRsuezSewWZ9czWwtA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

Looks reasonable

#syz fix: io_uring/io-wq: only free worker if it was allocated for creation


On Wed, Mar 15, 2023 at 6:35 AM syzbot
<[email protected]> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit e6db6f9398dadcbc06318a133d4c44a2d3844e61
> Author: Jens Axboe <[email protected]>
> 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=108bc2e2c80000
> start commit:   a689b938df39 Merge tag 'block-2023-01-06' of git://git.ker..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=33ad6720950f996d
> dashboard link: https://syzkaller.appspot.com/bug?extid=55cc59267340fad29512
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1532ef72480000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10b43f3a480000
>
> 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
>

      reply	other threads:[~2023-03-15 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  6:03 [syzbot] KASAN: use-after-free Read in io_worker_get syzbot
2023-01-09 13:08 ` Pavel Begunkov
2023-01-09 18:40   ` syzbot
2023-03-15  5:35 ` [syzbot] [io-uring?] " syzbot
2023-03-15 12:17   ` Aleksandr Nogikh [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=CANp29Y4WhUTNjUF1BPKDcSzUFx4Jb2uMHRsuezSewWZ9czWwtA@mail.gmail.com \
    [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