From: Dave Chinner <david@fromorbit.com>
To: CAI Qian <caiqian@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 3.9.2: xfstests triggered panic
Date: Wed, 22 May 2013 19:53:00 +1000 [thread overview]
Message-ID: <20130522095300.GK29466@dastard> (raw)
In-Reply-To: <1805266998.4499261.1369211998387.JavaMail.root@redhat.com>
On Wed, May 22, 2013 at 04:39:58AM -0400, CAI Qian wrote:
> Reproduced on almost all s390x guests by running xfstests.
>
> 14634.396658¨ XFS (dm-1): Mounting Filesystem
> 14634.525522¨ XFS (dm-1): Ending clean mount
> 14640.413007¨ <000000000017c6d4>¨ idle_balance+0x1a0/0x340
> 14640.413010¨ <000000000063303e>¨ __schedule+0xa22/0xaf0
> 14640.428279¨ <0000000000630da6>¨ schedule_timeout+0x186/0x2c0
> 14640.428289¨ <00000000001cf864>¨ rcu_gp_kthread+0x1bc/0x298
> 14640.428300¨ <0000000000158c5a>¨ kthread+0xe6/0xec
> 14640.428304¨ <0000000000634de6>¨ kernel_thread_starter+0x6/0xc
> 14640.428308¨ <0000000000634de0>¨ kernel_thread_starter+0x0/0xc
> 14640.428311¨ Last Breaking-Event-Address:
> 14640.428314¨ <000000000016bd76>¨ walk_tg_tree_from+0x3a/0xf4
> 14640.428319¨ list_add corruption. next->prev should be prev (0000000000000918
> ), but was (null). (next= (null)).
Where's XFS in this? walk_tg_tree_from() is part of the scheduler
code. This kind of implies a stack corruption....
> Sometimes, this pops up,
> [16907.275002] WARNING: at kernel/rcutree.c:1960
>
> or this,
> 15316.154171¨ XFS (dm-1): Mounting Filesystem
> 15316.255796¨ XFS (dm-1): Ending clean mount
> 15320.364246¨ 00000000006367a2: e310b0080004 lg %r1,8(%r
> 11)
> 15320.364249¨ 00000000006367a8: 41101010 la %r1,16(%
> r1)
> 15320.364251¨ 00000000006367ac: e33010000004 lg %r3,0(%r
> 1)
> 15320.364252¨ Call Trace:
> 15320.364252¨ Last Breaking-Event-Address:
> 15320.364253¨ � <0000000000000000>¨ Kernel stack overflow.
> 15320.364308¨ CPU: 0 Tainted: GF W 3.9.2 #1
> 15320.364309¨ Process rhts-test-runne (pid: 625, task: 000000003dccc890, ksp: 0
.... and there you go - a stack overflow. Your kernel stack size is
too small.
I'd suggest that you need 16k stacks on s390 - IIRC every function
call has 128 byte stack frame, and there are call chains 70-80
functions deep in the storage stack...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2013-05-22 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40971621.4497871.1369211701112.JavaMail.root@redhat.com>
2013-05-22 8:39 ` 3.9.2: xfstests triggered panic CAI Qian
2013-05-22 9:53 ` Dave Chinner [this message]
2013-05-23 3:16 ` CAI Qian
2013-05-23 3:46 ` Dave Chinner
2013-05-23 4:11 ` CAI Qian
2013-05-23 4:57 ` 3.9.2/3.9.3: stack overrun on s390x and ppc64 (WAS Re: 3.9.2: xfstests triggered panic) CAI Qian
2013-05-24 3:33 ` CAI Qian
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=20130522095300.GK29466@dastard \
--to=david@fromorbit.com \
--cc=caiqian@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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