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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 11 Aug 2014 07:53:57 -0700
From:	"H. Peter Anvin" <>
To:	Jan Beulich <>,
	Denys Vlasenko <>,
	Denys Vlasenko <>
CC:	Andy Lutomirski <>,
	Kees Cook <>,
	Will Drewry <>,
	Frederic Weisbecker <>,
	X86 ML <>, Alexei Starovoitov <>,
	Oleg Nesterov <>,
	Linux Kernel Mailing List <>
Subject: Re: [PATCH 4/5] x86: entry_64.S: always allocate complete "struct

On 08/11/2014 07:17 AM, Jan Beulich wrote:
>> The existing comments explain what every byte means.
>> They are useful if CFI-literate reader wants to check correctness
>> of the encoding of this annotation.
>> There is no overall comment what this CFI annotation
>> *achieves*. In human language, what do we say
>> to DWARF decoder here?
> Short answer: DW_CFA_def_cfa_expression.
> Longer response: Just like I said before, what you're asking for is
> identical to ask for each other CFI annotation to get a comment
> associated to tell you what it's doing, which I don't think you
> really mean to ask for. (Our main problem here is that we can't
> specify expressions with the .cfi_* gas directives, and hence have
> to resort to .cfi_escape.)

No, in *human language*.  What does the DW_CFA_def_cfa_expression
actually aim to accomplish?  If you don't know the innards of the DWARF
spec, the whole thing might as well be Hungarian.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists