From: Ali Akcaagac <aliakc@web.de>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel OOOPS in 2.6.11.6
Date: Tue, 29 Mar 2005 02:28:56 +0200 [thread overview]
Message-ID: <1112056136.1849.9.camel@localhost> (raw)
In-Reply-To: <2cd57c9005032816126557d064@mail.gmail.com>
On Tue, 2005-03-29 at 08:12 +0800, Coywolf Qi Hunt wrote:
> > > > 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.
> > >
> > > I think it is f = kmem_cache_alloc(filp_cachep, GFP_KERNEL); returns an
> > > invalid pointer, then in memset(f, 0, sizeof(*f)); fault happens at address f.
> > > eax == 0 is to clear the memory in memset().
> >
> > The trace indicates it's in linvfs_open
> > (EIP: 0060:[linvfs_open+89/160])
> > and the insturction dump at the end supports that.
>
> How to explain:
> Call Trace: [get_empty_filp+89/208] get_empty_filp+0x59/0xd0 ?
I like to let you know that this was all I got as dump. Was simply
trying to copy some stuff from A to B on my harddisk using MC on a XFS
partition using 2.6.11.6.
Though I also detected another really strange thing together with this
issue. On a valid XFS partition (no errors or something) I tried to
delete about 160 CVS checked out modules (GNOME) and *buff* stuff
couldn't be deleted anymore but I wasn't aware of this at that moment.
Seconds later I was trying to copy stuff from A to B as described above
and this gave me that hit. Luckely the hit caused let me continue using
the System. I then tried to delete the stuff again and noticed that it
hadn't deleted the CVS checkout in A) properly and that I copied the
undeleted stuff to B) as well. I then inserted my own created rescue CD,
mounted the partition again, and voila was able to delete the stuff
xfs_repair check on it gave no errors or something.
Maybe this helps isolating the issue.
next prev parent reply other threads:[~2005-03-29 0:28 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 [this message]
2005-03-29 6:30 ` Nathan Scott
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=1112056136.1849.9.camel@localhost \
--to=aliakc@web.de \
--cc=chrisw@osdl.org \
--cc=coywolf@gmail.com \
--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