All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+38769495e847cea2dcca@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, ducheng2@gmail.com,
	dvyukov@google.com, io-uring@vger.kernel.org,
	linux-kernel@vger.kernel.org, mpe@ellerman.id.au,
	paulmck@kernel.org, peterz@infradead.org, qais.yousef@arm.com,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] KASAN: use-after-free Read in __cpuhp_state_remove_instance
Date: Mon, 19 Apr 2021 07:41:09 -0700	[thread overview]
Message-ID: <0000000000000c120805c05452c0@google.com> (raw)
In-Reply-To: <0000000000000427db05bc3a2be3@google.com>

syzbot suspects this issue was fixed by commit:

commit 470ec4ed8c91b4db398ad607c700e9ce88365202
Author: Jens Axboe <axboe@kernel.dk>
Date:   Fri Feb 26 17:20:34 2021 +0000

    io-wq: fix double put of 'wq' in error path

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11e89cc5d00000
start commit:   cee407c5 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=8f67201de02a572b
dashboard link: https://syzkaller.appspot.com/bug?extid=38769495e847cea2dcca
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=154e360ad00000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: io-wq: fix double put of 'wq' in error path

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2021-04-19 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26  9:48 KASAN: use-after-free Read in __cpuhp_state_remove_instance syzbot
2021-02-26  9:58 ` Dmitry Vyukov
2021-02-26 21:33 ` syzbot
2021-02-26 22:06   ` Jens Axboe
2021-02-26 22:50 ` syzbot
2021-04-19 14:41 ` syzbot [this message]
2021-04-19 17:51   ` [syzbot] " 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=0000000000000c120805c05452c0@google.com \
    --to=syzbot+38769495e847cea2dcca@syzkaller.appspotmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=ducheng2@gmail.com \
    --cc=dvyukov@google.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=qais.yousef@arm.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    /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.