From: Andrey Konovalov <andreyknvl@gmail.com>
To: Peter Collingbourne <pcc@google.com>
Cc: Alexander Potapenko <glider@google.com>,
George Popescu <georgepope@android.com>,
Elena Petrova <lenaptr@google.com>,
Evgenii Stepanov <eugenis@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] kasan: fix unit tests with CONFIG_UBSAN_LOCAL_BOUNDS enabled
Date: Fri, 7 May 2021 00:12:41 +0200 [thread overview]
Message-ID: <CA+fCnZfTvOsFfwLfpHZKsDJSMDa6NpJu6NVfq4LREjPWg6Yw2w@mail.gmail.com> (raw)
In-Reply-To: <20210506212025.815380-1-pcc@google.com>
On Thu, May 6, 2021 at 11:20 PM Peter Collingbourne <pcc@google.com> wrote:
>
> These tests deliberately access these arrays out of bounds,
> which will cause the dynamic local bounds checks inserted by
> CONFIG_UBSAN_LOCAL_BOUNDS to fail and panic the kernel. To avoid this
> problem, access the arrays via volatile pointers, which will prevent
> the compiler from being able to determine the array bounds.
>
> Signed-off-by: Peter Collingbourne <pcc@google.com>
> Cc: stable@vger.kernel.org
> Link: https://linux-review.googlesource.com/id/I90b1713fbfa1bf68ff895aef099ea77b98a7c3b9
> ---
> lib/test_kasan.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/lib/test_kasan.c b/lib/test_kasan.c
> index dc05cfc2d12f..2a078e8e7b8e 100644
> --- a/lib/test_kasan.c
> +++ b/lib/test_kasan.c
> @@ -654,8 +654,8 @@ static char global_array[10];
>
> static void kasan_global_oob(struct kunit *test)
> {
> - volatile int i = 3;
> - char *p = &global_array[ARRAY_SIZE(global_array) + i];
> + char *volatile array = global_array;
> + char *p = &array[ARRAY_SIZE(global_array) + 3];
Nit: in the kernel, "volatile" usually comes before the pointer type.
>
> /* Only generic mode instruments globals. */
> KASAN_TEST_NEEDS_CONFIG_ON(test, CONFIG_KASAN_GENERIC);
> @@ -703,8 +703,8 @@ static void ksize_uaf(struct kunit *test)
> static void kasan_stack_oob(struct kunit *test)
> {
> char stack_array[10];
> - volatile int i = OOB_TAG_OFF;
> - char *p = &stack_array[ARRAY_SIZE(stack_array) + i];
> + char *volatile array = stack_array;
> + char *p = &array[ARRAY_SIZE(stack_array) + OOB_TAG_OFF];
>
> KASAN_TEST_NEEDS_CONFIG_ON(test, CONFIG_KASAN_STACK);
>
> @@ -715,7 +715,8 @@ static void kasan_alloca_oob_left(struct kunit *test)
> {
> volatile int i = 10;
> char alloca_array[i];
> - char *p = alloca_array - 1;
> + char *volatile array = alloca_array;
> + char *p = array - 1;
>
> /* Only generic mode instruments dynamic allocas. */
> KASAN_TEST_NEEDS_CONFIG_ON(test, CONFIG_KASAN_GENERIC);
> @@ -728,7 +729,8 @@ static void kasan_alloca_oob_right(struct kunit *test)
> {
> volatile int i = 10;
> char alloca_array[i];
> - char *p = alloca_array + i;
> + char *volatile array = alloca_array;
> + char *p = array + i;
>
> /* Only generic mode instruments dynamic allocas. */
> KASAN_TEST_NEEDS_CONFIG_ON(test, CONFIG_KASAN_GENERIC);
> --
> 2.31.1.607.g51e8a6a459-goog
>
Acked-by: Andrey Konovalov <andreyknvl@gmail.com>
Thanks, Peter!
next prev parent reply other threads:[~2021-05-06 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 21:20 Peter Collingbourne
2021-05-06 22:12 ` Andrey Konovalov [this message]
2021-05-06 23:47 ` Peter Collingbourne
2021-05-06 23:57 ` Andrey Konovalov
2021-05-07 2:59 ` Peter Collingbourne
2021-05-09 0:30 ` Andrew Morton
2021-05-10 17:16 ` Peter Collingbourne
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=CA+fCnZfTvOsFfwLfpHZKsDJSMDa6NpJu6NVfq4LREjPWg6Yw2w@mail.gmail.com \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eugenis@google.com \
--cc=georgepope@android.com \
--cc=glider@google.com \
--cc=lenaptr@google.com \
--cc=linux-mm@kvack.org \
--cc=pcc@google.com \
--cc=stable@vger.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