On Mon, 2007-03-12 at 10:56 -0700, Jean Tourrilhes wrote: > I did that in the e-mail to Jouni. The problem is that most > people are unfamiliar with decoding iwevents, so can't grasp the > explanation. > Basically, for iwpoint, we have an outer lenght and an inner > length. If they don't match, we have an alignement issue and just need > to pick the payload 8 bytes after the expected location. > For other events, they have a well known size. If the outer > lenght is not the expected size, but is expected+4, you just pick the > payload 4 bytes after the expected location. Ok. So the plan now is to put this document up somewhere maybe with some graphics or whatever, and then send this to distros so they know what happens when people hit this bug. Does your new version work without padding even on 64-bit arches? Then in a few years we can actually remove the padding completely in the kernel, right? johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
