From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 83D38C001DC for ; Thu, 20 Jul 2023 18:00:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230211AbjGTSAJ (ORCPT ); Thu, 20 Jul 2023 14:00:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48350 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229609AbjGTSAI (ORCPT ); Thu, 20 Jul 2023 14:00:08 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D10B0270C; Thu, 20 Jul 2023 11:00:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=V7G2UtptYlwfwVXmCQnk4Mjk/yUqKgviUimViNIUGao=; b=APuLBZisvMr6cQw8KUoNNdpuMH BpT5J/c1XSPhDXrksvjXAixfS/BvGwt0RsKlTzcOKgWsSmYVJIZr2Kx1k2BZfobhgBng4kFQdoqUr lIAAgVrxtPhrO8wG68By//7CqCS1swkCl2dZVSduoiMFQgIok4rPGzIYGdLIahYNg3OV7ReHZ2dwY H5P0IAuC4uqBUbb8WItLwTsvqLsNDkPlSP5U12Csd8QukocOIfGcqi7BTMfJNjaCCs2qazoNqJBom fFrmqGJIoTzq3xz4xc+rPrWjCLGUlDnMbB5IuuT+OLwYKn2k89jCBhzJfCY2r5VaJAEDNn+TrPsDn /S8+glug==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1qMXwM-000JgO-RJ; Thu, 20 Jul 2023 17:59:50 +0000 Date: Thu, 20 Jul 2023 18:59:50 +0100 From: Matthew Wilcox To: John Paul Adrian Glaubitz Cc: Dmitry Vyukov , Viacheslav Dubeyko , Arnd Bergmann , Linus Torvalds , syzbot , Andrew Morton , christian.brauner@ubuntu.com, Damien Le Moal , Jeff Layton , Linux FS Devel , LKML , syzkaller-bugs@googlegroups.com, ZhangPeng , linux-m68k@lists.linux-m68k.org, debian-ports Subject: Re: [syzbot] [hfs?] WARNING in hfs_write_inode Message-ID: References: <5f45bb9a-5e00-48dd-82b0-46b19b1b98a3@app.fastmail.com> <2575F983-D170-4B79-A6BA-912D4ED2CC73@dubeyko.com> <46F233BB-E587-4F2B-AA62-898EB46C9DCE@dubeyko.com> <50D6A66B-D994-48F4-9EBA-360E57A37BBE@dubeyko.com> <2d0bd58fb757e7771d13f82050a546ec5f7be8de.camel@physik.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2d0bd58fb757e7771d13f82050a546ec5f7be8de.camel@physik.fu-berlin.de> Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote: > > 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. If they're so popular, then it should be no trouble to find somebody to volunteer to maintain those filesystems. Except they've been marked as orphaned since 2011 and effectively were orphaned several years before that (the last contribution I see from Roman Zippel is in 2008, and his last contribution to hfs was in 2006).