linux-kernel - Re: sysenter cause a segmentation fault.

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

Message-ID: <p733b427dom.fsf@bingen.suse.de>
Date:	18 Mar 2007 16:51:21 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	"Ying Chu" <xjtuychu@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: sysenter cause a segmentation fault.

"Ying Chu" <xjtuychu@...il.com> writes:

> A simple code running on PIII 800,kernel 2.6.20 with SEP enabled
> causes  a  segmentation fault.

SYSENTER has a hardcoded return address, that is why you cannot be used
anywhere but in the vsyscall trampoline.  In addition it doesn't work
on x86-64 for 32bit processes for AMD. The only system call method
supported without the vDSO is int 0x80. Better you just use the vDSO.

> More, when i enabled Kdb and set "bp sysenter_entry",it went with a
> catastrophic error errupted.

The stack and some other kernel state are not set up yet at this point.

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