From: syzbot <syzbot+9704e6f099d952508943@syzkaller.appspotmail.com>
To: davem@davemloft.net, eadavis@qq.com, eadavis@sina.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, reibax@gmail.com,
richardcochran@gmail.com, syzkaller-bugs@googlegroups.com,
twuufnxlz@gmail.com, wojciech.drewek@intel.com
Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in ptp_read
Date: Sun, 10 Dec 2023 13:38:04 -0800 [thread overview]
Message-ID: <000000000000e08cbb060c2ea1ca@google.com> (raw)
In-Reply-To: <0000000000002e8d4a06085267f3@google.com>
syzbot suspects this issue was fixed by commit:
commit b714ca2ccf6a90733f6ceb14abb6ce914f8832c3
Author: Edward Adam Davis <eadavis@qq.com>
Date: Tue Nov 7 08:00:40 2023 +0000
ptp: ptp_read should not release queue
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10477d6ce80000
start commit: 4bbdb725a36b Merge tag 'iommu-updates-v6.7' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=beb32a598fd79db9
dashboard link: https://syzkaller.appspot.com/bug?extid=9704e6f099d952508943
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17233388e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a3f898e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ptp: ptp_read should not release queue
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-12-10 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 18:37 [syzbot] [net?] KASAN: slab-use-after-free Read in ptp_read syzbot
2023-10-23 2:46 ` [PATCH] ptp: ptp_read should not release queue Edward AD
2023-10-23 9:01 ` Drewek, Wojciech
2023-10-23 9:55 ` [PATCH net] " Edward AD
2023-10-23 16:33 ` Jakub Kicinski
2023-10-24 0:34 ` Edward AD
2023-10-24 1:49 ` Jakub Kicinski
2023-10-23 16:32 ` [PATCH] " Jakub Kicinski
2023-12-10 21:38 ` syzbot [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=000000000000e08cbb060c2ea1ca@google.com \
--to=syzbot+9704e6f099d952508943@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=eadavis@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 \
--cc=twuufnxlz@gmail.com \
--cc=wojciech.drewek@intel.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.