linux-kernel - Re: [PATCH, resend] x86-64: fix CFI data for interrupt frames

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]

Date:	Wed, 28 Sep 2011 18:59:18 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jan Beulich <JBeulich@...e.com>
Cc:	tglx@...utronix.de, hpa@...or.com,
	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH, resend] x86-64: fix CFI data for interrupt frames


* Jan Beulich <JBeulich@...e.com> wrote:

> The patch titled "x86: Don't use frame pointer to save old stack on irq
> entry" did not properly adjust CFI directives, so this patch is a
> follow-up to that one.
> 
> With the old stack pointer no longer stored in a callee-saved register
> (plus some offset), we now have to use a CFA expression to describe the
> memory location where it is being found. This requires the use of
> .cfi_escape (allowing arbitrary byte streams to be emitted into
> .eh_frame), as there is no .cfi_def_cfa_expression (which also cannot
> reasonably be expected, as it would require a full expression parser).
> 
> Signed-off-by: Jan Beulich <jbeulich@...e.com>
> Cc: Frederic Weisbecker <fweisbec@...il.com>
> 
> ---
>  arch/x86/include/asm/dwarf2.h |    2 ++
>  arch/x86/kernel/entry_64.S    |   14 +++++++++-----
>  2 files changed, 11 insertions(+), 5 deletions(-)

Applied all 3 patches you sent, thanks Jan! (the tip-bot notification 
depends on korg being fully restored.)

Thanks,

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