All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Lutomirski <luto@kernel.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH] framewarn: expand KASAN_EXTRA exception to KASAN
Date: Fri, 21 Sep 2018 02:15:13 +0200	[thread overview]
Message-ID: <20180921001513.12504-1-Jason@zx2c4.com> (raw)

It turns out that KASAN in general will bloat stack frames in unexpected
ways, not just KASAN_EXTRA. So, this patch trivially changes that
default to be associated with KASAN instead of KASAN_EXTRA.

Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
---
 lib/Kconfig.debug | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 4966c4fbe7f7..39078a080e29 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -222,7 +222,7 @@ config ENABLE_MUST_CHECK
 config FRAME_WARN
 	int "Warn for stack frames larger than (needs gcc 4.4)"
 	range 0 8192
-	default 3072 if KASAN_EXTRA
+	default 3072 if KASAN
 	default 2048 if GCC_PLUGIN_LATENT_ENTROPY
 	default 1280 if (!64BIT && PARISC)
 	default 1024 if (!64BIT && !PARISC)
-- 
2.19.0


             reply	other threads:[~2018-09-21  0:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21  0:15 Jason A. Donenfeld [this message]
2018-09-21  1:50 ` [PATCH] framewarn: expand KASAN_EXTRA exception to KASAN Andy Lutomirski
2018-09-21  8:42   ` Dmitry Vyukov
2018-09-21 12:11     ` Andrey Konovalov
2018-09-21  9:25   ` Andrey Ryabinin
2018-09-21  9:45     ` Dmitry Vyukov
2018-09-21  9:55       ` Nathan Chancellor
2018-09-21 17:59       ` Nick Desaulniers
2018-09-21 18:17         ` Nick Desaulniers
2018-09-22 14:56       ` Arnd Bergmann
2018-09-24  8:04         ` Dmitry Vyukov

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=20180921001513.12504-1-Jason@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.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 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.