From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-1.2689.fc6PAE: oops in ext3_clear_inode+0x52/0x8b
Date: Thu, 28 Sep 2006 14:26:33 -0700 [thread overview]
Message-ID: <451C3E09.6000400@goop.org> (raw)
In-Reply-To: <20060928142313.8848cec9.akpm@osdl.org>
Andrew Morton wrote:
> 756e6547 -> uneG. Matches "GenuineIntel".
>
> That'll get written into a temporary page by the /proc/cpuinfo handler, so
> it might just be a use-uninitialised.
>
I was compiling a kernel at the time, so it could have come from the
kernel source.
> It's relatively common for that big inode LRU walk to wander off in the
> wrong direction and to start operating on random memory.
>
> IOW: don't know. Something scribbled on memory somewhere.
>
Yep, that was as far as I got...
J
next prev parent reply other threads:[~2006-09-28 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 20:42 2.6.18-1.2689.fc6PAE: oops in ext3_clear_inode+0x52/0x8b Jeremy Fitzhardinge
2006-09-28 20:48 ` James Morris
2006-09-28 21:00 ` Jeremy Fitzhardinge
2006-09-28 21:23 ` Andrew Morton
2006-09-28 21:26 ` Jeremy Fitzhardinge [this message]
2006-10-03 5:32 ` Eric Sandeen
2006-10-03 5:42 ` Adrian Bunk
2006-10-03 14:06 ` Eric Sandeen
2006-10-03 16:23 ` Adrian Bunk
2006-10-03 16:27 ` 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=451C3E09.6000400@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--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