From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, Sasha Levin <sasha.levin@oracle.com>,
Andrey Ryabinin <a.ryabinin@samsung.com>,
James Morris <james.l.morris@oracle.com>,
serge@hallyn.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: security: oops on boot in __key_link_begin
Date: Mon, 28 Jul 2014 16:37:02 +0100 [thread overview]
Message-ID: <3112.1406561822@warthog.procyon.org.uk> (raw)
In-Reply-To: <14383.1406559660@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> Sasha Levin <sasha.levin@oracle.com> wrote:
>
> > I've tried keys-next and linux-next for today and it didn't reproduce, but
> > it did show up again when I applied the KASAN patchset (Cc Andrey).
>
> The 'KASAN' patchset?
Never mind. I should've googled first.
David
prev parent reply other threads:[~2014-07-28 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 3:14 security: oops on boot in __key_link_begin Sasha Levin
2014-07-28 11:10 ` David Howells
2014-07-28 11:32 ` David Howells
2014-07-28 14:49 ` Sasha Levin
2014-07-28 15:01 ` David Howells
2014-07-28 15:37 ` David Howells [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=3112.1406561822@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=a.ryabinin@samsung.com \
--cc=james.l.morris@oracle.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=serge@hallyn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.