Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <7e76d1c3239bf2d33889c4874bc9919fee6b6ebe.camel@perches.com>
Subject: Re: drivers/video/backlight/ltv350qv.c:192:12: warning: stack frame
 size of 13472 bytes in function 'ltv350qv_power'
From:   Joe Perches <joe@perches.com>
To:     Andrew Morton <akpm@linux-foundation.org>,
        kernel test robot <lkp@intel.com>
Cc:     Andrey Konovalov <andreyknvl@google.com>, kbuild-all@lists.01.org,
        clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org,
        Linux Memory Management List <linux-mm@kvack.org>
Date:   Sun, 25 Oct 2020 12:23:21 -0700
In-Reply-To: <20201025121708.04d4070a44e28146baf9a6a7@linux-foundation.org>
References: <202010260230.VivTG0Gb-lkp@intel.com>
         <20201025121708.04d4070a44e28146baf9a6a7@linux-foundation.org>
Content-Type: text/plain; charset="ISO-8859-1"
User-Agent: Evolution 3.38.1-1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

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@intel.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?