linux-kernel - Re: [PATCH 1/2] Replace magic for trusting the secondary keyring with #define

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <07e17009-18bb-df72-3408-7e8c0c11e16f@sembritzki.me>
Date:   Thu, 16 Aug 2018 15:17:47 +0200
From:   Yannik Sembritzki <yannik@...britzki.me>
To:     David Howells <dhowells@...hat.com>
Cc:     torvalds@...ux-foundation.org, keyrings@...r.kernel.org,
        linux-security-module@...r.kernel.org,
        linux-kernel@...r.kernel.org, dyoung@...hat.com,
        James.Bottomley@...senPartnership.com, gregkh@...uxfoundation.org
Subject: Re: [PATCH 1/2] Replace magic for trusting the secondary keyring with
 #define

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?

Yannik