[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f89b41ea8fc1ab84cc19fd1c1f9b048457bbc28d.camel@linux.intel.com>
Date: Tue, 17 Mar 2020 00:19:06 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: David Howells <dhowells@...hat.com>,
Waiman Long <longman@...hat.com>
Cc: James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Mimi Zohar <zohar@...ux.ibm.com>, keyrings@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-integrity@...r.kernel.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 v3 3/3] KEYS: Use kvmalloc() to better handle large
buffer allocation
On Mon, 2020-03-16 at 14:24 +0000, David Howells wrote:
> I wonder if it's worth merging this into patch 2. I'm not sure it's really
> worth its own patch. If you want to generalise kvzfree(), then that could go
> as its own patch first.
>
> David
Also in the sense that there is no senseful situation where you'd
only wanted to pick either but not both.
/Jarkko
Powered by blists - more mailing lists