From: Matthew Wilcox <willy@infradead.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: Hui Guo <guohui.study@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Ingo Molnar <mingo@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Uros Bizjak <ubizjak@gmail.com>,
Carlos Llamas <cmllamas@google.com>, Jens Axboe <axboe@kernel.dk>,
Pankaj Raghav <p.raghav@samsung.com>,
Ryusuke Konishi <konishi.ryusuke@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: stack-out-of-bounds Write in end_buffer_read_sync
Date: Tue, 20 Aug 2024 05:04:17 +0100 [thread overview]
Message-ID: <ZsQVwUVdR5jQOPFJ@casper.infradead.org> (raw)
In-Reply-To: <CANp29Y4UGksKhXi3CG5F=E2JOTLAiW4MuHirWfLAs2WG4zygCw@mail.gmail.com>
On Mon, Aug 19, 2024 at 03:28:13PM +0200, Aleksandr Nogikh wrote:
> On Mon, Aug 19, 2024 at 2:54 PM Hui Guo <guohui.study@gmail.com> wrote:
> >
> > Hi Kernel Maintainers,
> > Our tool found the following kernel bug "KASAN: stack-out-of-bounds
> > Write in end_buffer_read_sync" on:
>
> Please note that the bug was already reported by syzbot in 2022:
> https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
> https://lore.kernel.org/all/0000000000005b04fa05dd71e0e0@google.com/T/
Oh, syzbot was more useful than Hui Guo. It pointed out that it's
an NTFS problem, so nobody cared. I'll go back to not caring.
prev parent reply other threads:[~2024-08-20 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 12:50 Hui Guo
2024-08-19 13:22 ` Matthew Wilcox
2024-08-19 13:28 ` Aleksandr Nogikh
2024-08-20 4:04 ` Matthew Wilcox [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=ZsQVwUVdR5jQOPFJ@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=guohui.study@gmail.com \
--cc=jack@suse.cz \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=nogikh@google.com \
--cc=p.raghav@samsung.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ubizjak@gmail.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
all inboxes | Powered by JetHome®