Re: [PATCH 2/6] vt: push down the tty lock so we can see what is left to tackle

From: Arnd Bergmann
Date: Thu Mar 01 2012 - 16:51:34 EST


On Thursday 01 March 2012, Alan Cox wrote:
> @@ -1407,6 +1425,7 @@ int vt_move_to_console(unsigned int vt, int alloc)
> return -EIO;
> }
> console_unlock();
> + /* Review: I don't see why we need tty_lock here FIXME */
> tty_lock();
> if (vt_waitactive(vt + 1)) {
> pr_debug("Suspend: Can't switch VCs.");

I'm pretty sure I only added this in be1bc288 "tty: introduce
wait_event_interruptible_tty" so I could release the mutex again in
vt_event_wait.

All other callers of that function hold it, so it needs to be released
in vt_event_wait and that can only be done if it's known to be held first.

Arnd
--
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/