From: syzbot <syzbot+47dd250f527cb7bebf24@syzkaller.appspotmail.com>
To: arve@android.com, asml.silence@gmail.com, axboe@kernel.dk,
brauner@kernel.org, gregkh@linuxfoundation.org, hdanton@sina.com,
hridya@google.com, io-uring@vger.kernel.org,
joel@joelfernandes.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, maco@android.com,
surenb@google.com, syzkaller-bugs@googlegroups.com,
tkjos@android.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KASAN: use-after-free Read in filp_close
Date: Sun, 05 Jun 2022 11:29:08 -0700 [thread overview]
Message-ID: <000000000000fc2dfb05e0b7873b@google.com> (raw)
In-Reply-To: <YpzxhRLKyETOtUeH@zeniv-ca.linux.org.uk>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+47dd250f527cb7bebf24@syzkaller.appspotmail.com
Tested on:
commit: 6dda6985 fix the breakage in close_fd_get_file() calli..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.fd
kernel config: https://syzkaller.appspot.com/x/.config?x=d4042ecb71632a26
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
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2022-06-05 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000fd54f805e0351875@google.com>
2022-06-05 14:04 ` [syzbot] KASAN: use-after-free Read in filp_close syzbot
2022-06-05 16:15 ` Al Viro
2022-06-05 18:10 ` Al Viro
2022-06-05 18:29 ` 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=000000000000fc2dfb05e0b7873b@google.com \
--to=syzbot+47dd250f527cb7bebf24@syzkaller.appspotmail.com \
--cc=arve@android.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=hridya@google.com \
--cc=io-uring@vger.kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=surenb@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tkjos@android.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox