From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: usama.anjum@collabora.com, kernel@collabora.com,
kernelci@groups.io, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] selftests/lkdtm: add config
Date: Fri, 18 Feb 2022 20:32:01 +0500 [thread overview]
Message-ID: <03ac8b04-15bb-d4a9-d09b-e5711bed1811@collabora.com> (raw)
In-Reply-To: <20220217205620.2512094-2-usama.anjum@collabora.com>
On 2/18/22 1:56 AM, Muhammad Usama Anjum wrote:
> Add config option which is needed for SLAB_LINEAR_OVERFLOW test. It
> needs KASAN enabled.
>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Fixes: 9c4f6ebc3665 ("lkdtm/heap: Add vmalloc linear overflow test")
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
Reported-by: "kernelci.org bot" <bot@kernelci.org>
WARNING: multiple messages have this Message-ID (diff)
From: "Usama" <usama.anjum@collabora.com>
To: Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: usama.anjum@collabora.com, kernel@collabora.com,
kernelci@groups.io, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] selftests/lkdtm: add config
Date: Fri, 18 Feb 2022 20:32:01 +0500 [thread overview]
Message-ID: <03ac8b04-15bb-d4a9-d09b-e5711bed1811@collabora.com> (raw)
In-Reply-To: <20220217205620.2512094-2-usama.anjum@collabora.com>
On 2/18/22 1:56 AM, Muhammad Usama Anjum wrote:
> Add config option which is needed for SLAB_LINEAR_OVERFLOW test. It
> needs KASAN enabled.
>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Fixes: 9c4f6ebc3665 ("lkdtm/heap: Add vmalloc linear overflow test")
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
Reported-by: "kernelci.org bot" <bot@kernelci.org>
next prev parent reply other threads:[~2022-02-18 15:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 20:56 [PATCH 1/2] selftests/lkdtm: add config and turn off CFI_FORWARD_PROTO Muhammad Usama Anjum
2022-02-17 20:56 ` Usama
2022-02-17 20:56 ` [PATCH 2/2] selftests/lkdtm: add config Muhammad Usama Anjum
2022-02-17 20:56 ` Usama
2022-02-18 15:32 ` Muhammad Usama Anjum [this message]
2022-02-18 15:32 ` Usama
2022-03-09 19:23 ` Kees Cook
2022-03-10 17:22 ` Muhammad Usama Anjum
2022-03-10 17:22 ` Usama
2022-03-15 11:55 ` Muhammad Usama Anjum
2022-03-15 11:55 ` Usama
2022-04-04 7:50 ` Muhammad Usama Anjum
2022-04-04 7:50 ` Usama
2022-04-16 21:13 ` Kees Cook
2022-02-18 15:31 ` [PATCH 1/2] selftests/lkdtm: add config and turn off CFI_FORWARD_PROTO Muhammad Usama Anjum
2022-02-18 15:31 ` Usama
2022-02-28 7:06 ` Muhammad Usama Anjum
2022-02-28 7:06 ` Usama
2022-03-08 11:17 ` Muhammad Usama Anjum
2022-03-08 11:17 ` Usama
2022-03-09 19:22 ` Kees Cook
2022-03-10 17:21 ` Muhammad Usama Anjum
2022-03-10 17:21 ` Usama
2022-04-14 11:31 ` Muhammad Usama Anjum
2022-04-14 11:31 ` Usama
2022-04-16 21:06 ` 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=03ac8b04-15bb-d4a9-d09b-e5711bed1811@collabora.com \
--to=usama.anjum@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=kernelci@groups.io \
--cc=linux-kernel@vger.kernel.org \
--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 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.