Hello,
On Fri, Aug 03, 2012 at 11:41:34PM +0200, Sasha Levin wrote:
> I forgot to comment on that one, sorry.
>
> If we put hash entries after struct hash_table we don't take the
> bits field size into account, or did I miss something?
So, if you do the following,
struct {
struct {
int i;
long ar[];
} B;
long __ar_storage[32];
} A;
It should always be safe to dereference A.B.ar[31]. I'm not sure
whether this is something guaranteed by C tho. Maybe compilers are
allowed to put members in reverse order but I think we already depend
on the above.
Thanks.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>