[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e76d1c3239bf2d33889c4874bc9919fee6b6ebe.camel@perches.com>
Date: Sun, 25 Oct 2020 12:23:21 -0700
From: Joe Perches <joe@...ches.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
kernel test robot <lkp@...el.com>
Cc: Andrey Konovalov <andreyknvl@...gle.com>, kbuild-all@...ts.01.org,
clang-built-linux@...glegroups.com, linux-kernel@...r.kernel.org,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: drivers/video/backlight/ltv350qv.c:192:12: warning: stack frame
size of 13472 bytes in function 'ltv350qv_power'
On Sun, 2020-10-25 at 12:17 -0700, Andrew Morton wrote:
> On Mon, 26 Oct 2020 02:15:37 +0800 kernel test robot <lkp@...el.com> wrote:
> > vim +/ltv350qv_power +192 drivers/video/backlight/ltv350qv.c
>
> Odd - the code looks pretty normal. It is possible that your compiler
> is (crazily) inlining ltv350qv_write_reg()?
There's a lot of stack used when gcc's compiler options include
-fsanitize=object-size
This option enables instrumentation of memory references using
the "__builtin_object_size" function. Various out of bounds
pointer accesses are detected.
Perhaps this config enables it?
Powered by blists - more mailing lists