Thread (1 message) 1 message, 1 author, 2007-03-08

Re: wireless extensions vs. 64-bit architectures

From: Johannes Berg <hidden>
Date: 2007-03-08 16:51:54
Also in: linux-wireless

On Thu, 2007-03-08 at 15:39 +0100, Johannes Berg wrote:
Now, I don't know what gcc for ia64 does and I don't have a cross
compiler to check, but on powerpc it does this.
As expected, the same happens on x86_64 (thanks to Michael Wu for the
debug dump):

 <1><e13>: Abbrev Number: 17 (DW_TAG_structure_type)
     DW_AT_sibling     : <e4c>
     DW_AT_name        : (indirect string, offset: 0x33d): iw_event
     DW_AT_byte_size   : 24
     DW_AT_decl_file   : 100
     DW_AT_decl_line   : 1049
 <2><e20>: Abbrev Number: 18 (DW_TAG_member)
     DW_AT_name        : len
     DW_AT_decl_file   : 100
     DW_AT_decl_line   : 1050
     DW_AT_type        : <58b>
     DW_AT_data_member_location: 2 byte block: 23 0     (DW_OP_plus_uconst: 0)
 <2><e2f>: Abbrev Number: 18 (DW_TAG_member)
     DW_AT_name        : cmd
     DW_AT_decl_file   : 100
     DW_AT_decl_line   : 1051
     DW_AT_type        : <58b>
     DW_AT_data_member_location: 2 byte block: 23 2     (DW_OP_plus_uconst: 2)
 <2><e3e>: Abbrev Number: 18 (DW_TAG_member)
     DW_AT_name        : u
     DW_AT_decl_file   : 100
     DW_AT_decl_line   : 1052
     DW_AT_type        : <9bf>
     DW_AT_data_member_location: 2 byte block: 23 8     (DW_OP_plus_uconst: 8)

Hence, on those machines 32-bit userspace is also broken and we have the
information leak too.

johannes

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help