All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ad53b671c30ddaba634d@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, hayeswang@realtek.com,
	io-uring@vger.kernel.org, kuba@kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] KASAN: use-after-free Read in io_wqe_worker (2)
Date: Sat, 11 Mar 2023 07:15:25 -0800	[thread overview]
Message-ID: <000000000000ec64a805f6a158c3@google.com> (raw)
In-Reply-To: <0000000000009bff3c05f1ce87f1@google.com>

syzbot suspects this issue was fixed by commit:

commit 02767440e1dda9861a11ca1dbe0f19a760b1d5c2
Author: Hayes Wang <hayeswang@realtek.com>
Date:   Thu Jan 19 07:40:43 2023 +0000

    r8152: reduce the control transfer of rtl8152_get_version()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13284762c80000
start commit:   9b43a525db12 Merge tag 'nfs-for-6.2-2' of git://git.linux-..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=ff5cf657dd0e7643
dashboard link: https://syzkaller.appspot.com/bug?extid=ad53b671c30ddaba634d
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=160480ba480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14cddc6a480000

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

#syz fix: r8152: reduce the control transfer of rtl8152_get_version()

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

  parent reply	other threads:[~2023-03-11 15:15 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_wqe_worker (2) syzbot
2023-01-09 13:09 ` Pavel Begunkov
2023-01-09 18:55   ` syzbot
2023-03-11 15:15 ` syzbot [this message]
2023-03-15 12:20   ` [syzbot] [io-uring?] " Aleksandr Nogikh

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=000000000000ec64a805f6a158c3@google.com \
    --to=syzbot+ad53b671c30ddaba634d@syzkaller.appspotmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hayeswang@realtek.com \
    --cc=io-uring@vger.kernel.org \
    --cc=kuba@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.