Re: [2.6.1-mm2] Badness in futex_wait at kernel/futex.c:509

[Rusty Russell]

In message <20040113223612.4fe709d9.akpm@xxxxxxxx> you write:
> Horacio de Oro <hgdeoro@xxxxxxxxx> wrote:
> >
> > Hi!
> > 
> > This happen every time I switch from X to console:
> > 
> > Badness in futex_wait at kernel/futex.c:509
> > Call Trace:
> >  [futex_wait+434/448] futex_wait+0x1b2/0x1c0
> >  [default_wake_function+0/32] default_wake_function+0x0/0x20
> >  [default_wake_function+0/32] default_wake_function+0x0/0x20
> >  [do_futex+112/128] do_futex+0x70/0x80
> >  [sys_futex+292/320] sys_futex+0x124/0x140
> >  [syscall_call+7/11] syscall_call+0x7/0xb
> > 
> 
> 	/* A spurious wakeup should never happen. */
> 	WARN_ON(!signal_pending(current));
> 
> (looks at Rusty)

You were the one who said spurious wakeups shouldn't happen 8)

This implies that the console code decided to do wake_up_process() on
us.  We returned -EINTR to userspace, but there was no signal, which
is odd.

Anyone have any ideas *why*?
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
-
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/