Re: [PATCH] vt: fix a potential race in the VT_WAITACTIVE handler

2007-03-19 Thread Andrew Morton
On Thu, 15 Mar 2007 15:10:23 +0100 Michal Januszewski <[EMAIL PROTECTED]> wrote: > On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0 > if fg_console has already been updated in redraw_screen(), but the > console switch itself hasn't been completed. Fix this by checking >

Re: [PATCH] vt: fix a potential race in the VT_WAITACTIVE handler

2007-03-19 Thread Andrew Morton
On Thu, 15 Mar 2007 15:10:23 +0100 Michal Januszewski [EMAIL PROTECTED] wrote: On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0 if fg_console has already been updated in redraw_screen(), but the console switch itself hasn't been completed. Fix this by checking fg_console

[PATCH] vt: fix a potential race in the VT_WAITACTIVE handler

2007-03-15 Thread Michal Januszewski
On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0 if fg_console has already been updated in redraw_screen(), but the console switch itself hasn't been completed. Fix this by checking fg_console in vt_waitactive() with the console sem held. Signed-off-by: Michal Januszewski

[PATCH] vt: fix a potential race in the VT_WAITACTIVE handler

2007-03-15 Thread Michal Januszewski
On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0 if fg_console has already been updated in redraw_screen(), but the console switch itself hasn't been completed. Fix this by checking fg_console in vt_waitactive() with the console sem held. Signed-off-by: Michal Januszewski