From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
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: Sat, 14 May 2022 17:28:33 +0100 [thread overview]
Message-ID: <Yn/YsTpOh898B30l@casper.infradead.org> (raw)
In-Reply-To: <202205150051.3RzuooAG-lkp@intel.com>
On Sun, May 15, 2022 at 12:23:46AM +0800, kernel test robot wrote:
> commit: 2c69e2057962b6bd76d72446453862eb59325b49 [9995/11651] fs: Convert block_read_full_page() to block_read_full_folio()
> config: hexagon-randconfig-r041-20220513 (https://download.01.org/0day-ci/archive/20220515/202205150051.3RzuooAG-lkp@intel.com/config)
> compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 38189438b69ca27b4c6ce707c52dbd217583d046)
...
> All warnings (new ones prefixed by >>):
>
> >> fs/buffer.c:2254:5: warning: stack frame size (2144) exceeds limit (1024) in 'block_read_full_folio' [-Wframe-larger-than]
> int block_read_full_folio(struct folio *folio, get_block_t *get_block)
> ^
> 1 warning generated.
Now show the warnings that were removed. This patch renames the
function, and I bet there was a similar warning before this patch.
But basically, I don't care about stack usage on hexagon with clang.
AIUI, it's a known bug.
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <willy@infradead.org>
To: kbuild-all@lists.01.org
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: Sat, 14 May 2022 17:28:33 +0100 [thread overview]
Message-ID: <Yn/YsTpOh898B30l@casper.infradead.org> (raw)
In-Reply-To: <202205150051.3RzuooAG-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Sun, May 15, 2022 at 12:23:46AM +0800, kernel test robot wrote:
> commit: 2c69e2057962b6bd76d72446453862eb59325b49 [9995/11651] fs: Convert block_read_full_page() to block_read_full_folio()
> config: hexagon-randconfig-r041-20220513 (https://download.01.org/0day-ci/archive/20220515/202205150051.3RzuooAG-lkp(a)intel.com/config)
> compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 38189438b69ca27b4c6ce707c52dbd217583d046)
...
> All warnings (new ones prefixed by >>):
>
> >> fs/buffer.c:2254:5: warning: stack frame size (2144) exceeds limit (1024) in 'block_read_full_folio' [-Wframe-larger-than]
> int block_read_full_folio(struct folio *folio, get_block_t *get_block)
> ^
> 1 warning generated.
Now show the warnings that were removed. This patch renames the
function, and I bet there was a similar warning before this patch.
But basically, I don't care about stack usage on hexagon with clang.
AIUI, it's a known bug.
next prev parent reply other threads:[~2022-05-14 16:28 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 [this message]
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
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=Yn/YsTpOh898B30l@casper.infradead.org \
--to=willy@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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.