[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200321005820.GC7166@linux.intel.com>
Date: Sat, 21 Mar 2020 02:58:20 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: David Howells <dhowells@...hat.com>
Cc: Waiman Long <longman@...hat.com>, James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Mimi Zohar <zohar@...ux.ibm.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, keyrings@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-integrity@...r.kernel.org, netdev@...r.kernel.org,
linux-afs@...ts.infradead.org, Sumit Garg <sumit.garg@...aro.org>,
Jerry Snitselaar <jsnitsel@...hat.com>,
Roberto Sassu <roberto.sassu@...wei.com>,
Eric Biggers <ebiggers@...gle.com>,
Chris von Recklinghausen <crecklin@...hat.com>
Subject: Re: [PATCH v5 2/2] KEYS: Avoid false positive ENOMEM error on key
read
On Fri, Mar 20, 2020 at 11:55:10PM +0000, David Howells wrote:
> Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com> wrote:
>
> > /* Key data can change as we don not hold key->sem. */
>
> I think you mean "we don't".
Oops, typo. Yes, thanks.
/Jarkko
Powered by blists - more mailing lists