From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+47dd250f527cb7bebf24@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in filp_close
Date: Sun, 5 Jun 2022 11:02:50 +0000 [thread overview]
Message-ID: <YpyNWgSXNityT14C@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <00000000000063ee3105e0af6e6e@google.com>
On Sun, Jun 05, 2022 at 01:49:19AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 952923ddc011 Merge tag 'pull-18-rc1-work.namei' of git://g..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=173fb6dbf00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3096247591885bfa
> dashboard link: https://syzkaller.appspot.com/bug?extid=47dd250f527cb7bebf24
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114f7bcdf00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1659a94ff00000
_Very_ interesting. Has anything of that sort been observed on -next?
Because everything in that branch had been present there since at least
January.
next prev parent reply other threads:[~2022-06-05 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 6:52 [syzbot] KASAN: use-after-free Read in filp_close syzbot
2022-06-05 8:49 ` syzbot
2022-06-05 11:02 ` Al Viro [this message]
2022-06-05 14:04 ` syzbot
2022-06-05 16:15 ` Al Viro
2022-06-05 18:10 ` Al Viro
2022-06-05 18:29 ` syzbot
[not found] <20220605113753.5943-1-hdanton@sina.com>
2022-06-05 14:35 ` 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=YpyNWgSXNityT14C@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+47dd250f527cb7bebf24@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox