linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: "Shi, Yang" <yang.shi@linaro.org>
Cc: "linux-kernel@vger.kernel.org >> LKML" <linux-kernel@vger.kernel.org>
Subject: Re: KASAN can't change FRAME_WARN
Date: Wed, 20 Apr 2016 19:03:04 +0300	[thread overview]
Message-ID: <5717A838.3050601@virtuozzo.com> (raw)
In-Reply-To: <57166F56.8010401@linaro.org>



On 04/19/2016 08:48 PM, Shi, Yang wrote:
> Hi Andrey,
> 
> When I enable KASAN for 4.5 and 4.6 (I didn't try with older versions), I got FRAME_WARN warning for frame size exceeds 2048 bytes.
> 
> Then I found the kconfig looks like:
> 
> range 0 8192
> default 0 if KASAN
> default 1024 if !64BIT
> default 2048 if 64BIT
> 
> In my understanding, FRAME_WARN should be 0 once KASAN is enabled, but it is still 2048. I tried a couple of fixes, i.e.
> 
> default 0 if KASAN
> default 1024 if (!KASAN && !64BIT)
> default 2048 if (!KASAN && 64BIT)
> 
> But, nothing works, so I have to add "depends on !KASAN" to disable FRAME_WARN completely, but it causes the kernel image size increased.
> 
> Any hint is appreciated.

make menuconfig/nconfig/whatever ?
And set FRAME_WARN to zero.

In kconfig we define only default FRAME_WARN value, but allow to change it.
Note that the default value is only assigned to the config symbol if no other
value was set by the user.

The main point of default here is to silence warning in build testing.
E.g. when 'make randconfig' enables KASAN, FRAME_WARN becomes 0 and silences warnings.



> Thanks,
> Yang

      reply	other threads:[~2016-04-20 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 17:48 KASAN can't change FRAME_WARN Shi, Yang
2016-04-20 16:03 ` Andrey Ryabinin [this message]

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=5717A838.3050601@virtuozzo.com \
    --to=aryabinin@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yang.shi@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).