From: David Howells <dhowells@redhat.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: dhowells@redhat.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 12:10:04 +0100 [thread overview]
Message-ID: <23131.1406545804@warthog.procyon.org.uk> (raw)
In-Reply-To: <53D31D16.1030806@oracle.com>
Sasha Levin <sasha.levin@oracle.com> wrote:
> I'm (sometimes) seeing the following when booting the most recent -next
> kernel:
Can you try with my keys-next branch?
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-next
That should cut out any interference from other -next stuff.
> [ 31.330473] RIP: assoc_array_insert (lib/assoc_array.c:480 lib/assoc_array.c:1021)
> ...
> [ 31.330473] ? get_parent_ip (kernel/sched/core.c:2561)
> [ 31.330473] ? preempt_count_sub (kernel/sched/core.c:2617)
> [ 31.330473] ? put_lock_stats.isra.13 (./arch/x86/include/asm/preempt.h:98 kernel/locking/lockdep.c:254)
> [ 31.330473] ? __key_link_begin (./arch/x86/include/asm/bitops.h:311 security/keys/keyring.c:1073)
> [ 31.330473] ? __key_link_begin (./arch/x86/include/asm/bitops.h:311 security/keys/keyring.c:1073)
> [ 31.330473] __key_link_begin (security/keys/keyring.c:1088)
> [ 31.330473] key_create_or_update (security/keys/key.c:840 (discriminator 4))
> [ 31.330473] load_system_certificate_list (kernel/system_keyring.c:88)
Given where this is happening, I'm surprised that it doesn't break every
time. I wonder if it might be some uninitialised memory somewhere:-/
David
next prev parent reply other threads:[~2014-07-28 11:10 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 [this message]
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
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=23131.1406545804@warthog.procyon.org.uk \
--to=dhowells@redhat.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.