linux-kernel - RBP save and restore on x86-64 system calls

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

Message-ID: <3B326087ABEA7940953BF629CAA40E17035BE455@azsmsx402>
Date:	Mon, 28 Aug 2006 10:37:31 -0700
From:	"Hanson, Jonathan M" <jonathan.m.hanson@...el.com>
To:	<linux-kernel@...r.kernel.org>
Subject: RBP save and restore on x86-64 system calls

	This may not be a kernel question per se but I was hoping someone on
this list might be able to shed some light into where RBP is saved to on an
x86-64 system when a non-tracing system call is made.
	An ioctl() triggers my kernel module and I need to have a way to
reliably retrieve what RBP was immediately before the system call. RBP is
not saved on the process' stack on kernel entry. The code in entry.S says
that it's up to the C code (which I'm taking to mean glibc) to deal with
these non-saved registers. I have a statically compiled application and I
can't see the glibc code doing anything to save or restore RBP in the
assembly. It has to be saved somewhere or these would be all kinds of
problems after control returned to the user application from the system
call.
	Please reply directly to me as well as the list as I'm not a current
subscriber. Thanks for your time.


Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (11348 bytes)