From: "Hua Zhong" <hzhong@gmail.com>
To: "'Linus Torvalds'" <torvalds@linux-foundation.org>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
"'Andrew Morton'" <akpm@linux-foundation.org>
Subject: RE: page corruption bug in recent kernel (2.6.29)?
Date: Thu, 9 Apr 2009 13:50:52 -0700 [thread overview]
Message-ID: <013701c9b954$dfd54fe0$9f7fefa0$@com> (raw)
In-Reply-To: <alpine.LFD.2.00.0904091326480.4583@localhost.localdomain>
> As you say that you can trigger this fairly easily, one thing that you
> could try is to bisect it down the which kernel release it starts
> happening with. And even if it's not a kernel bug, doint that may give
> hints about perhaps what kind of things trigger the behavior, and might
> help you figure out where the bug is even if it's somewhere else.
Thanks, I agree it's not necessarily kernel related. I'm in the process
of bisecting it. Will keep you posted.
Hua
prev parent reply other threads:[~2009-04-09 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 20:10 page corruption bug in recent kernel (2.6.29)? Hua Zhong
2009-04-09 20:42 ` Linus Torvalds
2009-04-09 20:50 ` Hua Zhong [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='013701c9b954$dfd54fe0$9f7fefa0$@com' \
--to=hzhong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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