From: syzbot <syzbot+005037419ebdf14e1d87@syzkaller.appspotmail.com>
To: dan.carpenter@oracle.com, hdanton@sina.com,
hverkuil-cisco@xs4all.nl, igormtorrente@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
mudongliangabcd@gmail.com, stephen.s.brennan@oracle.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KASAN: use-after-free Read in em28xx_close_extension
Date: Fri, 01 Oct 2021 01:55:07 -0700 [thread overview]
Message-ID: <00000000000052dbbf05cd46b81e@google.com> (raw)
In-Reply-To: <000000000000d068cf05c716264c@google.com>
syzbot suspects this issue was fixed by commit:
commit 0766ec82e5fb26fc5dc6d592bc61865608bdc651
Author: Stephen Brennan <stephen.s.brennan@oracle.com>
Date: Wed Sep 1 17:51:41 2021 +0000
namei: Fix use after free in kern_path_locked
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17bf2a03300000
start commit: fa54d366a6e4 Merge tag 'acpi-5.14-rc7' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=96f0602203250753
dashboard link: https://syzkaller.appspot.com/bug?extid=005037419ebdf14e1d87
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c086c5300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12950bee300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: namei: Fix use after free in kern_path_locked
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-10-01 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 14:27 [syzbot] KASAN: use-after-free Read in em28xx_close_extension syzbot
[not found] ` <20210727100151.2051-1-hdanton@sina.com>
2021-07-27 14:14 ` Dan Carpenter
2021-07-27 15:13 ` Dongliang Mu
2021-07-27 15:33 ` Dan Carpenter
2021-07-28 13:39 ` Dan Carpenter
2021-10-01 8:55 ` 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=00000000000052dbbf05cd46b81e@google.com \
--to=syzbot+005037419ebdf14e1d87@syzkaller.appspotmail.com \
--cc=dan.carpenter@oracle.com \
--cc=hdanton@sina.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=igormtorrente@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=stephen.s.brennan@oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.