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 13238C433EF for ; Tue, 17 May 2022 04:48:54 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 57D278D0010; Tue, 17 May 2022 00:48:54 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 52CCA8D0003; Tue, 17 May 2022 00:48:54 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 41B358D0010; Tue, 17 May 2022 00:48:54 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 320A38D0003 for ; Tue, 17 May 2022 00:48:54 -0400 (EDT) Received: from smtpin09.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay13.hostedemail.com (Postfix) with ESMTP id E0ACB61285 for ; Tue, 17 May 2022 04:48:53 +0000 (UTC) X-FDA: 79474004946.09.F8A3E2D Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf11.hostedemail.com (Postfix) with ESMTP id 21FB04009C for ; Tue, 17 May 2022 04:48:47 +0000 (UTC) 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=6VdXU36plQ8uaQ+VdzI8WaT/aCW7YyIgVyie8C4UwZQ=; b=Lwo8VzstY2I33pwrgT6Oe7JrVv 2Smz0NCanGwQH4Q0AquxBcma1Btb2dQHOmtEcj4lEmlS1TYhiX5jknBJYPp2IA3KwdwEI3mzIphe1 Rr6AgqpIRbou8hwB1Bq+4WuzkEVDjBgucpYEpR8zjDEY9ufmSukNYu2j/I/Q2p6o1gnmcV0zE4aun bwDdQUqGlMyOqTAifEyM/qSSHAvojyIfsmHP3Of3pM9SoNl0YFia6z01a2TIYiOrHqmg3TK7LMa6D 8/F+jpzMCaAl2WY4sLnjY4rgeJF59syaLqIdlJMyQlASBjlj0l5y2/uVbUbrJJL8M5wKxWFK1ZMoU tvDoXa6w==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1nqp8I-00AX5V-QY; Tue, 17 May 2022 04:48:30 +0000 Date: Tue, 17 May 2022 05:48:30 +0100 From: Matthew Wilcox To: Brian Cain Cc: Nathan Chancellor , kernel test robot , "llvm@lists.linux.dev" , "kbuild-all@lists.01.org" , Linux Memory Management List , "linux-hexagon@vger.kernel.org" , Sid Manning Subject: Re: [linux-next:master 9995/11651] fs/buffer.c:2254:5: warning: stack frame size (2144) exceeds limit (1024) in 'block_read_full_folio' Message-ID: References: <202205150051.3RzuooAG-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspam-User: X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: 21FB04009C X-Stat-Signature: ax74557nxc6wsi7zq5ffy4fsw6zhm9dz Authentication-Results: imf11.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=Lwo8Vzst; spf=none (imf11.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none X-HE-Tag: 1652762927-733514 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 Tue, May 17, 2022 at 04:16:45AM +0000, Brian Cain wrote: > > -----Original Message----- > > From: Nathan Chancellor > ... > > As a side note... Brian, is there any reason for 256K pages to exist for > > Hexagon? This has been an option since Hexagon's introduction but is it > > actually used? 4K pages is the default and the help text says "use with > > caution". Perhaps the choice should be turned off altogether for > > CONFIG_COMPILE_TEST so that we cannot select this configuration and > > bother developers with these reports. > > It's not the most commonly used page size, yeah. Ok, we will disable it for CONFIG_COMPILE_TEST. Maybe the stack size limit could be raised for 256KB page size? Presumably the minimum stack size is 256KB, so it's not a problem for an individual function to consume 16KB of stack space?