| commit | 0565103d1adbd765ca45248d04c327c076dd1571 | [log] [tgz] |
|---|---|---|
| author | Anton Ivanov <antivano@cisco.com> | Fri Mar 07 18:37:47 2014 +0000 |
| committer | Richard Weinberger <richard@nod.at> | Sun Apr 20 23:57:21 2014 +0200 |
| tree | bc72dc69499b068766284276bee91884afb1218b | |
| parent | 9fcb663be42e4727c1beabc7c80e2d839199e6b1 [diff] |
um: Memory corruption on startup The reverse case of this race (you must msync before read) is well known. This is the not so common one. It can be triggered only on systems which do a lot of task switching and only at UML startup. If you are starting 200+ UMLs ~ 0.5% will always die without this fix. Signed-off-by: Anton Ivanov <antivano@cisco.com> [rw: minor whitespace fixes] Signed-off-by: Richard Weinberger <richard@nod.at>