New struct sock_common breaks parisc 64 bit compiles with a misalignment
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 20030615.073503.112613460.davem@redhat.com.suse.lists.linux.kernel
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 20030615.082355.08334189.davem@redhat.com.suse.lists.linux.kernel
Quoted 10 lines · David S. Miller
From: James Bottomley <[email protected]>
Date: 15 Jun 2003 10:17:10 -0500It's not necessary and would, indeed, be detrimental to operation since we'd generate alignment traps on almost every encapsulated protocol (at several hundred instructions per trap). If we do this, our network performance will tank.
It doesn't happen for all the normal cases, but it does for things like IP in appletalk and stuff like that.
It can be remotely triggered in ordinary TCP. Just add an odd number of nops before a TCP timestamp to misalign it.
In short any linux parisc64 box on the net is very likely remotely panicable.
-Andi