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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 123C3C001DB for ; Fri, 4 Aug 2023 10:22:28 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 102782802E6; Fri, 4 Aug 2023 06:22:28 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 0B1E02802E1; Fri, 4 Aug 2023 06:22:28 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id EE2892802E6; Fri, 4 Aug 2023 06:22:27 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id DF1CE2802E1 for ; Fri, 4 Aug 2023 06:22:27 -0400 (EDT) Received: from smtpin29.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 84083A1377 for ; Fri, 4 Aug 2023 10:22:27 +0000 (UTC) X-FDA: 81086032734.29.FD79389 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf21.hostedemail.com (Postfix) with ESMTP id AA2CD1C0009 for ; Fri, 4 Aug 2023 10:22:23 +0000 (UTC) Authentication-Results: imf21.hostedemail.com; dkim=none; spf=none (imf21.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1691144544; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Y5QjF/0ZBXzNRvGUWOhPxQNXXyPn9HXP7dOaQKxSjNM=; b=2miquMbRho5/wfQCFdTKFbn46lRMRadfp6TEODeKScpr8pN4c9MWcuY74ZzQIjDU2i8//c YZCB5Go+FPDpviX/naPnUBQf4amVylJgDZQNzYMrFDn+6XbU8EUfDc3m8kvrvRT67y6+7q QnQ8kfWTJD4pDdu6ODMoxNG4+nw9dcM= ARC-Authentication-Results: i=1; imf21.hostedemail.com; dkim=none; spf=none (imf21.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1691144544; a=rsa-sha256; cv=none; b=rOmserbJRmCP+Pmwvpsc2zts268vuOgm1IkzDYkjFku6vJAaR2D4R1x2m/RmN9mZKMyqkr Y9gAMa+22t7M7orF7/cNY1NJ9pNZZnBatmNmrpUlo+SPR+Sq7wZHbc9Max1y3JE1u/wI5d xcQmMRcZuQ0C3/vOlrQ8UH1PSLwn7w0= Received: by verein.lst.de (Postfix, from userid 2407) id A1F7D68AA6; Fri, 4 Aug 2023 12:22:18 +0200 (CEST) Date: Fri, 4 Aug 2023 12:22:18 +0200 From: Christoph Hellwig To: Matthew Wilcox Cc: kernel test robot , Andrew Morton , Linux Memory Management List , linux-arm-msm@vger.kernel.org, linux-doc@vger.kernel.org, linux-rtc@vger.kernel.org, linux-serial@vger.kernel.org, Christoph Hellwig , Jens Axboe Subject: Re: [linux-next:master] BUILD REGRESSION fb4327106e5250ee360d0d8b056c1eef7eeb9a98 Message-ID: <20230804102218.GD23274@lst.de> References: <202308040141.gUjtZ32J-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Rspamd-Queue-Id: AA2CD1C0009 X-Rspam-User: X-Stat-Signature: ami3foq45nrcswcig13zkns4jwuurg8a X-Rspamd-Server: rspam01 X-HE-Tag: 1691144543-714274 X-HE-Meta: U2FsdGVkX1/MrYBiZWFW+mOFis410/T3mxl9XqxHxp9tPORokXSV32iY/gq2PmS/QwzONbvc78QhN0C7qYLzJWRc4u0QWJJAwcQjMj91wHuPVe+OUl2zeLBaSOQYpfww+W/JpCxsrOkuL6a6FNkJ0U7p3E76DA4eY5Ft6l3M2exrGmaOmZDxxvJHHtdLVyGEJ9KbrYEpSDZyyXezDdC7dFuaNrJDBQV1kNncl+IfZgUEkhB/+HaX+fOPlZGciFwd6rKcPPCRvfpxOn6uhL+zQxOu3SVtVHsR/IY8Ds61mi3nkSMmr4oojpNCyrr/YFCG0TLcchgPj1M3lRg1G9AVYe2EfXLUocvd/0e8mLoxZY7dK3K832HH03CLyDvwa2X6uZOxCa223ktU4YH6z5sIRWnRrCJvkGA5ekWwYJ57dR4WaRCL0baqXOzMC1Ja9xlRLwA9XrHtMT0gfzzTicCWgdfUUfDCD7te2WNioR9rzXQrJqJdXzPjAHwGyazo4KIyDlfVygBxKZAPCHARUxj0QPRr775YRdfPnJcmPB6yPFCwIm1ZuCLdm+HNU9hx1f/TF8Uy4zhPXH8C3/S2e/VXNyj19anmmhtIqJmXIVqZZU2k7pq+GYiizaQDWKboDuSSoPS75gcnO4XyzfRrycqaBm+T+KQhyZfhbKYwiuOdBFNUj+9dIO1qVdJbD6ZX7cdZIm1pSpebqmgdxLrfQofTtMTuhWSnAev6FJOERe3q7ZWibfnciEatEb4XQPrnK4WSAELuzg/iuaXSTDy+yyy232EVLNoEauQG6ASAxBAhFp3EquS7SsFFpVnam9/lRSNSZPLINHs4tnJq024s2Ak5dusWLid2fkmRdMHDpcMF9NL8G3T5vj0LlbaI76ZBJgj8kSR82fj80Kr8Ik59N5Rdbx6swE1ujhzSi/29EXYw0DcrNd79jVkdx+xPJ/1adQCEZeW4Po7ZQTUPFE3rwQW Ly2O9Q+X 8A7scYkEoHjvdoB30uXT11fHVNp5gsQBR7jb6GeDKAiOiKzuXzLYccf1RhQ== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Aug 03, 2023 at 09:02:29PM +0100, Matthew Wilcox wrote: > I think something like this would fix it. Jens? Christoph? > > +++ b/fs/romfs/Kconfig > @@ -2,6 +2,7 @@ > config ROMFS_FS > tristate "ROM file system support" > depends on BLOCK || MTD > + select BUFFER_HEAD > help > This is a very small read-only file system mainly intended for > initial ram disks of installation disks, but it could be used for > > romfs has a few options and I spent no time looking at this closely; > maybe not every version of romfs needs buffer heads. It only needs buffer_heads for the block based path. I'll send a patch for it.