From: Greg KH <gregkh@linuxfoundation.org>
To: linux-security-module@vger.kernel.org
Subject: Re: [PATCH 1/2] Replace magic for trusting the secondary keyring with #define
Date: Thu, 16 Aug 2018 15:12:52 +0000 [thread overview]
Message-ID: <20180816151252.GD10648@kroah.com> (raw)
In-Reply-To: <07e17009-18bb-df72-3408-7e8c0c11e16f@sembritzki.me>
On Thu, Aug 16, 2018 at 03:17:47PM +0200, Yannik Sembritzki wrote:
> On 16.08.2018 15:15, David Howells wrote:
> > I would suggest something like that. I've switched the patches over as has
> > been suggested. I think it makes more sense to create the constant first and
> > then use that.
> >
> > I've also fleshed out the patch description a bit and added cc and Fixes
> > fields as appropriate.
>
> Thanks, that looks good to me.
> I see that you only cc'd stable@ in the (now) second patch. I'm curious,
> will this automatically apply the first patch to stable?
No, but I'll try to remember to do it in order to get it right :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 1/2] Replace magic for trusting the secondary keyring with #define
Date: Thu, 16 Aug 2018 17:12:52 +0200 [thread overview]
Message-ID: <20180816151252.GD10648@kroah.com> (raw)
In-Reply-To: <07e17009-18bb-df72-3408-7e8c0c11e16f@sembritzki.me>
On Thu, Aug 16, 2018 at 03:17:47PM +0200, Yannik Sembritzki wrote:
> On 16.08.2018 15:15, David Howells wrote:
> > I would suggest something like that. I've switched the patches over as has
> > been suggested. I think it makes more sense to create the constant first and
> > then use that.
> >
> > I've also fleshed out the patch description a bit and added cc and Fixes
> > fields as appropriate.
>
> Thanks, that looks good to me.
> I see that you only cc'd stable@ in the (now) second patch. I'm curious,
> will this automatically apply the first patch to stable?
No, but I'll try to remember to do it in order to get it right :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Yannik Sembritzki <yannik@sembritzki.me>
Cc: David Howells <dhowells@redhat.com>,
torvalds@linux-foundation.org, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, dyoung@redhat.com,
James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH 1/2] Replace magic for trusting the secondary keyring with #define
Date: Thu, 16 Aug 2018 17:12:52 +0200 [thread overview]
Message-ID: <20180816151252.GD10648@kroah.com> (raw)
In-Reply-To: <07e17009-18bb-df72-3408-7e8c0c11e16f@sembritzki.me>
On Thu, Aug 16, 2018 at 03:17:47PM +0200, Yannik Sembritzki wrote:
> On 16.08.2018 15:15, David Howells wrote:
> > I would suggest something like that. I've switched the patches over as has
> > been suggested. I think it makes more sense to create the constant first and
> > then use that.
> >
> > I've also fleshed out the patch description a bit and added cc and Fixes
> > fields as appropriate.
>
> Thanks, that looks good to me.
> I see that you only cc'd stable@ in the (now) second patch. I'm curious,
> will this automatically apply the first patch to stable?
No, but I'll try to remember to do it in order to get it right :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-08-16 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 13:05 [PATCH 1/2] Replace magic for trusting the secondary keyring with #define David Howells
2018-08-16 13:05 ` David Howells
2018-08-16 13:05 ` David Howells
2018-08-16 13:05 ` [PATCH 2/2] Fix kexec forbidding kernels signed with keys in the secondary keyring to boot David Howells
2018-08-16 13:05 ` David Howells
2018-08-16 13:05 ` David Howells
2018-08-16 13:05 ` David Howells
2018-08-16 13:15 ` [PATCH 1/2] Replace magic for trusting the secondary keyring with #define David Howells
2018-08-16 13:15 ` David Howells
2018-08-16 13:15 ` David Howells
2018-08-16 13:17 ` Yannik Sembritzki
2018-08-16 13:17 ` Yannik Sembritzki
2018-08-16 13:17 ` Yannik Sembritzki
2018-08-16 15:12 ` Greg KH [this message]
2018-08-16 15:12 ` Greg KH
2018-08-16 15:12 ` Greg KH
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=20180816151252.GD10648@kroah.com \
--to=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.