Re: x86: Cleanup highmap after brk is concluded

[Yuri Arabadji]

Hi.

I strongly disagree with this commit. Some freak back-ported it into
2.3.32 and since then fear and suffering was brought to many innocent
people. It took me straight 3 hours of bisecting & testing to find out
why latest "stable" "longterm" 2.6.32 kernel (used as Xen PVops) won't
even boot on latest CentOS' standard dom0.

Something's wrong up there in the heavens. Can we get a working kernel
on kernel.org, please, and more testing/reviewing in the future?

Thanks.

On Mar 19, 10:40 pm, tip-bot for Yinghai Lu <ying...@xxxxxxxxxx> wrote:
> Commit-ID:  e5f15b45ddf3afa2bbbb10c7ea34fb32b6de0a0e
> Gitweb:    http://git.kernel.org/tip/e5f15b45ddf3afa2bbbb10c7ea34fb32b6de0a0e
> Author:     Yinghai Lu <ying...@xxxxxxxxxx>
> AuthorDate: Fri, 18 Feb 2011 11:30:30 +0000
> Committer:  H. Peter Anvin <h...@xxxxxxxxx>
> CommitDate: Sat, 19 Mar 2011 11:58:19 -0700
>
> x86: Cleanup highmap after brk is concluded
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/