From: Dave Chinner <david@fromorbit.com>
To: "Michael L. Semon" <mlsemon35@gmail.com>
Cc: Mark Tinguely <tinguely@sgi.com>, xfs@oss.sgi.com
Subject: Re: Null pointer dereference while at ACL limit on v5 XFS
Date: Tue, 24 Jun 2014 14:04:34 +1000 [thread overview]
Message-ID: <20140624040434.GC9508@dastard> (raw)
In-Reply-To: <53A8F1AC.90109@gmail.com>
On Mon, Jun 23, 2014 at 11:34:04PM -0400, Michael L. Semon wrote:
> [ 1068.431391] ------------[ cut here ]------------
> [ 1068.431566] WARNING: CPU: 0 PID: 41 at lib/list_debug.c:59 __list_del_entry+0xce/0x110()
> [ 1068.431596] list_del corruption. prev->next should be db5bf580, but was (null)
Ok, so the current log item points to a log item that has
null pointers (i.e. not on the list).
> [ 1068.431629] CPU: 0 PID: 41 Comm: kworker/0:1H Not tainted 3.16.0-rc1+ #3
> [ 1068.431656] Hardware name: Dell Computer Corporation L733r /CA810E , BIOS A14 09/05/2001
> [ 1068.431697] Workqueue: xfslogd xfs_buf_iodone_work
> [ 1068.431738] 00000000 00000000 de92fc24 c15d4e76 de92fc68 de92fc58 c103ca33 c1737648
> [ 1068.431891] de92fc84 00000029 c173705a 0000003b c13c3e9e 0000003b c13c3e9e 0000003b
> [ 1068.432115] db5bf580 00000001 de92fc70 c103cab3 00000009 de92fc68 c1737648 de92fc84
> [ 1068.432267] Call Trace:
> [ 1068.432329] [<c15d4e76>] dump_stack+0x48/0x60
> [ 1068.432386] [<c103ca33>] warn_slowpath_common+0x83/0xa0
> [ 1068.432433] [<c13c3e9e>] ? __list_del_entry+0xce/0x110
> [ 1068.432478] [<c13c3e9e>] ? __list_del_entry+0xce/0x110
> [ 1068.432524] [<c103cab3>] warn_slowpath_fmt+0x33/0x40
> [ 1068.432569] [<c13c3e9e>] __list_del_entry+0xce/0x110
> [ 1068.432615] [<c13c3eeb>] list_del+0xb/0x20
> [ 1068.432674] [<c126eb4d>] xfs_ail_delete+0x1d/0x60
....
> [ 1068.433567] ---[ end trace 60289514948e4bd7 ]---
> [ 1068.433603] BUG: unable to handle kernel NULL pointer dereference at 0000000c
> [ 1068.433795] IP: [<c126eac8>] xfs_ail_check+0x58/0xc0
And that's trying to dereference a pointer from an item that is not
on the list....
So there's linked list corruption occurring here.
> I can reproduce the oops in kernel 3.15.0, perhaps with xfs-oss/for-next
> merged, but there's no vmlinux to go with the kernel. Therefore, I'll have
> to resort to other means (rebuilt kernel with netconsole, re-attaching the
> serial cable, etc.) to get the full crash log.
How far back can you reproduce it? If it's a recent occurrence, can
you bisect it?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-24 4:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 21:48 Null pointer dereference while at ACL limit on v5 XFS Michael L. Semon
2014-06-23 22:08 ` Mark Tinguely
2014-06-23 22:13 ` Mark Tinguely
2014-06-24 3:34 ` Michael L. Semon
2014-06-24 4:04 ` Dave Chinner [this message]
2014-06-24 13:31 ` Michael L. Semon
2014-07-01 22:27 ` Michael L. Semon
2014-07-03 11:56 ` Jeff Liu
2014-06-24 16:31 ` Mark Tinguely
2014-06-24 18:25 ` Mark Tinguely
2014-06-24 2:18 ` Dave Chinner
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=20140624040434.GC9508@dastard \
--to=david@fromorbit.com \
--cc=mlsemon35@gmail.com \
--cc=tinguely@sgi.com \
--cc=xfs@oss.sgi.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