From: keescook@chromium.org (Kees Cook)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] seccomp: remove unnecessary unlikely()
Date: Wed, 5 Sep 2018 17:13:05 -0700 [thread overview]
Message-ID: <CAGXu5jJKovNX9SMEPrawx=BqzkPHXay-WSfidQF830hqAGZ-eg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1809061008210.23269@namei.org>
On Wed, Sep 5, 2018 at 5:08 PM, James Morris <jmorris@namei.org> wrote:
> On Wed, 5 Sep 2018, Kees Cook wrote:
>
>> On Wed, Sep 5, 2018 at 3:49 PM, Igor Stoppa <igor.stoppa@gmail.com> wrote:
>> >
>> >
>> > On 06/09/18 01:23, Kees Cook wrote:
>> >
>> >> Should I take this, or is it part of your series going somewhere else?
>> >
>> >
>> > It turned out it doesn't really work to have a generic series against 20
>> > trees :-/
>>
>> I know that pain very well!
>>
>> > I'm submitting them individually to each subsystem.
>> > So this one is just for security.
>>
>> Sounds good.
>>
>> James, can you take this directly, or would you prefer a pull request from me?
>
> I'll take it with your ack.
Already included! :) (This was a v2, split from a separate series, so
Igor already included my Ack from the other thread.)
But, for completeness:
Acked-by: Kees Cook <keescook@chromium.org>
-Kees
--
Kees Cook
Pixel Security
next prev parent reply other threads:[~2018-09-06 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 20:34 [PATCH] seccomp: remove unnecessary unlikely() Igor Stoppa
2018-09-05 22:23 ` Kees Cook
2018-09-05 22:49 ` Igor Stoppa
2018-09-05 23:31 ` Kees Cook
2018-09-06 0:08 ` James Morris
2018-09-06 0:13 ` Kees Cook [this message]
2018-09-06 20:31 ` James Morris
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='CAGXu5jJKovNX9SMEPrawx=BqzkPHXay-WSfidQF830hqAGZ-eg@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=linux-security-module@vger.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).