All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8a676a50d4eee2f21539@syzkaller.appspotmail.com>
To: davem@davemloft.net, eadavis@qq.com, hdanton@sina.com,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, reibax@gmail.com,
	richardcochran@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in ptp_release
Date: Sun, 10 Dec 2023 21:37:06 -0800	[thread overview]
Message-ID: <000000000000162818060c3553cc@google.com> (raw)
In-Reply-To: <000000000000ffc87a06086172a0@google.com>

syzbot suspects this issue was fixed by commit:

commit 1bea2c3e6df8caf45d18384abfb707f47e9ff993
Author: Edward Adam Davis <eadavis@qq.com>
Date:   Tue Nov 7 08:00:41 2023 +0000

    ptp: fix corrupted list in ptp_open

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=145ba76ce80000
start commit:   6bc986ab839c Merge tag 'nfs-for-6.7-1' of git://git.linux-..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=1ffa1cec3b40f3ce
dashboard link: https://syzkaller.appspot.com/bug?extid=8a676a50d4eee2f21539
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17cc14a8e80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11ade40f680000

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

#syz fix: ptp: fix corrupted list in ptp_open

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

  parent reply	other threads:[~2023-12-11  5:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 12:34 [syzbot] [net?] KASAN: slab-use-after-free Read in ptp_release syzbot
2023-11-01  2:51 ` syzbot
2023-11-01 16:03 ` syzbot
2023-11-01 22:21 ` syzbot
2023-12-11  5:37 ` syzbot [this message]
     [not found] <20231103120103.1304-1-hdanton@sina.com>
2023-11-03 12:21 ` syzbot

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=000000000000162818060c3553cc@google.com \
    --to=syzbot+8a676a50d4eee2f21539@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=eadavis@qq.com \
    --cc=hdanton@sina.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=reibax@gmail.com \
    --cc=richardcochran@gmail.com \
    --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.