From: David Howells <dhowells@redhat.com>
To: Waiman Long <longman@redhat.com>
Cc: dhowells@redhat.com,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Mimi Zohar <zohar@linux.ibm.com>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org,
Sumit Garg <sumit.garg@linaro.org>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Roberto Sassu <roberto.sassu@huawei.com>,
Eric Biggers <ebiggers@google.com>,
Chris von Recklinghausen <crecklin@redhat.com>
Subject: Re: [PATCH v3 3/3] KEYS: Use kvmalloc() to better handle large buffer allocation
Date: Mon, 16 Mar 2020 14:24:32 +0000 [thread overview]
Message-ID: <1809107.1584368672@warthog.procyon.org.uk> (raw)
In-Reply-To: <20200313152102.1707-4-longman@redhat.com>
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
next prev parent reply other threads:[~2020-03-16 14:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 15:20 [PATCH v3 0/3] KEYS: Read keys to internal buffer & then copy to userspace Waiman Long
2020-03-13 15:21 ` [PATCH v3 1/3] KEYS: Don't write out to userspace while holding key semaphore Waiman Long
2020-03-15 19:21 ` Jarkko Sakkinen
2020-03-15 21:27 ` Jarkko Sakkinen
2020-03-16 11:22 ` David Howells
2020-03-16 13:53 ` Jarkko Sakkinen
2020-03-16 16:33 ` Waiman Long
2020-03-17 18:10 ` Waiman Long
2020-03-16 11:34 ` David Howells
2020-03-13 15:21 ` [PATCH v3 2/3] KEYS: Avoid false positive ENOMEM error on key read Waiman Long
2020-03-15 21:32 ` Jarkko Sakkinen
2020-03-17 18:36 ` Waiman Long
2020-03-13 15:21 ` [PATCH v3 3/3] KEYS: Use kvmalloc() to better handle large buffer allocation Waiman Long
2020-03-13 16:43 ` Eric Biggers
2020-03-13 17:49 ` Waiman Long
2020-03-15 21:52 ` Jarkko Sakkinen
2020-03-15 22:01 ` Waiman Long
2020-03-16 11:50 ` [PATCH v3 1/3] KEYS: Don't write out to userspace while holding key semaphore David Howells
2020-03-17 18:09 ` Waiman Long
2020-03-16 14:24 ` David Howells [this message]
2020-03-16 15:21 ` [PATCH v3 3/3] KEYS: Use kvmalloc() to better handle large buffer allocation Waiman Long
2020-03-16 22:19 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1809107.1584368672@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=crecklin@redhat.com \
--cc=ebiggers@google.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=jsnitsel@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=longman@redhat.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=sumit.garg@linaro.org \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).