From: Eric Sandeen <sandeen@sandeen.net>
To: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
Cc: xfs@oss.sgi.com
Subject: Re: kernel panic - stack-protector: kernel stack is corrupted in: f87aca93
Date: Mon, 28 Feb 2011 18:00:46 -0600 [thread overview]
Message-ID: <4D6C372E.6030105@sandeen.net> (raw)
In-Reply-To: <4D6C28A5.60905@mnsu.edu>
On 2/28/11 4:58 PM, Jeffrey Hundstad wrote:
> Hello,
>
> I'm compiling the main Linux branch commit 493f3358cb289ccf716c5a14fa5bb52ab75943e5 with no other patches. It boots and seems to operate fine. When I do an xfs_fsr it Kernel panics. I can easily reproduce it
>
> Kernel Panic: (hand copied, photo available)
>
> Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: f87aca93
>
> Pid: 262, comm: xfs_fsr Not tainted 2.6.38-rc6-493f3358cb2+ #1
> Call Trace:
>
> [<c12991ac>] ? panic+0x50/0x150
> [<c102ed71>] ? __stack_chk_fail+0x10/0x18
> [<f87aca93>] ? xfs_ioc_fsgeometry_v1+0x56/0x5d [xfs]
> [<f87aca93>] ? xfs_ioc_fsgeometry_v1+0x56/0x5d [xfs]
> [<f87ae062>] ? xfs_file_ioctl+0x33c/0x6fe [xfs]
> [<c1047f1a>] ? sched_clock_cpu+0x130/0x140
> [<c1050f41>] ? trace_hardirqs_off+0xb/0xd
> [<c1047f57>] ? local_clock+0x2d/0x4e
> [<c1050f6e>] ? lock_release_holdtime+0x2b/0xcd
> [<c10a925a>] ? check_valid_pointer+0x1c/0x48
> [<c10a99c8>] ? check_object+0x122/0x156
> [<f87add26>] ? xfs_file_ioctl+0x0/0x6fe [xfs]
> [<c10bf5c9>] ? do_vfs_ioctl+0x483/0x4c8
> [<c10aab72>] ? kmeme_chache_free+0x8f/0x9b
> [<c10b41b4>] ? fcheck_files+0xa1/0xd0
> [<c10bf64f>] ? sys_ioctl+0x41/0x61
> [<c1002893>] ? sysenter_do_call+0x12/0x32
>
>
>
> You can find the config, initrd.img, vmlinuz and crash screen at:
> http://krypton.mnsu.edu/~j3gum/linux-error-20110228/
>
> - gcc (Debian 4.4.5-13) 4.4.5
> - xfs_fsr version 3.1.4
>
>
> Please let know if you'd like more info.
>
I tried to extract your vmlinuz to a vmlinux to disassemble and look at stack usage of functions, but that was painful and did not seem to work out in the end. :)
Can you do:
objdump -d vmlinux | scripts/checkstack.pl
and similar for xfs if it's a module:
objdump -d xfs.ko | scripts/checkstack.pl
and see how big each of the functions on the above backtrace is, in your kernel?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-28 23:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 22:58 kernel panic - stack-protector: kernel stack is corrupted in: f87aca93 Jeffrey Hundstad
2011-03-01 0:00 ` Eric Sandeen [this message]
2011-03-01 1:03 ` Jeffrey Hundstad
2011-03-01 1:32 ` Eric Sandeen
2011-03-01 2:57 ` Dave Chinner
2011-03-01 1:37 ` [PATCH] xfs: zero proper structure size for geometry calls Eric Sandeen
2011-03-01 2:59 ` Dave Chinner
2011-03-01 3:01 ` Eric Sandeen
2011-03-01 6:59 ` [PATCH V2] " Eric Sandeen
2011-03-01 12:55 ` Dan Rosenberg
2011-03-01 15:36 ` Jeffrey Hundstad
2011-03-01 15:49 ` Eric Sandeen
2011-03-01 17:50 ` [PATCH, V3 (sort of)] " Alex Elder
2011-03-01 18:18 ` Eric Sandeen
2011-03-01 21:40 ` Jeffrey Hundstad
2011-03-02 0:02 ` 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=4D6C372E.6030105@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jeffrey.hundstad@mnsu.edu \
--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