linux-kernel - Re: vsyscall=emulate regression

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: <CALCETrUpXNkUSGh59+dy=+ocy2=J7G7=nXs4L1girsWFZVGC9g@mail.gmail.com>
Date:	Fri, 3 Feb 2012 07:30:55 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	Amit Shah <amit.shah@...hat.com>
Cc:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: vsyscall=emulate regression

On Fri, Feb 3, 2012 at 12:27 AM, Amit Shah <amit.shah@...hat.com> wrote:
> Hello,
>
> I'm booting some latest kernels on a Fedora 11 (released June 2009)
> guest.  After the recent change of default to vsyscall=emulate, the
> guest fails to boot (init segfaults).

Which kernel is the host running and which kernel is the guest
running?  And which kernel has the vsyscall=emulate parameter?  If
vsyscall=emulate is a problem on a pre-3.3 kernel, can you try
something containing commit 4fc3490114bb159bd4fff1b3c96f4320fe6fb08f?
(UML, for example, is known to have serious issues without that fix.)

Otherwise, can you tell me what hypervisor you're using and what init
version (i.e. the rpm) so I can try to reproduce it?  A pointer to an
actual image would work, too.  A copy of the oops would also be nice.

--Andy
--
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/