stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] KEYS: fix freeing uninitialized memory in key_update()
Date: Wed, 31 May 2017 12:07:42 -0700	[thread overview]
Message-ID: <20170531190742.GA72735@gmail.com> (raw)
In-Reply-To: <3742.1491234534@warthog.procyon.org.uk>

On Mon, Apr 03, 2017 at 04:48:54PM +0100, David Howells wrote:
> Pulled.

David, where was this pulled to?  It's not in keys-next at
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git.  Nor did
it show up in v4.12-rc1.

      reply	other threads:[~2017-05-31 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01 22:36 [PATCH] KEYS: fix freeing uninitialized memory in key_update() Eric Biggers
2017-04-03 15:48 ` David Howells
2017-05-31 19:07   ` Eric Biggers [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=20170531190742.GA72735@gmail.com \
    --to=ebiggers3@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=ebiggers@google.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;
as well as URLs for NNTP newsgroup(s).