linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Kees Cook <keescook@chromium.org>
Cc: usama.anjum@collabora.com, Shuah Khan <shuah@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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: Thu, 10 Mar 2022 22:22:51 +0500	[thread overview]
Message-ID: <76529762-1a36-142d-0aa9-beb5fa2bb27b@collabora.com> (raw)
In-Reply-To: <202203091123.33E89F5@keescook>

On 3/10/22 12:23 AM, Kees Cook wrote:
> On Fri, Feb 18, 2022 at 01:56:20AM +0500, Muhammad Usama Anjum wrote:
>> Add config option which is needed for SLAB_LINEAR_OVERFLOW test. It
>> needs KASAN enabled.
> 
> I'd prefer this use the SLAB_DEBUG options -- KASAN is very heavy.
I'll test it out and update in the next patch version.

-- 
Muhammad Usama Anjum

  reply	other threads:[~2022-03-10 17:24 UTC|newest]

Thread overview: 15+ 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 ` [PATCH 2/2] selftests/lkdtm: add config Muhammad Usama Anjum
2022-02-18 15:32   ` Muhammad Usama Anjum
2022-03-09 19:23   ` Kees Cook
2022-03-10 17:22     ` Muhammad Usama Anjum [this message]
2022-03-15 11:55       ` Muhammad Usama Anjum
2022-04-04  7:50         ` Muhammad Usama Anjum
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-28  7:06 ` Muhammad Usama Anjum
2022-03-08 11:17   ` Muhammad Usama Anjum
2022-03-09 19:22 ` Kees Cook
2022-03-10 17:21   ` Muhammad Usama Anjum
2022-04-14 11:31     ` Muhammad Usama Anjum
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=76529762-1a36-142d-0aa9-beb5fa2bb27b@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 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).