From: Brian Cain <bcain@quicinc.com>
To: Nathan Chancellor <nathan@kernel.org>,
Matthew Wilcox <willy@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>,
Sid Manning <sidneym@quicinc.com>
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'
Date: Tue, 17 May 2022 04:16:45 +0000 [thread overview]
Message-ID: <SN6PR02MB4205A0695B4B2543A9B981FCB8CE9@SN6PR02MB4205.namprd02.prod.outlook.com> (raw)
In-Reply-To: <YoAlvnyjEbYV4T1L@dev-arch.thelio-3990X>
> -----Original Message-----
> From: Nathan Chancellor <nathan@kernel.org>
...
> 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.
-Brian
next prev parent reply other threads:[~2022-05-17 4:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 16:23 [linux-next:master 9995/11651] fs/buffer.c:2254:5: warning: stack frame size (2144) exceeds limit (1024) in 'block_read_full_folio' kernel test robot
2022-05-14 16:28 ` Matthew Wilcox
2022-05-14 16:28 ` Matthew Wilcox
2022-05-14 21:57 ` Nathan Chancellor
2022-05-14 21:57 ` Nathan Chancellor
2022-05-15 0:30 ` Matthew Wilcox
2022-05-15 0:30 ` Matthew Wilcox
2022-05-15 0:30 ` Matthew Wilcox
2022-05-16 10:09 ` [kbuild-all] " Chen, Rong A
2022-05-17 4:16 ` Brian Cain
2022-05-17 4:16 ` Brian Cain [this message]
2022-05-17 4:48 ` Matthew Wilcox
2022-05-17 4:48 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SN6PR02MB4205A0695B4B2543A9B981FCB8CE9@SN6PR02MB4205.namprd02.prod.outlook.com \
--to=bcain@quicinc.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=sidneym@quicinc.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.