Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1562176 > unrolled thread

Re: [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry_valid

Started byAndrew Morton <akpm@linux-foundation.org>
First post2017-01-18 22:10 +0100
Last post2017-01-19 02:00 +0100
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [lkp-robot] e5a305ac4a:  WARNING:at_lib/list_debug.c:#__list_del_entry_valid Andrew Morton <akpm@linux-foundation.org> - 2017-01-18 22:10 +0100
    Re: [lkp-robot] e5a305ac4a:  WARNING:at_lib/list_debug.c:#__list_del_entry_valid Ye Xiaolong <xiaolong.ye@intel.com> - 2017-01-19 01:50 +0100
      Re: [lkp-robot] e5a305ac4a:  WARNING:at_lib/list_debug.c:#__list_del_entry_valid Andrew Morton <akpm@linux-foundation.org> - 2017-01-19 02:00 +0100

#1562176 — Re: [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry_valid

FromAndrew Morton <akpm@linux-foundation.org>
Date2017-01-18 22:10 +0100
SubjectRe: [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry_valid
Message-ID<t15Et-O4-13@gated-at.bofh.it>
On Wed, 18 Jan 2017 09:23:04 +0800 kernel test robot <xiaolong.ye@intel.com> wrote:

> 
> FYI, we noticed the following commit:
> 
> commit: e5a305ac4a5233e039586c97f4ea643a4c7dc484 ("Reimplement IDR and IDA using the radix tree")
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> 
> in testcase: trinity
> with following parameters:
> 
> 	runtime: 300s
> 
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://codemonkey.org.uk/projects/trinity/
> 
> 
> on test machine: qemu-system-i386 -enable-kvm -m 256M
> 
> ...
> 
> [    2.963488] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
> [    2.964998] evbug: Connected device: input1 (AT Translated Set 2 keyboard at isa0060/serio0/input0)
> [    2.966202] ------------[ cut here ]------------
> [    2.966844] WARNING: CPU: 0 PID: 14 at lib/list_debug.c:55 __list_del_entry_valid+0x43/0xb0
> [    2.968198] list_del corruption. next->prev should be bc904168, but was b215df80
> [    2.969171] CPU: 0 PID: 14 Comm: kworker/0:1 Not tainted 4.10.0-rc2-02114-ge5a305a #1
> [    2.970209] Workqueue: events_long serio_handle_event
> [    2.970893] Call Trace:
> [    2.971217]  dump_stack+0x16/0x19
> [    2.971677]  __warn+0xa5/0xc0
> [    2.972074]  warn_slowpath_fmt+0x28/0x30

Thanks.

That isn't a very good backtrace.  Is that really the entire output?

> 
> To reproduce:
> 
>         git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>         cd lkp-tests
>         bin/lkp qemu -k <bzImage> job-script  # job-script is attached in this email

[toc] | [next] | [standalone]


#1562348

FromYe Xiaolong <xiaolong.ye@intel.com>
Date2017-01-19 01:50 +0100
Message-ID<t195o-2Ne-19@gated-at.bofh.it>
In reply to#1562176
On 01/18, Andrew Morton wrote:
>On Wed, 18 Jan 2017 09:23:04 +0800 kernel test robot <xiaolong.ye@intel.com> wrote:
>
>> 
>> FYI, we noticed the following commit:
>> 
>> commit: e5a305ac4a5233e039586c97f4ea643a4c7dc484 ("Reimplement IDR and IDA using the radix tree")
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> 
>> in testcase: trinity
>> with following parameters:
>> 
>> 	runtime: 300s
>> 
>> test-description: Trinity is a linux system call fuzz tester.
>> test-url: http://codemonkey.org.uk/projects/trinity/
>> 
>> 
>> on test machine: qemu-system-i386 -enable-kvm -m 256M
>> 
>> ...
>> 
>> [    2.963488] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
>> [    2.964998] evbug: Connected device: input1 (AT Translated Set 2 keyboard at isa0060/serio0/input0)
>> [    2.966202] ------------[ cut here ]------------
>> [    2.966844] WARNING: CPU: 0 PID: 14 at lib/list_debug.c:55 __list_del_entry_valid+0x43/0xb0
>> [    2.968198] list_del corruption. next->prev should be bc904168, but was b215df80
>> [    2.969171] CPU: 0 PID: 14 Comm: kworker/0:1 Not tainted 4.10.0-rc2-02114-ge5a305a #1
>> [    2.970209] Workqueue: events_long serio_handle_event
>> [    2.970893] Call Trace:
>> [    2.971217]  dump_stack+0x16/0x19
>> [    2.971677]  __warn+0xa5/0xc0
>> [    2.972074]  warn_slowpath_fmt+0x28/0x30
>
>Thanks.
>
>That isn't a very good backtrace.  Is that really the entire output?

Hmm, it is a fragment of the entire backtrace, the whole output can be found in
attached dmesg.xz, we'll try to paste the whole backtrace next time.

Thanks,
Xiaolong
>
>> 
>> To reproduce:
>> 
>>         git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>>         cd lkp-tests
>>         bin/lkp qemu -k <bzImage> job-script  # job-script is attached in this email
>

[toc] | [prev] | [next] | [standalone]


#1562350

FromAndrew Morton <akpm@linux-foundation.org>
Date2017-01-19 02:00 +0100
Message-ID<t19f3-2Qy-1@gated-at.bofh.it>
In reply to#1562348
On Thu, 19 Jan 2017 08:40:25 +0800 Ye Xiaolong <xiaolong.ye@intel.com> wrote:

> On 01/18, Andrew Morton wrote:
> >On Wed, 18 Jan 2017 09:23:04 +0800 kernel test robot <xiaolong.ye@intel.com> wrote:
> >
> >> 
> >> FYI, we noticed the following commit:
> >> 
> >> commit: e5a305ac4a5233e039586c97f4ea643a4c7dc484 ("Reimplement IDR and IDA using the radix tree")
> >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> >> 
> >> in testcase: trinity
> >> with following parameters:
> >> 
> >> 	runtime: 300s
> >> 
> >> test-description: Trinity is a linux system call fuzz tester.
> >> test-url: http://codemonkey.org.uk/projects/trinity/
> >> 
> >> 
> >> on test machine: qemu-system-i386 -enable-kvm -m 256M
> >> 
> >> ...
> >> 
> >> [    2.963488] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
> >> [    2.964998] evbug: Connected device: input1 (AT Translated Set 2 keyboard at isa0060/serio0/input0)
> >> [    2.966202] ------------[ cut here ]------------
> >> [    2.966844] WARNING: CPU: 0 PID: 14 at lib/list_debug.c:55 __list_del_entry_valid+0x43/0xb0
> >> [    2.968198] list_del corruption. next->prev should be bc904168, but was b215df80
> >> [    2.969171] CPU: 0 PID: 14 Comm: kworker/0:1 Not tainted 4.10.0-rc2-02114-ge5a305a #1
> >> [    2.970209] Workqueue: events_long serio_handle_event
> >> [    2.970893] Call Trace:
> >> [    2.971217]  dump_stack+0x16/0x19
> >> [    2.971677]  __warn+0xa5/0xc0
> >> [    2.972074]  warn_slowpath_fmt+0x28/0x30
> >
> >Thanks.
> >
> >That isn't a very good backtrace.  Is that really the entire output?
> 
> Hmm, it is a fragment of the entire backtrace, the whole output can be found in
> attached dmesg.xz, we'll try to paste the whole backtrace next time.

Ah, OK, thanks.  This:

[    2.966202] ------------[ cut here ]------------
[    2.966844] WARNING: CPU: 0 PID: 14 at lib/list_debug.c:55 __list_del_entry_valid+0x43/0xb0
[    2.968198] list_del corruption. next->prev should be bc904168, but was b215df80
[    2.969171] CPU: 0 PID: 14 Comm: kworker/0:1 Not tainted 4.10.0-rc2-02114-ge5a305a #1
[    2.970209] Workqueue: events_long serio_handle_event
[    2.970893] Call Trace:
[    2.971217]  dump_stack+0x16/0x19
[    2.971677]  __warn+0xa5/0xc0
[    2.972074]  warn_slowpath_fmt+0x28/0x30
[    2.972587]  __list_del_entry_valid+0x43/0xb0
[    2.973186]  devices_kset_move_last+0x2d/0x80
[    2.973815]  ? driver_sysfs_add+0x5a/0x80
[    2.974341]  really_probe+0x127/0x230
[    2.974849]  __driver_attach+0x7f/0xa0
[    2.975345]  ? really_probe+0x230/0x230
[    2.975873]  bus_for_each_dev+0x4f/0x80
[    2.976375]  driver_attach+0x14/0x20
[    2.976868]  ? really_probe+0x230/0x230
[    2.977370]  serio_handle_event+0x1bb/0x230
[    2.977953]  ? process_one_work+0x105/0x3f0
[    2.978504]  process_one_work+0x153/0x3f0
[    2.979054]  ? process_one_work+0x105/0x3f0
[    2.979596]  worker_thread+0x39/0x460
[    2.980104]  ? _raw_spin_unlock_irqrestore+0x3d/0x50
[    2.980803]  kthread+0xd9/0x110
[    2.981211]  ? process_one_work+0x3f0/0x3f0
[    2.981782]  ? __kthread_create_on_node+0x190/0x190
[    2.982426]  ret_from_fork+0x19/0x30
[    2.982919] ---[ end trace 842edab4ceba3acb ]---

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web