uml: DEBUG_SHIRQ fixes
authorEduard-Gabriel Munteanu <maxdamage@aladin.ro>
Mon, 16 Jul 2007 06:38:51 +0000 (23:38 -0700)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Mon, 16 Jul 2007 16:05:38 +0000 (09:05 -0700)
commit89df6bfc04059716de2eb2fe529f05b3e124fafd
tree5f28a79bc65549f48e153f18b1692d9cf462c628
parente18eecb8b35703a5eea73ee2b45324262029e62c
uml: DEBUG_SHIRQ fixes

DEBUG_SHIRQ generates spurious interrupts, triggering handlers such as
mconsole_interrupt() or line_interrupt().  They expect data to be available to
be read from their sockets/pipes, but in the case of spurious interrupts, the
host didn't actually send anything, so UML hangs in read() and friends.
Setting those fd's as O_NONBLOCK makes DEBUG_SHIRQ-enabled UML kernels boot
and run correctly.

Signed-off-by: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
Signed-off-by: Jeff Dike <jdike@linux.intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
arch/um/drivers/chan_user.c
arch/um/drivers/mconsole_user.c
arch/um/drivers/ubd_user.c
arch/um/drivers/xterm.c