[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2866042.1584544464@warthog.procyon.org.uk>
Date: Wed, 18 Mar 2020 15:14:24 +0000
From: David Howells <dhowells@...hat.com>
To: Waiman Long <longman@...hat.com>
Cc: dhowells@...hat.com,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.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 v4 4/4] KEYS: Avoid false positive ENOMEM error on key read
Waiman Long <longman@...hat.com> wrote:
> Doing this is micro-optimization. As the keys subsystem is that
> performance critical, do we need to do that to save a cycle or two while
> making the code a bit harder to read?
It was more sort of a musing comment. Feel free to ignore it. kvfree()
doesn't do this.
David
Powered by blists - more mailing lists