From: Mark Rutland <mark.rutland@arm.com>
To: Marco Elver <elver@google.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, kasan-dev@googlegroups.com
Subject: Re: [PATCH 2/2] lib/test_kasan: Add stack overflow test
Date: Tue, 23 Jul 2019 17:24:03 +0100 [thread overview]
Message-ID: <20190723162403.GA56959@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20190719132818.40258-2-elver@google.com>
On Fri, Jul 19, 2019 at 03:28:18PM +0200, Marco Elver wrote:
> Adds a simple stack overflow test, to check the error being reported on
> an overflow. Without CONFIG_STACK_GUARD_PAGE, the result is typically
> some seemingly unrelated KASAN error message due to accessing random
> other memory.
Can't we use the LKDTM_EXHAUST_STACK case to check this?
I was also under the impression that the other KASAN self-tests weren't
fatal, and IIUC this will kill the kernel.
Given that, and given this is testing non-KASAN functionality, I'm not
sure it makes sense to bundle this with the KASAN tests.
Thanks,
Mark.
>
> Signed-off-by: Marco Elver <elver@google.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
> Cc: Alexander Potapenko <glider@google.com>
> Cc: Dmitry Vyukov <dvyukov@google.com>
> Cc: Andrey Konovalov <andreyknvl@google.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: x86@kernel.org
> Cc: linux-kernel@vger.kernel.org
> Cc: kasan-dev@googlegroups.com
> ---
> lib/test_kasan.c | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/lib/test_kasan.c b/lib/test_kasan.c
> index b63b367a94e8..3092ec01189d 100644
> --- a/lib/test_kasan.c
> +++ b/lib/test_kasan.c
> @@ -15,6 +15,7 @@
> #include <linux/mman.h>
> #include <linux/module.h>
> #include <linux/printk.h>
> +#include <linux/sched/task_stack.h>
> #include <linux/slab.h>
> #include <linux/string.h>
> #include <linux/uaccess.h>
> @@ -709,6 +710,32 @@ static noinline void __init kmalloc_double_kzfree(void)
> kzfree(ptr);
> }
>
> +#ifdef CONFIG_STACK_GUARD_PAGE
> +static noinline void __init stack_overflow_via_recursion(void)
> +{
> + volatile int n = 512;
> +
> + BUILD_BUG_ON(IS_ENABLED(CONFIG_STACK_GROWSUP));
> +
> + /* About to overflow: overflow via alloca'd array and try to write. */
> + if (!object_is_on_stack((void *)&n - n)) {
> + volatile char overflow[n];
> +
> + overflow[0] = overflow[0];
> + return;
> + }
> +
> + stack_overflow_via_recursion();
> +}
> +
> +static noinline void __init kasan_stack_overflow(void)
> +{
> + pr_info("stack overflow begin\n");
> + stack_overflow_via_recursion();
> + pr_info("stack overflow end\n");
> +}
> +#endif
> +
> static int __init kmalloc_tests_init(void)
> {
> /*
> @@ -753,6 +780,15 @@ static int __init kmalloc_tests_init(void)
> kasan_bitops();
> kmalloc_double_kzfree();
>
> +#ifdef CONFIG_STACK_GUARD_PAGE
> + /*
> + * Only test with CONFIG_STACK_GUARD_PAGE, as without we get other
> + * random KASAN violations, due to accessing other random memory (we
> + * want to avoid actually corrupting memory in these tests).
> + */
> + kasan_stack_overflow();
> +#endif
> +
> kasan_restore_multi_shot(multishot);
>
> return -EAGAIN;
> --
> 2.22.0.657.g960e92d24f-goog
>
next prev parent reply other threads:[~2019-07-23 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 13:28 [PATCH 1/2] kernel/fork: Add support for stack-end guard page Marco Elver
2019-07-19 13:28 ` [PATCH 2/2] lib/test_kasan: Add stack overflow test Marco Elver
2019-07-23 16:24 ` Mark Rutland [this message]
2019-07-23 16:49 ` Marco Elver
2019-07-24 11:23 ` Mark Rutland
2019-07-23 16:41 ` [PATCH 1/2] kernel/fork: Add support for stack-end guard page Mark Rutland
2019-07-24 9:11 ` Dmitry Vyukov
2019-07-24 11:21 ` Mark Rutland
2019-07-25 7:53 ` Dmitry Vyukov
2019-07-25 10:14 ` Mark Rutland
2019-07-25 15:14 ` Daniel Axtens
2019-07-25 16:08 ` Mark Rutland
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=20190723162403.GA56959@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=bp@alien8.de \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®