From: "Paul E. McKenney" <paulmck@kernel.org>
To: Marco Elver <elver@google.com>
Cc: will@kernel.org, peterz@infradead.org, tglx@linutronix.de,
mingo@kernel.org, mark.rutland@arm.com, boqun.feng@gmail.com,
dvyukov@google.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] random32: Re-enable KCSAN instrumentation
Date: Tue, 1 Dec 2020 08:58:44 -0800 [thread overview]
Message-ID: <20201201165844.GH1437@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20201124110210.495616-2-elver@google.com>
On Tue, Nov 24, 2020 at 12:02:10PM +0100, Marco Elver wrote:
> Re-enable KCSAN instrumentation, now that KCSAN no longer relies on code
> in lib/random32.c.
>
> Signed-off-by: Marco Elver <elver@google.com>
Queued and pushed both, thank you!
Thanx, Paul
> ---
> v3:
> * Add patch to series, since KCSAN no longer needs lib/random32.c.
> ---
> lib/Makefile | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/lib/Makefile b/lib/Makefile
> index ce45af50983a..301020c49533 100644
> --- a/lib/Makefile
> +++ b/lib/Makefile
> @@ -27,9 +27,6 @@ KASAN_SANITIZE_string.o := n
> CFLAGS_string.o += -fno-stack-protector
> endif
>
> -# Used by KCSAN while enabled, avoid recursion.
> -KCSAN_SANITIZE_random32.o := n
> -
> lib-y := ctype.o string.o vsprintf.o cmdline.o \
> rbtree.o radix-tree.o timerqueue.o xarray.o \
> idr.o extable.o sha1.o irq_regs.o argv_split.o \
> --
> 2.29.2.454.gaff20da3a2-goog
>
next prev parent reply other threads:[~2020-12-01 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 11:02 [PATCH v3 1/2] kcsan: Rewrite kcsan_prandom_u32_max() without prandom_u32_state() Marco Elver
2020-11-24 11:02 ` [PATCH v3 2/2] random32: Re-enable KCSAN instrumentation Marco Elver
2020-12-01 16:58 ` Paul E. McKenney [this message]
2020-12-01 8:41 ` [PATCH v3 1/2] kcsan: Rewrite kcsan_prandom_u32_max() without prandom_u32_state() Marco Elver
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=20201201165844.GH1437@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@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®