linux-kernel - Re: [REGRESSION] 2.6.32.36 - Linux Xen DomU doesn't boot anymore

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTim9iAM=d-aWxKySJTsUjvOyVLD0=A@mail.gmail.com>
Date:	Thu, 14 Apr 2011 19:03:39 -0300
From:	"guilherme m. schroeder" <guilherme.m.schroeder@...il.com>
To:	Stratos Psomadakis <psomas@....ntua.gr>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION] 2.6.32.36 - Linux Xen DomU doesn't boot anymore

On Thu, Apr 14, 2011 at 5:52 PM, Stratos Psomadakis <psomas@....ntua.gr> wrote:
> Can you try 2.6.32.37-rc1?
> The patch you're referring to was committed I think along with another
> patch which caused some trouble in the -stable trees(I'm not surea bout
> that though :/).
> And in 2.6.32.37-rc1 it was reverted:
> [59/74] [PATCH] Revert "x86: Cleanup highmap after brk is concluded"
> Maybe it fixes your problem.
>
> --
> Stratos Psomadakis
> <psomas@....ntua.gr>

No problem with 2.6.32.37-rc1.
Do I need to bisect 2.6.32.37-rc1 against 2.6.32.36 to make sure it is
the patch that you mentioned?
And if we find it, there'll be a 2.6.32.36.1 release or we need to
wait for 2.6.32.37?
I'm asking this because some distros are already taking 2.6.32.36
(Debian 6.0 proposed kernel for example).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/