[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YGYjjpoj1uMn1VEd@zeniv-ca.linux.org.uk>
Date: Thu, 1 Apr 2021 19:48:30 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Roy Yang <royyang@...gle.com>
Cc: keescook@...omium.org, akpm@...ux-foundation.org,
alex.popov@...ux.com, ard.biesheuvel@...aro.org,
catalin.marinas@....com, corbet@....net, david@...hat.com,
elena.reshetova@...el.com, glider@...gle.com, jannh@...gle.com,
kernel-hardening@...ts.openwall.com,
linux-arm-kernel@...ts.infradead.org,
linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, luto@...nel.org, mark.rutland@....com,
peterz@...radead.org, rdunlap@...radead.org, rppt@...ux.ibm.com,
tglx@...utronix.de, vbabka@...e.cz, will@...nel.org, x86@...nel.org
Subject: Re: [PATCH] Where we are for this patch?
On Thu, Apr 01, 2021 at 12:17:44PM -0700, Roy Yang wrote:
> Both Android and Chrome OS really want this feature; For Container-Optimized OS, we have customers
> interested in the defense too.
>
> Thank you very much.
>
> Change-Id: I1eb1b726007aa8f9c374b934cc1c690fb4924aa3
You forgot to tell what patch you are refering to. Your
Change-Id (whatever the hell that is) doesn't help at all. Don't
assume that keys in your internal database make sense for the
rest of the world, especially when they appear to contain a hash
of something...
Powered by blists - more mailing lists