Received: by 2002:a05:6358:7058:b0:131:369:b2a3 with SMTP id 24csp9925314rwp; Thu, 20 Jul 2023 11:46:36 -0700 (PDT) X-Google-Smtp-Source: APBJJlExpZNGx6EA0bFr19SFXfHPpVl0WYZTtobK6j/PCCDuym6EuW/JPF9Re/y3NL01B7G7tUVv X-Received: by 2002:a17:90a:e014:b0:262:e912:5c75 with SMTP id u20-20020a17090ae01400b00262e9125c75mr322366pjy.13.1689878796028; Thu, 20 Jul 2023 11:46:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689878796; cv=none; d=google.com; s=arc-20160816; b=y2MM1D2cu4lJYx7xMZBlAw49SQIvdJI+9QuTv1a6G99QunX3idJG2L27k05F7yDRym OX+w2oyXNDLsCzG5eMQQKHT93G5e2ZuPO3sYhyTZJp5I4g7mVLz8l47+FXROwn+TNmxK RtKcP9Li1DA/jE9cxc6S1nRPSq6YCN3cD9dlNPPdyHE0aODwGMB4rBIRKPelHPiCU1Qu UosUyGw+l0kYsQBRo080JZ2vuuJ19X29ErJsEfA28PzXtj5Uof9lQco0Us7MIWj7yV8z a2GIhCz3QdgmzWfatwYSloGbnZE6PiDRrF/sQ4Um9Ib3K9EV8aMSwqXarcbACwLfQMG6 PpSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id; bh=VJ4oDT5VXko7xBT6Nj5+vKj3ar5t2TsDLgn8wuHjfjU=; fh=bLwaiiBFbP0ecGL79BnmpqVmoykvBE6H1Q1q3WZlb/Q=; b=m7GI1C23OLxmJdYkXEA5Pp0vXgheG9xb5R5u6f76WX+1rlUUyaM6BlOJDH4gZer7Wo R7rGH+ybxO4rXF3IKqIeDHOHNfJtvGNK94GLZFvmwPI9r86YhZ3lXnIWZgQwQgvjYZDq CAVkFGcc0r5Y6dETTmEnqQXAR9zUZY2cgy/VyGxMgiGch1ZsPmZEpswb7WCdmSUxDQi0 v6QpYiAZpt8ZcK2M0yU0ID3jeHGm4kP/fahlvdcJMUXkx356GR4Ry5NkicYHKghW16Pe 0QZdUKqUTK0XqD77dW4BZHdQeBpHTj2mcds44NrGFrxMwRfp2840aFIpw8xx3yK6ELMx Tl3A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id mm9-20020a17090b358900b0026360db338fsi1517882pjb.107.2023.07.20.11.46.23; Thu, 20 Jul 2023 11:46:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231954AbjGTRvS convert rfc822-to-8bit (ORCPT + 99 others); Thu, 20 Jul 2023 13:51:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44806 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229580AbjGTRvQ (ORCPT ); Thu, 20 Jul 2023 13:51:16 -0400 Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6939C269D; Thu, 20 Jul 2023 10:51:15 -0700 (PDT) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.95) with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (envelope-from ) id 1qMXnc-002BO8-NB; Thu, 20 Jul 2023 19:50:48 +0200 Received: from p57bd98fd.dip0.t-ipconnect.de ([87.189.152.253] helo=suse-laptop.fritz.box) by inpost2.zedat.fu-berlin.de (Exim 4.95) with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (envelope-from ) id 1qMXnc-003YrW-FC; Thu, 20 Jul 2023 19:50:48 +0200 Message-ID: <2d0bd58fb757e7771d13f82050a546ec5f7be8de.camel@physik.fu-berlin.de> Subject: Re: [syzbot] [hfs?] WARNING in hfs_write_inode From: John Paul Adrian Glaubitz To: Matthew Wilcox , Dmitry Vyukov Cc: 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 Date: Thu, 20 Jul 2023 19:50:47 +0200 In-Reply-To: References: <000000000000dbce4e05f170f289@google.com> <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> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT User-Agent: Evolution 3.48.4 MIME-Version: 1.0 X-Original-Sender: glaubitz@physik.fu-berlin.de X-Originating-IP: 87.189.152.253 X-ZEDAT-Hint: PO X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_BLOCKED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.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 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