linux-kernel - Re: [PATCH 4/5] x86: entry_64.S: always allocate complete "struct pt

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]

Message-Id: <53E8A98A020000780002B059@mail.emea.novell.com>
Date:	Mon, 11 Aug 2014 10:31:22 +0100
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"Andy Lutomirski" <luto@...capital.net>
Cc:	"Kees Cook" <keescook@...omium.org>,
	"Will Drewry" <wad@...omium.org>,
	"Frederic Weisbecker" <fweisbec@...il.com>,
	"Denys Vlasenko" <vda.linux@...glemail.com>,
	"X86 ML" <x86@...nel.org>, "Alexei Starovoitov" <ast@...mgrid.com>,
	"Denys Vlasenko" <dvlasenk@...hat.com>,
	"Oleg Nesterov" <oleg@...hat.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 4/5] x86: entry_64.S: always allocate complete
 "struct pt_regs"

>>> On 11.08.14 at 11:07, <luto@...capital.net> wrote:
> How does one test the entry CFI annotations?  The best that I know of
> is to single-step through using gdb attached to qemu and see whether
> backtraces seem to work.

Or have the kernel generate a backtrace from a suitable location and
check that the backtrace is correct (of course provided you have Dwarf
stack unwinding support in your kernel).

Jan

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