Received: by 2002:a05:6358:7058:b0:131:369:b2a3 with SMTP id 24csp10591623rwp; Fri, 21 Jul 2023 01:29:18 -0700 (PDT) X-Google-Smtp-Source: APBJJlEg+DZ/YEZGmilnExyRlVSmN6S4uDMA7KJ8hp6QcoCHS5OO1vKISlfF7aKxgg4o/7NP4vat X-Received: by 2002:a05:6a20:2453:b0:137:9622:17d1 with SMTP id t19-20020a056a20245300b00137962217d1mr1095351pzc.27.1689928157867; Fri, 21 Jul 2023 01:29:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689928157; cv=none; d=google.com; s=arc-20160816; b=iJOBL2GcPJRlsYC6MnMxGOFhMjmAGE05zpPuDCS4ur1DzegndA4oDISnsCKS4txs+X wiMGsGuwNQ8ImzoE3Wgd31jImWy65aFoQIp3NemrFdwVN5bis6xub3WFfmBWCd04A7Nk i0xGDitlU8ZQbHxoTMLPEiphz2xvXn92iHC0s9GyiHBG6UGrXOsQC3A8uO0Q1WkPaC6h GchmUx8aFdxyLFdx8I8BnkJ4qe/ze2ua5sijOOZTpIZMV+XQNjKPELzRdRmTExUzpKaE LHJWNavvX22WLf4izQ14efZdNDN0cgbCLr+JEUmHFoNJ6HuZvIbXqZjmxggMJ6ja94a6 xG4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:feedback-id:dkim-signature; bh=FUNFJj6urWuhzj/ULPd7dgB790ZiEm9pAM63aZfvl0o=; fh=lz2Fd0LyL/hyx/Ba0p+oQySW1L/7mUMKcc8fN9sbv7c=; b=sUgPgxJ3Ykqopoe21uz5Gz0OHZeji4RF77hCtMiB5tTcQWMJy67rrSzo8UKuRFynJ9 AZW3C/YOu9hEwHNdZ5JwM9kCpyekbSXBUIdXm7A9CX0dGGmwrEwQfP2xLvtV1OXeJpVn /ACr5oPYSN5nIiEB8kGopUcxlg62IH8HHHRPsUld7K1xVBFHg1eXsimf7+BjZ9xPdFY/ spEAdDGzw7H/7Xqgoc/OK802FGMccCa10Fsdmptn4iaxvTeAr/MIY913wqKPSAhzvbKO JfmjMdQxVuyowVKKKFmYoTi8SAZw2DUr669mdRLwokG66kcm5JaXKjmkdCCHSnXu/4LF fFDw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=K+rMc5OS; 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 f1-20020a637541000000b00547a1922957si1048998pgn.407.2023.07.21.01.29.05; Fri, 21 Jul 2023 01:29:17 -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; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=K+rMc5OS; 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 S231423AbjGUIOT (ORCPT + 99 others); Fri, 21 Jul 2023 04:14:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57382 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231435AbjGUIOQ (ORCPT ); Fri, 21 Jul 2023 04:14:16 -0400 Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D07D52710; Fri, 21 Jul 2023 01:14:10 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id AA0ED3200FA5; Fri, 21 Jul 2023 04:14:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 21 Jul 2023 04:14:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1689927244; x=1690013644; bh=FUNFJj6urWuhz j/ULPd7dgB790ZiEm9pAM63aZfvl0o=; b=K+rMc5OSCr1Fh3xdtUlGdyEGp1ONI 51AJM7rHQtcPDLtX+kJ6dtJJb+OZ5//ie4+jgpfhPd2tNJruDPl3+eEPHvmFD1ye 4Jb/J120LU917i5czkrEOBtvJtmoP6YWY5AggOG930AFqj2FrrXcZ/QWbx/zbGhb PZY7UmtLp9n1vsTgl/DpXwt4ICVD+veAS/haXKLYa0q5n4/a1ZfwwnxQ8xOgKm30 Z6urvnxBg9uTdpQ0kpWJHWUotlTyCmMxFR5rkEXm7b8y+XCwHVtHzIZvPHLLTYor S+KRdPKxBmDyGziWoDh0avzv1jkwzeT49W/KC6xVFmpQE7uOHeLVNM+MA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrhedugdduvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevufgjkfhfgggtsehttdertddttddvnecuhfhrohhmpefhihhnnhcu vfhhrghinhcuoehfthhhrghinheslhhinhhugidqmheikehkrdhorhhgqeenucggtffrrg htthgvrhhnpeelueehleehkefgueevtdevteejkefhffekfeffffdtgfejveekgeefvdeu heeuleenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hfthhhrghinheslhhinhhugidqmheikehkrdhorhhg X-ME-Proxy: Feedback-ID: i58a146ae:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 21 Jul 2023 04:14:01 -0400 (EDT) Date: Fri, 21 Jul 2023 18:14:04 +1000 (AEST) From: Finn Thain To: Matthew Wilcox cc: Dave Chinner , Jeff Layton , John Paul Adrian Glaubitz , Dmitry Vyukov , Viacheslav Dubeyko , Arnd Bergmann , Linus Torvalds , syzbot , Andrew Morton , christian.brauner@ubuntu.com, Damien Le Moal , 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 In-Reply-To: Message-ID: <3eca2dab-df70-9d91-52a1-af779e3c2e04@linux-m68k.org> References: <46F233BB-E587-4F2B-AA62-898EB46C9DCE@dubeyko.com> <50D6A66B-D994-48F4-9EBA-360E57A37BBE@dubeyko.com> <2d0bd58fb757e7771d13f82050a546ec5f7be8de.camel@physik.fu-berlin.de> <868611d7f222a19127783cc8d5f2af2e42ee24e4.camel@kernel.org> <60b57ae9-ff49-de1d-d40d-172c9e6d43d5@linux-m68k.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_BLOCKED,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL, SPF_HELO_PASS,SPF_NONE,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable 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 On Fri, 21 Jul 2023, Matthew Wilcox wrote: > > You've misunderstood. Google have decided to subject the entire kernel > (including obsolete unmaintained filesystems) to stress tests that it's > never had before. IOW these bugs have been there since the code was > merged. There's nothing to back out. There's no API change to blame. > It's always been buggy and it's never mattered before. > I'm not blaming the unstable API for the bugs, I'm blaming it for the workload. A stable API (like a userspace API) decreases the likelihood that overloaded maintainers have to orphan a filesystem implementation.