linux-kernel - [PATCH 0/2] fix sysenter for 32-on-64 processes

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>] [day] [month] [year] [list]

Message-ID: <4885209E.8050003@goop.org>
Date:	Mon, 21 Jul 2008 16:49:50 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Mark McLoughlin <markmc@...hat.com>,
	Eduardo Habkost <ehabkost@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] fix sysenter for 32-on-64 processes

Hi Ingo,

Here's a little two-part patch series which fixes 32-on-64 syscalls 
using sysenter.

The first is a difference in ordering in arch_setup(); the 64-bit code 
was calling early_init_cpu() way too late.  Moving it earlier, to the 
same place as the 32-bit code, works for me, but I wonder if it might 
cause problems with other configurations.  Certainly it makes logical 
sense that both architectures do the same cpu setup at the same place.

The other fix is an outright Xen-specific bug, which resulted in 
usermode registers being trashed as a result of an over-enthusiastic use 
of sysret.

Both patches are .27 material, but I expect the arch_setup() change 
needs to cooking before being comfortable with it.

Thanks,
    J
--
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/