Re: [PATCH] fix console change race exposed by CFS
From: Jan Luebbe
Date: Sun Sep 30 2007 - 04:30:23 EST
On Sun, 2007-09-30 at 09:20 +-0200, Ingo Molnar wrote:
+AD4 +ACo Jan Luebbe +ADw-jluebbe+AEA-lasnet.de+AD4 wrote:
+AD4 +AD4 From: Jan L+APw-bbe +ADw-jluebbe+AEA-lasnet.de+AD4
+AD4 +AD4 The new behaviour of CFS exposes a race which occurs if a switch is
+AD4 +AD4 requested when vt+AF8-mode.mode is VT+AF8-PROCESS.
+AD4 +AD4 The process with vc-+AD4-vt+AF8-pid is signaled before vc-+AD4-vt+AF8-newvt is set. This
+AD4 +AD4 causes the switch to fail when triggered by the monitoing process
+AD4 +AD4 because the target is still -1.
+AD4 +AD4 Signed-off-by: Jan L+APw-bbe +ADw-jluebbe+AEA-lasnet.de+AD4
+AD4 nifty+ACE I'm wondering what the symptoms of this bug were - how did you
+AD4 notice it? Also, i'm wondering how you managed to debug this - looks
+AD4 quite hard to trigger this race, right?
+AD4 Acked-by: Ingo Molnar +ADw-mingo+AEA-elte.hu+AD4
I'm currenly porting the OpenMoko patchset to 2.6.23-rc8. We are using
psplash and kdrive. When booting, I got an error from psplash about
being unable to switch consoles. Strangely, it was possible to start
kdrive manually. So i set up qemu for kernel debugging, set some
interesting breakpoints and then saw that it was scheduling away
directly after the kill+AF8-pid. Then it was quite obvious.
It was triggering every time, on the device and in qemu identically.
Most people testing the RCs probably don't run psplash (or any other
program which sets vt+AF8-mode.mode to VT+AF8-PROCESS), so it wasn't noticed
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/