From: Nathan Scott <nathans@sgi.com>
To: Ali Akcaagac <aliakc@web.de>, Chris Wright <chrisw@osdl.org>, hch@lst.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel OOOPS in 2.6.11.6
Date: Tue, 29 Mar 2005 16:30:44 +1000 [thread overview]
Message-ID: <20050329063044.GB17541@frodo> (raw)
In-Reply-To: <20050328224430.GO28536@shell0.pdx.osdl.net>
On Mon, Mar 28, 2005 at 02:44:30PM -0800, Chris Wright wrote:
> * Ali Akcaagac (aliakc@web.de) wrote:
> > And happy easter to you all. Just got this while trying to delete some
> > files on my system.
> ...
> > : EIP is at linvfs_open+0x59/0xa0
> ...
> Nothing in the -stable series has changed either XFS or the core vfs
> path on during file open. Without a chance of reproducing or any more
> information, it'll be tough to make much progress here.
*nod*.
Your full .config would be useful too, Ali, thanks.
> with eax == 00000000. This corresponds to a vp->v_fops (or rather
> vp->v_bh.bh_first->bd_ops) deref. So, looks like the vnode has a
> NULL v_bh.bh_first (which looks like it's meant to be used to mean
> uninitialized). May check with XFS folks if they've seen this type
> of bug.
Its not currently known. Looks like a possible iget-related race;
does this one ring any bells, Christoph?
cheers.
--
Nathan
next prev parent reply other threads:[~2005-03-29 6:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 11:09 Kernel OOOPS in 2.6.11.6 Ali Akcaagac
2005-03-28 22:44 ` Chris Wright
2005-03-28 22:57 ` Coywolf Qi Hunt
2005-03-28 23:04 ` Chris Wright
2005-03-29 0:12 ` Coywolf Qi Hunt
2005-03-29 0:24 ` Chris Wright
2005-03-29 2:06 ` Chris Wedgwood
2005-03-29 2:27 ` Keith Owens
2005-03-29 3:12 ` Chris Wedgwood
2005-03-29 0:28 ` Ali Akcaagac
2005-03-29 6:30 ` Nathan Scott [this message]
2005-03-29 16:55 ` Christoph Hellwig
2005-03-29 16:59 ` Chris Wright
2005-03-29 17:01 ` Christoph Hellwig
2005-04-01 21:08 ` Ali Akcaagac
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=20050329063044.GB17541@frodo \
--to=nathans@sgi.com \
--cc=aliakc@web.de \
--cc=chrisw@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
/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