From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: oopses in xfs_attr_shortform_* on kerneloops.org
Date: Thu, 01 Jan 2009 22:01:36 -0600 [thread overview]
Message-ID: <495D91A0.4050304@sandeen.net> (raw)
I noticed this on kerneloops.org and pinged Christoph about it but I'll
go ahead & point it out here & file a bug so it doesn't get lost:
http://www.kerneloops.org/search.php?search=xfs_attr_shortform&btnG=Function+Search
would seem to indicate a problem, though not a (recent) regression anyway.
Many traces like:
RIP: 0010:[<ffffffff8802e346>] [<ffffffff8802e346>]
:xfs:xfs_attr_shortform_getvalue+0x27/0xf3
...
Call Trace:
[<ffffffff8802ce07>] :xfs:xfs_attr_fetch+0xba/0x114
[<ffffffff810cc227>] ? inotify_d_instantiate+0x1a/0x42
[<ffffffff8802cf12>] :xfs:xfs_attr_get+0xb1/0xd1
[<ffffffff8802cf50>] :xfs:attr_generic_get+0x1e/0x2e
[<ffffffff880713fb>] :xfs:xfs_vn_getxattr+0x86/0x95
[<ffffffff810be6ff>] vfs_getxattr+0xa1/0xb4
[<ffffffff810be7ae>] getxattr+0x9c/0xfb
[<ffffffff810b9f8a>] ? mntput_no_expire+0x20/0x85
[<ffffffff810ab1c5>] ? path_put+0x2c/0x30
[<ffffffff810adc45>] ? path_walk+0xb6/0xc3
[<ffffffff810adfee>] ? do_path_lookup+0x1d6/0x231
[<ffffffff810acb45>] ? putname+0x30/0x39
[<ffffffff810aea41>] ? __user_walk_fd+0x4c/0x5c
[<ffffffff810be8e2>] sys_lgetxattr+0x53/0x73
[<ffffffff810a7343>] ? sys_newlstat+0x31/0x3c
[<ffffffff8100bedb>] system_call_after_swapgs+0x7b/0x80
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-01-02 4:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 4:01 Eric Sandeen [this message]
2009-01-02 17:59 ` oopses in xfs_attr_shortform_* on kerneloops.org Christoph Hellwig
2009-01-03 4:09 ` Eric Sandeen
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=495D91A0.4050304@sandeen.net \
--to=sandeen@sandeen.net \
--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