From: Andrew Morton <akpm@linux-foundation.org>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: Matthew Wilcox <willy@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Matthew Wilcox <willy@infradead.org>,
Matthew Wilcox <mawilcox@microsoft.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry_valid
Date: Wed, 18 Jan 2017 16:49:53 -0800 [thread overview]
Message-ID: <20170118164953.430a36a5643e2d05df7322b8@linux-foundation.org> (raw)
In-Reply-To: <20170119004025.GA20827@yexl-desktop>
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 ]---
prev parent reply other threads:[~2017-01-19 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 1:23 kernel test robot
2017-01-18 5:13 ` Matthew Wilcox
2017-01-19 0:41 ` Ye Xiaolong
2017-01-18 21:09 ` Andrew Morton
2017-01-19 0:40 ` Ye Xiaolong
2017-01-19 0:49 ` 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=20170118164953.430a36a5643e2d05df7322b8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mawilcox@microsoft.com \
--cc=ross.zwisler@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
--cc=willy@infradead.org \
--cc=willy@linux.intel.com \
--cc=xiaolong.ye@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
all inboxes | Powered by JetHome®