From: kernel test robot <ying.huang@linux.intel.com>
To: lkp@lists.01.org
Subject: [list] 4b29978299: dmesg.WARNING:at_lib/list_debug.c:#__list_add()
Date: Mon, 23 Nov 2015 15:35:44 +0800 [thread overview]
Message-ID: <877fl96ucv.fsf@yhuang-dev.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git libnvdimm-pending
commit 4b29978299ae61b278fcbc6cf393c85265d78517 ("list: introduce list_del_poison()")
[ 29.194068] Write protecting the kernel text: 7156k
[ 29.195054] Write protecting the kernel read-only data: 3856k
[ 29.202249] ------------[ cut here ]------------
[ 29.202806] WARNING: CPU: 1 PID: 79 at lib/list_debug.c:27 __list_add+0x125/0x162()
[ 29.203874] list_add attempted on force-poisoned entry
[ 29.204453] Modules linked in:
[ 29.204837] CPU: 1 PID: 79 Comm: init Not tainted 4.4.0-rc1-00027-g4b29978 #1
[ 29.205646] 00000000 00000000 50631de4 412ebc69 50631e0c 50631dfc 4107548d 4132fb1a
[ 29.206726] 50fb9768 40014460 50fb9728 50631e14 410755a2 00000009 50631e0c 41a3ef22
[ 29.207764] 50631e28 50631e34 4132fb1a 41a3ed35 0000001b 41a3ef22 50fb9760 50622380
[ 29.208885] Call Trace:
[ 29.209180] [<412ebc69>] dump_stack+0xb8/0x108
[ 29.209708] [<4107548d>] warn_slowpath_common+0xdb/0x11c
[ 29.210353] [<4132fb1a>] ? __list_add+0x125/0x162
[ 29.210921] [<410755a2>] warn_slowpath_fmt+0x42/0x54
[ 29.211520] [<4132fb1a>] __list_add+0x125/0x162
[ 29.212057] [<411ae802>] list_add+0x18/0x28
[ 29.212552] [<411ae839>] anon_vma_chain_link+0x27/0x51
[ 29.213143] [<411b0afc>] anon_vma_clone+0xda/0x1ae
[ 29.226792] [<411b0c17>] anon_vma_fork+0x47/0x1a9
[ 29.227348] [<41165c91>] dup_mmap+0x253/0x54d
[ 29.227873] [<41073296>] copy_process+0x1000/0x1da6
[ 29.228440] [<4107425a>] _do_fork+0xc4/0x4f0
[ 29.228955] [<4108d546>] ? SyS_rt_sigaction+0xd8/0x165
[ 29.229562] [<41074762>] SyS_clone+0x35/0x61
[ 29.230093] [<41001d04>] do_syscall_32_irqs_on+0x92/0xc0
[ 29.230753] [<416fab0a>] entry_INT80_32+0x2a/0x2a
[ 29.231299] ---[ end trace 28bcbeb98cb33b0e ]---
[ 29.231881] ------------[ cut here ]------------
Thanks,
Ying Huang
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 16956 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <ying.huang@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: lkp@01.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [lkp] [list] 4b29978299: dmesg.WARNING:at_lib/list_debug.c:#__list_add()
Date: Mon, 23 Nov 2015 15:35:44 +0800 [thread overview]
Message-ID: <877fl96ucv.fsf@yhuang-dev.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git libnvdimm-pending
commit 4b29978299ae61b278fcbc6cf393c85265d78517 ("list: introduce list_del_poison()")
[ 29.194068] Write protecting the kernel text: 7156k
[ 29.195054] Write protecting the kernel read-only data: 3856k
[ 29.202249] ------------[ cut here ]------------
[ 29.202806] WARNING: CPU: 1 PID: 79 at lib/list_debug.c:27 __list_add+0x125/0x162()
[ 29.203874] list_add attempted on force-poisoned entry
[ 29.204453] Modules linked in:
[ 29.204837] CPU: 1 PID: 79 Comm: init Not tainted 4.4.0-rc1-00027-g4b29978 #1
[ 29.205646] 00000000 00000000 50631de4 412ebc69 50631e0c 50631dfc 4107548d 4132fb1a
[ 29.206726] 50fb9768 40014460 50fb9728 50631e14 410755a2 00000009 50631e0c 41a3ef22
[ 29.207764] 50631e28 50631e34 4132fb1a 41a3ed35 0000001b 41a3ef22 50fb9760 50622380
[ 29.208885] Call Trace:
[ 29.209180] [<412ebc69>] dump_stack+0xb8/0x108
[ 29.209708] [<4107548d>] warn_slowpath_common+0xdb/0x11c
[ 29.210353] [<4132fb1a>] ? __list_add+0x125/0x162
[ 29.210921] [<410755a2>] warn_slowpath_fmt+0x42/0x54
[ 29.211520] [<4132fb1a>] __list_add+0x125/0x162
[ 29.212057] [<411ae802>] list_add+0x18/0x28
[ 29.212552] [<411ae839>] anon_vma_chain_link+0x27/0x51
[ 29.213143] [<411b0afc>] anon_vma_clone+0xda/0x1ae
[ 29.226792] [<411b0c17>] anon_vma_fork+0x47/0x1a9
[ 29.227348] [<41165c91>] dup_mmap+0x253/0x54d
[ 29.227873] [<41073296>] copy_process+0x1000/0x1da6
[ 29.228440] [<4107425a>] _do_fork+0xc4/0x4f0
[ 29.228955] [<4108d546>] ? SyS_rt_sigaction+0xd8/0x165
[ 29.229562] [<41074762>] SyS_clone+0x35/0x61
[ 29.230093] [<41001d04>] do_syscall_32_irqs_on+0x92/0xc0
[ 29.230753] [<416fab0a>] entry_INT80_32+0x2a/0x2a
[ 29.231299] ---[ end trace 28bcbeb98cb33b0e ]---
[ 29.231881] ------------[ cut here ]------------
Thanks,
Ying Huang
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 16956 bytes --]
next reply other threads:[~2015-11-23 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 7:35 kernel test robot [this message]
2015-11-23 7:35 ` [lkp] [list] 4b29978299: dmesg.WARNING:at_lib/list_debug.c:#__list_add() kernel test robot
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=877fl96ucv.fsf@yhuang-dev.intel.com \
--to=ying.huang@linux.intel.com \
--cc=lkp@lists.01.org \
/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.