From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: dmitry.kasatkin@gmail.com, james.l.morris@oracle.com,
serge@hallyn.com, linux-ima-devel@lists.sourceforge.net,
linux-ima-user@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: ima: BUG: spinlock bad magic
Date: Mon, 12 Sep 2016 06:58:36 -0400 [thread overview]
Message-ID: <1473677916.3785.15.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACT4Y+aZz079jQQhyHG7Uzy-saWDFtnao5mPHSB_g2d20UXMfw@mail.gmail.com>
Hi Dmitry,
On Fri, 2016-09-09 at 21:19 +0200, Dmitry Vyukov wrote:
> Hello,
>
> While booting linux-next on 4affa544adb8077403893e62b9e327fcf87de6f7
> (Sep 8), I've got the following BUG:
>
> BUG: spinlock bad magic on CPU#3, swapper/0/1
> lock: template_list+0x0/0x60, .magic: 00000000, .owner: <none>/-1,
> .owner_cpu: 0
> CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.8.0-rc5-next-20160905+ #14
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> ffffffff886b6fe0 ffff88003ebf7d48 ffffffff82db81a9 ffffffff870b20c0
> fffffbfff10d6dfc ffffffff8a6ac660 ffff88003ebee040 dffffc0000000000
> ffffffff88ad2ca0 dffffc0000000000 ffff88003ebf7d80 ffffffff814a71fd
> Call Trace:
> [< inline >] __dump_stack lib/dump_stack.c:15
> [<ffffffff82db81a9>] dump_stack+0x12e/0x185 lib/dump_stack.c:51
> [<ffffffff814a71fd>] spin_dump+0x14d/0x280 kernel/locking/spinlock_debug.c:67
> [< inline >] spin_bug kernel/locking/spinlock_debug.c:75
> [< inline >] debug_spin_lock_before kernel/locking/spinlock_debug.c:83
> [<ffffffff814a75e4>] do_raw_spin_lock+0x224/0x2b0
> kernel/locking/spinlock_debug.c:135
> [< inline >] __raw_spin_lock ./include/linux/spinlock_api_smp.h:145
> [<ffffffff86e19a4b>] _raw_spin_lock+0x3b/0x50 kernel/locking/spinlock.c:151
> [< inline >] spin_lock ./include/linux/spinlock.h:302
> [<ffffffff896de48a>] ima_init_template_list+0x4c/0x10c
> security/integrity/ima/ima_template.c:218
> [<ffffffff896ddb26>] init_ima+0xf/0x44 security/integrity/ima/ima_main.c:421
> [<ffffffff81002310>] do_one_initcall+0xa0/0x2b0 init/main.c:782
> [< inline >] do_initcall_level init/main.c:848
> [< inline >] do_initcalls init/main.c:856
> [< inline >] do_basic_setup init/main.c:874
> [<ffffffff8963fd43>] kernel_init_freeable+0x476/0x52f init/main.c:1021
> [<ffffffff86dff183>] kernel_init+0x13/0x160 init/main.c:947
> [<ffffffff86e1ab4a>] ret_from_fork+0x2a/0x40 arch/x86/entry/entry_64.S:431
>
> Seems to be caused by:
>
> commit 5d74ec48cc8fd2109001c36bada5bf69c046b487
> Author: Mimi Zohar <zohar@linux.vnet.ibm.com>
> Date: Sat Sep 3 15:20:40 2016 +1000
> ima: store the builtin/custom template definitions in a list
Thank you for reporting this bug. The fix will be included in the v4
post.
Mimi
prev parent reply other threads:[~2016-09-12 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 19:19 ima: BUG: spinlock bad magic Dmitry Vyukov
2016-09-12 10:58 ` Mimi Zohar [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=1473677916.3785.15.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=dvyukov@google.com \
--cc=james.l.morris@oracle.com \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-ima-user@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=syzkaller@googlegroups.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.