Anton Ivanov 0565103d1a 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>		2014-04-20 23:57:21 +02:00
..
drivers
skas	um: siginfo cleanup	2013-07-19 11:31:36 +02:00
aio.c	um: Cleanup SIGTERM handling	2013-09-07 10:56:58 +02:00
elf_aux.c
execvp.c
file.c	um: Memory corruption on startup	2014-04-20 23:57:21 +02:00
helper.c
internal.h
irq.c
main.c	um: Missing pipe handling	2014-04-20 23:13:30 +02:00
Makefile
mem.c	uml: Simplify tempdir logic.	2014-04-20 23:10:44 +02:00
process.c	um: Cleanup SIGTERM handling	2013-09-07 10:56:58 +02:00
registers.c
sigio.c	um: Cleanup SIGTERM handling	2013-09-07 10:56:58 +02:00
signal.c	um: Make stack trace reliable against kernel mode faults	2013-11-17 11:27:30 +01:00
start_up.c
time.c
tty.c
umid.c
user_syms.c
util.c	um: Cleanup SIGTERM handling	2013-09-07 10:56:58 +02:00