From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Matthew Wilcox <willy@infradead.org>, Dmitry Vyukov <dvyukov@google.com>
Cc: Viacheslav Dubeyko <slava@dubeyko.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
syzbot <syzbot+7bb7cd3595533513a9e7@syzkaller.appspotmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
christian.brauner@ubuntu.com,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Jeff Layton <jlayton@kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
ZhangPeng <zhangpeng362@huawei.com>,
linux-m68k@lists.linux-m68k.org,
debian-ports <debian-ports@lists.debian.org>
Subject: Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Date: Thu, 20 Jul 2023 19:50:47 +0200 [thread overview]
Message-ID: <2d0bd58fb757e7771d13f82050a546ec5f7be8de.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <ZLlvII/jMPTT32ef@casper.infradead.org>
Hello!
On Thu, 2023-07-20 at 18:30 +0100, Matthew Wilcox wrote:
> On Thu, Jul 20, 2023 at 05:27:57PM +0200, Dmitry Vyukov wrote:
> > On Thu, 5 Jan 2023 at 17:45, Viacheslav Dubeyko <slava@dubeyko.com> wrote:
> > > > On Wed, Jan 04, 2023 at 08:37:16PM -0800, Viacheslav Dubeyko wrote:
> > > > > Also, as far as I can see, available volume in report (mount_0.gz) somehow corrupted already:
> > > >
> > > > Syzbot generates deliberately-corrupted (aka fuzzed) filesystem images.
> > > > So basically, you can't trust anything you read from the disc.
> > > >
> > >
> > > If the volume has been deliberately corrupted, then no guarantee that file system
> > > driver will behave nicely. Technically speaking, inode write operation should never
> > > happened for corrupted volume because the corruption should be detected during
> > > b-tree node initialization time. If we would like to achieve such nice state of HFS/HFS+
> > > drivers, then it requires a lot of refactoring/implementation efforts. I am not sure that
> > > it is worth to do because not so many guys really use HFS/HFS+ as the main file
> > > system under Linux.
> >
> >
> > Most popular distros will happily auto-mount HFS/HFS+ from anything
> > inserted into USB (e.g. what one may think is a charger). This creates
> > interesting security consequences for most Linux users.
> > An image may also be corrupted non-deliberately, which will lead to
> > random memory corruptions if the kernel trusts it blindly.
>
> Then we should delete the HFS/HFS+ filesystems. They're orphaned in
> MAINTAINERS and if distros are going to do such a damnfool thing,
> then we must stop them.
Both HFS and HFS+ work perfectly fine. And if distributions or users are so
sensitive about security, it's up to them to blacklist individual features
in the kernel.
Both HFS and HFS+ have been the default filesystem on MacOS for 30 years
and I don't think it's justified to introduce such a hard compatibility
breakage just because some people are worried about theoretical evil
maid attacks.
HFS/HFS+ mandatory if you want to boot Linux on a classic Mac or PowerMac
and I don't think it's okay to break all these systems running Linux.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2023-07-20 17:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 14:24 [syzbot] [hfs?] WARNING in hfs_write_inode syzbot
2023-01-04 14:43 ` Arnd Bergmann
2023-01-04 19:06 ` Linus Torvalds
2023-01-04 22:33 ` Arnd Bergmann
2023-01-04 22:42 ` John Paul Adrian Glaubitz
2023-01-05 0:36 ` Viacheslav Dubeyko
2023-01-05 4:37 ` Viacheslav Dubeyko
2023-01-05 15:46 ` Matthew Wilcox
2023-01-05 16:45 ` Viacheslav Dubeyko
2023-07-20 15:27 ` Dmitry Vyukov
2023-07-20 17:30 ` Matthew Wilcox
2023-07-20 17:50 ` John Paul Adrian Glaubitz [this message]
2023-07-20 17:59 ` Matthew Wilcox
2023-07-20 18:27 ` Jeff Layton
2023-07-20 22:20 ` Dave Chinner
2023-07-21 1:03 ` Finn Thain
2023-07-21 1:11 ` Matthew Wilcox
2023-07-21 1:25 ` Michael Schmitz
2023-07-21 1:45 ` Finn Thain
2023-07-21 6:42 ` Kirsten Bromilow
2023-07-21 8:14 ` Finn Thain
2023-07-21 13:10 ` Theodore Ts'o
2023-07-20 21:38 ` Jeffrey Walton
2023-07-20 22:37 ` Matthew Wilcox
2023-07-20 22:53 ` Linus Torvalds
2023-07-21 1:28 ` Mike Hosken
2023-07-20 17:56 ` John Paul Adrian Glaubitz
2023-07-20 19:05 ` Michael Schmitz
2023-07-21 5:07 ` John Paul Adrian Glaubitz
2023-07-21 5:40 ` Eric W. Biederman
2023-01-05 21:34 ` Michael Schmitz
2023-01-05 21:53 ` Linus Torvalds
2023-01-05 23:46 ` Michael Schmitz
2023-01-06 7:09 ` Michael Schmitz
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=2d0bd58fb757e7771d13f82050a546ec5f7be8de.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=christian.brauner@ubuntu.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=debian-ports@lists.debian.org \
--cc=dvyukov@google.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=slava@dubeyko.com \
--cc=syzbot+7bb7cd3595533513a9e7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
--cc=zhangpeng362@huawei.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).