From: James Morris <james.l.morris@oracle.com>
To: Kees Cook <keescook@chromium.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: LKML <linux-kernel@vger.kernel.org>,
Kentaro Takeda <takedakn@nttdata.co.jp>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] TOMOYO: use designated initializers
Date: Thu, 30 Mar 2017 09:32:35 +1100 [thread overview]
Message-ID: <7b574e9d-e877-f73b-9cfc-6f6f0766a30d@oracle.com> (raw)
In-Reply-To: <CAGXu5j+kUbEcAcCKZT09pHFxWTYkiNqnxGKCyrLhuYLeiSemZw@mail.gmail.com>
On 30/03/17 07:45, Kees Cook wrote:
> On Fri, Dec 16, 2016 at 6:55 PM, Tetsuo Handa
> <penguin-kernel@i-love.sakura.ne.jp> wrote:
>> Kees Cook wrote:
>>> Prepare to mark sensitive kernel structures for randomization by making
>>> sure they're using designated initializers. These were identified during
>>> allyesconfig builds of x86, arm, and arm64, with most initializer fixes
>>> extracted from grsecurity.
>>>
>>> Signed-off-by: Kees Cook <keescook@chromium.org>
>>> ---
>>> security/tomoyo/file.c | 12 ++++++------
>>> security/tomoyo/tomoyo.c | 20 ++++++++++----------
>>> 2 files changed, 16 insertions(+), 16 deletions(-)
>>
>> Acked-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
>>
>> James, please apply to linux-security.git .
>
> Friendly ping. :) James, I don't think this ever got into -next?
Please resend it.
prev parent reply other threads:[~2017-03-29 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 1:05 Kees Cook
2016-12-17 2:55 ` Tetsuo Handa
2017-03-29 20:45 ` Kees Cook
2017-03-29 22:32 ` James Morris [this message]
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=7b574e9d-e877-f73b-9cfc-6f6f0766a30d@oracle.com \
--to=james.l.morris@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=serge@hallyn.com \
--cc=takedakn@nttdata.co.jp \
/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®