[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jKg6zCd4wwmx974+m2fW3biMoD1He52C0b9UmwsSUfnCQ@mail.gmail.com>
Date: Mon, 3 Oct 2016 14:13:10 -0700
From: Kees Cook <keescook@...omium.org>
To: Elena Reshetova <elena.reshetova@...el.com>
Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, David Windsor <dwindsor@...il.com>,
Hans Liljestrand <ishkamiel@...il.com>
Subject: Re: [RFC PATCH 03/13] kernel: identify wrapping atomic usage
On Sun, Oct 2, 2016 at 11:41 PM, Elena Reshetova
<elena.reshetova@...el.com> wrote:
> From: David Windsor <dwindsor@...il.com>
>
> Signed-off-by: Hans Liljestrand <ishkamiel@...il.com>
> Signed-off-by: Elena Reshetova <elena.reshetova@...el.com>
> Signed-off-by: David Windsor <dwindsor@...il.com>
While these patches are all doing the same mechanic changes, I think
they should still have a commit message body. Maybe something simple
like:
Switch wrapping atomic_t uses in $subsystem to atomic_t_wrap in
support of CONFIG_HARDENED_ATOMIC.
-Kees
--
Kees Cook
Nexus Security
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.
