From: Andrew Morton <[email protected]>
Date: Sun, 11 Dec 2005 20:32:26 -0800
> So foo_mb() in preemptible code is potentially buggy.
>
> I guess we assume that a context switch accidentally did enough of the
> right types of barriers for things to work OK.
A trap ought to flush all memory operations.
There are some incredibly difficult memory error handling cases if the
cpu does not synchronize all pending memory operations when a trap
occurs.
Failing that, yes, to be absolutely safe we'd need to have some
explicit memory barrier in the context switch.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
