[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202010051910.BC7E9F4@keescook>
Date: Mon, 5 Oct 2020 19:12:29 -0700
From: Kees Cook <keescook@...omium.org>
To: Thibaut Sautereau <thibaut.sautereau@...p-os.org>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
kernel-hardening@...ts.openwall.com, linux-kernel@...r.kernel.org,
Thibaut Sautereau <thibaut.sautereau@....gouv.fr>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Willy Tarreau <w@....eu>, Emese Revfy <re.emese@...il.com>,
Theodore Ts'o <tytso@....edu>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] random32: Restore __latent_entropy attribute on
net_rand_state
On Fri, Oct 02, 2020 at 05:16:11PM +0200, Thibaut Sautereau wrote:
> From: Thibaut Sautereau <thibaut.sautereau@....gouv.fr>
>
> Commit f227e3ec3b5c ("random32: update the net random state on interrupt
> and activity") broke compilation and was temporarily fixed by Linus in
> 83bdc7275e62 ("random32: remove net_rand_state from the latent entropy
> gcc plugin") by entirely moving net_rand_state out of the things handled
> by the latent_entropy GCC plugin.
>
> From what I understand when reading the plugin code, using the
> __latent_entropy attribute on a declaration was the wrong part and
> simply keeping the __latent_entropy attribute on the variable definition
> was the correct fix.
>
> Fixes: 83bdc7275e62 ("random32: remove net_rand_state from the latent entropy gcc plugin")
> Cc: Linus Torvalds <torvalds@...ux-foundation.org>
> Cc: Willy Tarreau <w@....eu>
> Cc: Emese Revfy <re.emese@...il.com>
> Signed-off-by: Thibaut Sautereau <thibaut.sautereau@....gouv.fr>
Yes, that looks correct. Thank you!
Acked-by: Kees Cook <keescook@...omium.org>
I'm not sure the best tree for this. Ted, Andrew, Linus? I'll take it
via my gcc plugin tree if no one else takes it. :)
--
Kees Cook
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
