From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [RFC][PATCH 0/6] KEYS: Fixes
Date: Fri, 23 Feb 2018 11:24:05 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1802231123500.21075@namei.org> (raw)
In-Reply-To: <29946.1519343081@warthog.procyon.org.uk>
On Thu, 22 Feb 2018, David Howells wrote:
> I've posted an update that converts the min() to a min_t() and tagged it:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/tag/?h=keys-fixes-20180222-2
>
> Do you want me to repost the patches?
Nope, I'll grab them from there.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2018-02-23 0:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 16:20 [RFC][PATCH 0/6] KEYS: Fixes David Howells
2018-02-22 16:20 ` [PATCH 1/6] PKCS#7: fix certificate chain verification David Howells
2018-02-22 16:20 ` [PATCH 2/6] PKCS#7: fix certificate blacklisting David Howells
2018-02-22 16:20 ` [PATCH 3/6] PKCS#7: fix direct verification of SignerInfo signature David Howells
2018-02-22 16:20 ` [PATCH 4/6] X.509: fix BUG_ON() when hash algorithm is unsupported David Howells
2018-02-22 16:21 ` [PATCH 5/6] X.509: fix NULL dereference when restricting key with unsupported_sig David Howells
2018-02-22 16:21 ` [PATCH 6/6] KEYS: Use individual pages in big_key for crypto buffers David Howells
2018-02-22 23:42 ` David Howells
2018-02-22 16:27 ` [RFC][PATCH 0/6] KEYS: Fixes David Howells
2018-02-22 23:44 ` David Howells
2018-02-23 0:24 ` James Morris [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=alpine.LRH.2.21.1802231123500.21075@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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