From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <fengguang.wu@intel.com>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
wfg@linux.intel.com
Subject: Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()
Date: Tue, 1 Mar 2016 10:33:44 -0800 [thread overview]
Message-ID: <20160301103344.6f3095a269db284fbe0c3c2c@linux-foundation.org> (raw)
In-Reply-To: <56aa2b47.MwdlkrzZ08oDKqh8%fengguang.wu@intel.com>
On Thu, 28 Jan 2016 22:52:55 +0800 kernel test robot <fengguang.wu@intel.com> wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit a1fd55538cae9f411059c9b067a3d48c41aa876b
> Author: Jesper Dangaard Brouer <brouer@redhat.com>
> AuthorDate: Thu Jan 28 09:47:16 2016 +1100
> Commit: Stephen Rothwell <sfr@canb.auug.org.au>
> CommitDate: Thu Jan 28 09:47:16 2016 +1100
>
> slab: use slab_pre_alloc_hook in SLAB allocator shared with SLUB
>
> ...
>
> [ 0.000000] ------------[ cut here ]------------
> [ 0.000000] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller+0x341/0x380()
> [ 0.000000] DEBUG_LOCKS_WARN_ON(unlikely(early_boot_irqs_disabled))
> [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.5.0-rc1-00069-ga1fd555 #1
> [ 0.000000] ffffffff82403dd8 ffffffff82403d90 ffffffff813b937d ffffffff82403dc8
> [ 0.000000] ffffffff810eb4d3 ffffffff812617cc 0000000000000001 ffff88000fcc50a8
> [ 0.000000] ffff8800000984c0 00000000024000c0 ffffffff82403e28 ffffffff810eb5c7
> [ 0.000000] Call Trace:
> [ 0.000000] [<ffffffff813b937d>] dump_stack+0x27/0x3a
> [ 0.000000] [<ffffffff810eb4d3>] warn_slowpath_common+0xa3/0x100
> [ 0.000000] [<ffffffff812617cc>] ? cache_alloc_refill+0x7ac/0x910
> [ 0.000000] [<ffffffff810eb5c7>] warn_slowpath_fmt+0x57/0x70
> [ 0.000000] [<ffffffff81143e61>] trace_hardirqs_on_caller+0x341/0x380
> [ 0.000000] [<ffffffff81143ebd>] trace_hardirqs_on+0x1d/0x30
> [ 0.000000] [<ffffffff812617cc>] cache_alloc_refill+0x7ac/0x910
> [ 0.000000] [<ffffffff8121df6a>] ? pcpu_mem_zalloc+0x5a/0xc0
> [ 0.000000] [<ffffffff81261fce>] __kmalloc+0x24e/0x440
> [ 0.000000] [<ffffffff8121df6a>] pcpu_mem_zalloc+0x5a/0xc0
> [ 0.000000] [<ffffffff829213aa>] percpu_init_late+0x4d/0xbb
The next patch
(http://ozlabs.org/~akpm/mmotm/broken-out/slab-use-slab_pre_alloc_hook-in-slab-allocator-shared-with-slub-fix.patch)
should have fixed this?
> [ 0.000000] [<ffffffff828f41c9>] start_kernel+0x30b/0x6e1
> [ 0.000000] [<ffffffff828f3120>] ? early_idt_handler_array+0x120/0x120
> [ 0.000000] [<ffffffff828f332f>] x86_64_start_reservations+0x46/0x4f
> [ 0.000000] [<ffffffff828f34d4>] x86_64_start_kernel+0x19c/0x1b2
> [ 0.000000] ---[ end trace cb88537fdc8fa200 ]---
>
> ...
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-03-01 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 14:52 kernel test robot
2016-01-28 17:47 ` Jesper Dangaard Brouer
2016-01-30 7:09 ` Valdis.Kletnieks
2016-01-30 17:46 ` Jesper Dangaard Brouer
2016-01-31 2:15 ` Stephen Rothwell
2016-01-31 18:40 ` Jesper Dangaard Brouer
2016-01-31 20:34 ` Stephen Rothwell
2016-02-02 19:12 ` Valdis.Kletnieks
2016-03-01 18:33 ` Andrew Morton [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=20160301103344.6f3095a269db284fbe0c3c2c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=wfg@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox