From: Matthew Wilcox <willy@infradead.org>
To: Strforexc yn <strforexc@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: KASAN: slab-out-of-bounds Read in hfsplus_bnode_read in v6.14-rc4 kernel
Date: Mon, 3 Mar 2025 03:59:32 +0000 [thread overview]
Message-ID: <Z8UpJLt_k7r_49ED@casper.infradead.org> (raw)
In-Reply-To: <CA+HokZpS9NC4ck36kK33pRha4RCM5cUr2nTakpUzO514C-w9CA@mail.gmail.com>
On Mon, Mar 03, 2025 at 09:52:56AM +0800, Strforexc yn wrote:
> KASAN detects a slab-out-of-bounds read of size 8 at address
> ffff888044c23ac0 in hfsplus_bnode_read (fs/hfsplus/bnode.c:32) during
> a rename operation. Preceding logs report: hfsplus: request for
> non-existent node 65030 in B*Tree.
hfsplus is unmaintained and rarely used. I'd rather delete it than
spend any time analysing this report.
prev parent reply other threads:[~2025-03-03 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 1:52 KASAN: slab-out-of-bounds Read in hfsplus_bnode_read in v6.14-rc4 kernel Strforexc yn
2025-03-03 3:59 ` 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=Z8UpJLt_k7r_49ED@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=strforexc@gmail.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;
as well as URLs for NNTP newsgroup(s).