From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [Bug #14388] keyboard under X with 2.6.31 Date: Tue, 13 Oct 2009 15:54:45 -0700 (PDT) Message-ID: References: <56acieJJ2fF.A.nEB.Hzl0KB@chimera> <87ljjgfcbu.fsf@spindle.srvr.nix> <4AD3F769.5080405@gmail.com> <4AD437F9.9020708@yahoo.co.uk> <4AD4DE4C.4010402@yahoo.co.uk> <20091013223212.3260a7eb@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Return-path: In-Reply-To: <20091013223212.3260a7eb@lxorguk.ukuu.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: TEXT/PLAIN; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alan Cox Cc: Boyan , =?ISO-8859-15?Q?Fr=E9d=E9ric_L=2E_W=2E_Meunier?= , "Justin P. Mattock" , Nix , Paul Fulghum , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Dmitry Torokhov , Ed Tomlinson , OGAWA Hirofumi On Tue, 13 Oct 2009, Alan Cox wrote: > > I can't help feeling a mutex might be simpler. It would also then fix > tiocsti() which is most definitely broken right now and documented as > racing. Hmm. Those tty's have too many different locks already. But maybe we could just have one generic mutex, and use it for termios and IO locking. It makes perfect sense to serialize the ->receive_buf() code with any termios changes, since termios is what affects _how_ that ->receive_buf() function works. I do wonder why tiocsti() doesn't just use the tty buffering layer, though? Maybe that harks back to the whole "pty's did things differently" thing? Why does it go directly to ->receive_buf() in the first place? And let's see if my patch even makes a difference. Maybe the breakage is somewhere else. The "oh, now we call flush_ldisc() from two different contexts" thing seems to be a promising lead, but ... Linus