From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: shuah@kernel.org
Cc: keescook@chromium.org, kernel@collabora.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] selftests/lkdtm: Disable CONFIG_UBSAN_TRAP in test config
Date: Mon, 25 Sep 2023 07:22:35 +0200 [thread overview]
Message-ID: <875y3yesis.fsf@collabora.com> (raw)
In-Reply-To: <20230802063252.1917997-1-ricardo.canuelo@collabora.com>
Hi Shuah,
Gentle ping for this, what's the merge status?
On mié, ago 02 2023 at 08:32:52, Ricardo Cañuelo <ricardo.canuelo@collabora.com> wrote:
> The lkdtm selftest config fragment enables CONFIG_UBSAN_TRAP to make the
> ARRAY_BOUNDS test kill the calling process when an out-of-bound access
> is detected by UBSAN. However, after this [1] commit, UBSAN is triggered
> under many new scenarios that weren't detected before, such as in struct
> definitions with fixed-size trailing arrays used as flexible arrays. As
> a result, CONFIG_UBSAN_TRAP=y has become a very aggressive option to
> enable except for specific situations.
>
> `make kselftest-merge` applies CONFIG_UBSAN_TRAP=y to the kernel config
> for all selftests, which makes many of them fail because of system hangs
> during boot.
>
> This change removes the config option from the lkdtm kselftest and
> configures the ARRAY_BOUNDS test to look for UBSAN reports rather than
> relying on the calling process being killed.
>
> [1] commit 2d47c6956ab3 ("ubsan: Tighten UBSAN_BOUNDS on GCC")'
>
> Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
> Reviewed-by: Kees Cook <keescook@chromium.org>
> ---
>
> Changelog:
>
> v2:
> - Configure the ARRAY_BOUNDS lkdtm test to match UBSAN reports instead
> of disabling the test
>
> tools/testing/selftests/lkdtm/config | 1 -
> tools/testing/selftests/lkdtm/tests.txt | 2 +-
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/lkdtm/config b/tools/testing/selftests/lkdtm/config
> index 5d52f64dfb43..7afe05e8c4d7 100644
> --- a/tools/testing/selftests/lkdtm/config
> +++ b/tools/testing/selftests/lkdtm/config
> @@ -9,7 +9,6 @@ CONFIG_INIT_ON_FREE_DEFAULT_ON=y
> CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y
> CONFIG_UBSAN=y
> CONFIG_UBSAN_BOUNDS=y
> -CONFIG_UBSAN_TRAP=y
> CONFIG_STACKPROTECTOR_STRONG=y
> CONFIG_SLUB_DEBUG=y
> CONFIG_SLUB_DEBUG_ON=y
> diff --git a/tools/testing/selftests/lkdtm/tests.txt b/tools/testing/selftests/lkdtm/tests.txt
> index 607b8d7e3ea3..2f3a1b96da6e 100644
> --- a/tools/testing/selftests/lkdtm/tests.txt
> +++ b/tools/testing/selftests/lkdtm/tests.txt
> @@ -7,7 +7,7 @@ EXCEPTION
> #EXHAUST_STACK Corrupts memory on failure
> #CORRUPT_STACK Crashes entire system on success
> #CORRUPT_STACK_STRONG Crashes entire system on success
> -ARRAY_BOUNDS
> +ARRAY_BOUNDS call trace:|UBSAN: array-index-out-of-bounds
> CORRUPT_LIST_ADD list_add corruption
> CORRUPT_LIST_DEL list_del corruption
> STACK_GUARD_PAGE_LEADING
> --
> 2.25.1
Thanks,
Ricardo
next prev parent reply other threads:[~2023-09-25 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 6:32 [PATCH v2] selftests/lkdtm: Disable CONFIG_UBSAN_TRAP in test config Ricardo Cañuelo
2023-09-25 5:22 ` Ricardo Cañuelo [this message]
2023-09-25 17:14 ` Kees Cook
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=875y3yesis.fsf@collabora.com \
--to=ricardo.canuelo@collabora.com \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).