Hi
01.11.2013, 23:30, "Andrew Morton" <[email protected]>:
> set_bit() operates on longs. So if we do
>
> struct foo {
> u32 a;
> u32 b;
> } f;
>
> ...
> set_bit(0, (long *)&f.a);
> ...
>
> then we'll scribble on f.b on a big-endian 64-bit machine.
Argh, why would we just don't do that? Its in-memory field, it can be anything,
I wouldn't be surprised if it even can be non-atomic because of proper locks
already
being held
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
