From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Christian Brauner <brauner@kernel.org>
Cc: David Sterba <dsterba@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
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: Tue, 15 Apr 2025 10:23:27 +0000 [thread overview]
Message-ID: <8bd5e290-cfda-4735-a907-27611d1aac67@wdc.com> (raw)
In-Reply-To: <20250415-razzia-umverteilen-4e8864b62583@brauner>
On 15.04.25 11:31, Christian Brauner wrote:
> On Tue, Apr 15, 2025 at 09:16:58AM +0000, Johannes Thumshirn wrote:
>> On 15.04.25 09:52, Christian Brauner wrote:
>>> Ok, I'm open to trying. I'm adding a deprecation message when initating
>>> a new hfs{plus} context logged to dmesg and then we can try and remove
>>> it by the end of the year.
>>>
>>>
>>
>> Just a word of caution though, (at least Intel) Macs have their EFI ESP
>> partition on HFS+ instead of FAT. I don't own an Apple Silicon Mac so I
>> can't check if it's there as well.
>
> Yeah, someone mentioned that. Well, then we hopefully have someone
> stepping up to for maintainership.
>
I hope you aren't considering me here :D. I'm lacking the time to
volunteer as a Maintainer but I can offer to look into some fixes.
next prev parent reply other threads:[~2025-04-15 10:23 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
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 [this message]
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=8bd5e290-cfda-4735-a907-27611d1aac67@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=brauner@kernel.org \
--cc=dsterba@suse.cz \
--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=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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®