[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4F38DA79.2040803@suse.cz>
Date: Mon, 13 Feb 2012 10:40:09 +0100
From: Jiri Slaby <jslaby@...e.cz>
To: Al Viro <viro@...IV.linux.org.uk>
CC: Jiri Slaby <jirislaby@...il.com>,
Richard Weinberger <richard@....at>,
linux-kernel@...r.kernel.org,
user-mode-linux-devel@...ts.sourceforge.net,
akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
gregkh@...uxfoundation.org
Subject: Re: your mail
On 02/12/2012 08:06 PM, Al Viro wrote:
> Yecchhh... If I'm reading (and grepping) it right, there are only two
> non-default instance of tty_operations ->shutdown() - pty and vt ones.
> Lovely... And while we are at it, vt instance is definitely not safe
> from interrupts - calls console_lock(). Not that it was relevant in
> this case...
Thanks for looking into that. I was too lazy to do that on Sunday.
You're right that it may cause problems. Fortunately vt doesn't refcount
ttys. Hence con_shutdown can be called only from release_tty (close
path) in the user context.
Adding to my TODO list, unless somebody beats me to fix it.
thanks,
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists