From: Waiman Long <longman@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Mimi Zohar <zohar@linux.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org, netdev@vger.kernel.org,
linux-afs@lists.infradead.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 v5 1/2] KEYS: Don't write out to userspace while holding key semaphore
Date: Fri, 20 Mar 2020 09:56:42 -0400 [thread overview]
Message-ID: <69678e1c-dfbe-7484-85ad-601ebe23c90d@redhat.com> (raw)
In-Reply-To: <3251035.1584692419@warthog.procyon.org.uk>
On 3/20/20 4:20 AM, David Howells wrote:
> Waiman Long <longman@redhat.com> wrote:
>
>> + if ((ret > 0) && (ret <= buflen)) {
> That's a bit excessive on the bracketage, btw, but don't worry about it unless
> you respin the patches.
Got it.
Thanks,
Longman
prev parent reply other threads:[~2020-03-20 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 22:14 [PATCH v5 0/2] KEYS: Read keys to internal buffer & then copy to userspace Waiman Long
2020-03-18 22:14 ` [PATCH v5 1/2] KEYS: Don't write out to userspace while holding key semaphore Waiman Long
2020-03-18 22:14 ` [PATCH v5 2/2] KEYS: Avoid false positive ENOMEM error on key read Waiman Long
2020-03-19 19:46 ` Jarkko Sakkinen
2020-03-20 0:07 ` Waiman Long
2020-03-20 2:07 ` Jarkko Sakkinen
2020-03-20 13:27 ` Waiman Long
2020-03-20 14:35 ` Jarkko Sakkinen
2020-03-20 15:09 ` Waiman Long
2020-03-20 23:55 ` David Howells
2020-03-21 0:58 ` Jarkko Sakkinen
2020-03-20 8:20 ` [PATCH v5 1/2] KEYS: Don't write out to userspace while holding key semaphore David Howells
2020-03-20 13:56 ` Waiman Long [this message]
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=69678e1c-dfbe-7484-85ad-601ebe23c90d@redhat.com \
--to=longman@redhat.com \
--cc=crecklin@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@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=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).