linux-kernel - Re: PATCH] firewire: add padding to some struct

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]

Message-ID: <48807527.9060806@s5r6.in-berlin.de>
Date:	Fri, 18 Jul 2008 12:49:11 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	JiSheng Zhang <jszhang3@...l.ustc.edu.cn>
CC:	linux-kernel@...r.kernel.org,
	linux1394-devel@...ts.sourceforge.net, krh@...hat.com
Subject: Re: PATCH] firewire: add padding to some struct

JiSheng Zhang wrote:
> struct fw_cdev_event_response and struct fw_cdev_event_iso_interrupt need padding.
> Otherwise, offset of the zero length array is not equal to the struct size. It may
> cause some strange problems under some platforms such as sparc32. This
> patch(against 2.6.26) should fix it.

The best solution to this problem would be to use

	offsetof(struct fw_cdev_event_XYZ, data)

instead of sizeof(struct fw_cdev_event_XYZ) in all the places where the
offset is required.

Your proposed solution to add padding...

> --- old/include/linux/firewire-cdev.h	2008-07-18 16:34:01.181794046 +0800
> +++ new/include/linux/firewire-cdev.h	2008-07-18 16:35:46.649294275 +0800
> @@ -92,6 +92,7 @@
>  	__u32 type;
>  	__u32 rcode;
>  	__u32 length;
> +	__u32 pad;
>  	__u32 data[0];
>  };
>  
> @@ -143,6 +144,7 @@
>  	__u32 type;
>  	__u32 cycle;
>  	__u32 header_length;
> +	__u32 pad;
>  	__u32 header[0];
>  };
>  

...can alas not be applied because it would break ABI compatibility.

Thanks for looking into it,
-- 
Stefan Richter
-=====-==--- -=== =--=-
http://arcgraph.de/sr/
--
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/