From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Xianghua Xiao <xiaoxianghua@gmail.com>
Cc: Maindoor <sanjeevfiles@yahoo.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] Fix DEBUG_PAGEALLOC on 603/e300
Date: Tue, 04 May 2010 15:13:26 +1000 [thread overview]
Message-ID: <1272950006.13814.19.camel@pasglop> (raw)
In-Reply-To: <g2pe6bf505b1005030719r3194c665i61d0c5906e1d1254@mail.gmail.com>
On Mon, 2010-05-03 at 09:19 -0500, Xianghua Xiao wrote:
> Ok here is the test result I did this morning, in short with/without
> Ben's patch it will oops if you write to a freed page.
Probably lucky enough that the free_pages() is pushing the stuff out of
the TLB. At least my patch prevents writing to a non-existing hash table
though, thus avoiding memory corruption.
Cheers,
Ben.
next prev parent reply other threads:[~2010-05-04 5:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 7:22 [PATCH] Fix DEBUG_PAGEALLOC on 603/e300 Benjamin Herrenschmidt
2010-04-28 19:15 ` Xianghua Xiao
2010-04-28 19:46 ` Kim Phillips
2010-04-28 22:29 ` Benjamin Herrenschmidt
2010-05-02 10:27 ` Maindoor
2010-05-03 14:19 ` Xianghua Xiao
2010-05-04 5:13 ` Benjamin Herrenschmidt [this message]
2010-05-06 8:23 ` Maindoor
2010-05-06 13:04 ` Maindoor
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=1272950006.13814.19.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sanjeevfiles@yahoo.com \
--cc=xiaoxianghua@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox