linux-kernel - Re: [PATCH] EFI x86: pass firmware call parameters on the stack

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]

Date:	Tue, 30 Jan 2007 11:10:58 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Frédéric Riss <frederic.riss@...il.com>,
	Matt Domsch <Matt_Domsch@...l.com>
Cc:	linux-kernel@...r.kernel.org, artiom.myaskouvskey@...el.com,
	bjorn.helgaas@...com,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] EFI x86: pass firmware call parameters on the stack

On Tue, 30 Jan 2007 20:01:18 +0100
Frédéric Riss <frederic.riss@...il.com> wrote:

> 
> When calling into an EFI firmware, the parameters need to be passed on
> the stack. The recent change to use -mregparm=3 breaks x86 EFI support.
> This patch is needed to allow the new Intel-based Macs to suspend to ram
> when run in EFI mode (efi.get_time is called during the suspend phase).
> 
> Signed-off-by: Frederic Riss <frederic.riss@...il.com>
> 
> ---
> 
> [As I couldn't find an official maintainer for the linux/efi.h file and
> the file header is quite old, I'm Cc:ing the last 2 commiters.]

Matt normally looks after EFI.

> This patch fixes the issue for x86, but the file is also used by IA64. I
> would have used asmlinkage to force arguments on the stack, but it has a
> special meaning on IA64, thus I used a raw regparm(0) GCC attribute.
> This attribute is documented only for x86, I hope it has no side effect
> on other archs.

hm, this sounds like a fairly serious problem.  Has this been runtime
tested on ia64 and x86_64>


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