[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YnAcLApzs6frds2n@dev-arch.thelio-3990X>
Date: Mon, 2 May 2022 11:00:12 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: kernel test robot <lkp@...el.com>, llvm@...ts.linux.dev,
kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org
Subject: Re: [willy-pagecache:for-next 60/69] fs/ntfs/aops.c:378:12: warning:
stack frame size (2216) exceeds limit (1024) in 'ntfs_read_folio'
On Sat, Apr 30, 2022 at 10:36:13PM +0100, Matthew Wilcox wrote:
> On Sat, Apr 30, 2022 at 01:11:43PM +0800, kernel test robot wrote:
> > >> fs/ntfs/aops.c:378:12: warning: stack frame size (2216) exceeds limit (1024) in 'ntfs_read_folio' [-Wframe-larger-than]
> > static int ntfs_read_folio(struct file *file, struct folio *folio)
> > ^
> > 1 warning generated.
>
> Am I getting this warning because I changed the name of the function?
> Or did I do something Bad?
I assume so. There have been other reports of high stack usage in this
function, which it seems Arnd narrowed down to 64K pages (or 256K pages
in this case):
https://lore.kernel.org/20210927141815.1711736-1-arnd@kernel.org/
https://lore.kernel.org/202103280658.kByZmw5Q-lkp@intel.com/
Cheers,
Nathan
Powered by blists - more mailing lists