Since new_disk is on the stack, is there something about 'conf'
that guarenetes it is not on the stack too? F.e. what if
&conf->last_used were one byte into 'new_disk' or something
like that.
Probably this is all illegal...
-- David S. Miller <davem@redhat.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/