All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: oopses in xfs_attr_shortform_* on kerneloops.org
Date: Fri, 02 Jan 2009 22:09:32 -0600	[thread overview]
Message-ID: <495EE4FC.9080808@sandeen.net> (raw)
In-Reply-To: <20090102175911.GA29506@infradead.org>

Christoph Hellwig wrote:
> On Thu, Jan 01, 2009 at 10:01:36PM -0600, Eric Sandeen wrote:
>> 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.
> 
> Yeah, I've been looking into and the disassemly looks like we have
> a NULL attribut fork pointer for some reason.  I did some poking
> around in the code and couldn't a cause for it.  So if anyone of
> the kerneloops submitters actually is on the list and can reproduce
> it that would be extremly helpful.

This *might* be a clue:

http://article.gmane.org/gmane.comp.file-systems.xfs.general/22156

one of those oopses, and associated xfs_repair output for the fs in
question... doesn't make anything clearer to me, though, offhand.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2009-01-03  4:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02  4:01 oopses in xfs_attr_shortform_* on kerneloops.org Eric Sandeen
2009-01-02 17:59 ` Christoph Hellwig
2009-01-03  4:09   ` Eric Sandeen [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=495EE4FC.9080808@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.