lkml.org 
[lkml]   [2014]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: security: oops on boot in __key_link_begin
    Date
    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


    \
     
     \ /
      Last update: 2014-07-28 13:41    [W:2.924 / U:0.500 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site