From: Matthew Wilcox <willy@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: now4yreal <now4yreal@foxmail.com>, Jan Kara <jack@suse.com>,
Viro <viro@zeniv.linux.org.uk>, Bacik <josef@toxicpanda.com>,
Stone <leocstone@gmail.com>, Sandeen <sandeen@redhat.com>,
Johnson <jeff.johnson@oss.qualcomm.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug Report] OOB-read BUG in HFS+ filesystem
Date: Mon, 14 Apr 2025 15:21:56 +0100 [thread overview]
Message-ID: <Z_0aBN-20w20-UiD@casper.infradead.org> (raw)
In-Reply-To: <20250414-behielt-erholen-e0cd10a4f7af@brauner>
On Mon, Apr 14, 2025 at 04:18:27PM +0200, Christian Brauner wrote:
> On Mon, Apr 14, 2025 at 09:45:25PM +0800, now4yreal wrote:
> > Dear Linux Security Maintainers,
> > I would like to report a OOB-read vulnerability in the HFS+ file
> > system, which I discovered using our in-house developed kernel fuzzer,
> > Symsyz.
>
> Bug reports from non-official syzbot instances are generally not
> accepted.
>
> hfs and hfsplus are orphaned filesystems since at least 2014. Bug
> reports for such filesystems won't receive much attention from the core
> maintainers.
>
> I'm very very close to putting them on the chopping block as they're
> slowly turning into pointless burdens.
I've tried asking some people who are long term Apple & Linux people,
but haven't been able to find anyone interested in becoming maintainer.
Let's drop both hfs & hfsplus. Ten years of being unmaintained is
long enough.
next prev parent reply other threads:[~2025-04-14 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 13:45 =?gb18030?B?bm93NHlyZWFs?=
2025-04-14 14:18 ` Christian Brauner
2025-04-14 14:21 ` Matthew Wilcox [this message]
2025-04-14 16:23 ` David Sterba
2025-04-15 7:52 ` Christian Brauner
2025-04-15 9:16 ` Johannes Thumshirn
2025-04-15 9:31 ` Christian Brauner
2025-04-15 10:23 ` Johannes Thumshirn
2025-04-15 11:25 ` Christian Brauner
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=Z_0aBN-20w20-UiD@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@kernel.org \
--cc=jack@suse.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=josef@toxicpanda.com \
--cc=leocstone@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=now4yreal@foxmail.com \
--cc=sandeen@redhat.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®