From: Jens Axboe <axboe@kernel.dk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
syzbot <syzbot+d3b704fabd7f02206294@syzkaller.appspotmail.com>,
io-uring@vger.kernel.org
Subject: Re: [syzbot] KASAN: use-after-free Read in fuse_dev_poll
Date: Tue, 24 Jan 2023 09:37:21 -0700 [thread overview]
Message-ID: <579d6d81-4f24-16e4-ee56-11089eae0164@kernel.dk> (raw)
In-Reply-To: <CAJfpegteWVfJ8CLATjhk7==iLmqyZT_ao8Hs2JaNKdbgceXZYw@mail.gmail.com>
On 1/24/23 9:29 AM, Miklos Szeredi wrote:
> Hi Jens,
>
> Forwarding, since it looks like io_uring is the culprit: vfs_poll() is
> called by io_poll_check_events() on an already released file.
We had a bad patch around that time, pretty sure that's what's
triggering this one too as it's not a recent kernel.
#syz invalid
--
Jens Axboe
prev parent reply other threads:[~2023-01-24 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 12:35 [syzbot] KASAN: use-after-free Read in fuse_dev_poll syzbot
2023-01-24 16:29 ` Miklos Szeredi
2023-01-24 16:37 ` Jens Axboe [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=579d6d81-4f24-16e4-ee56-11089eae0164@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=syzbot+d3b704fabd7f02206294@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