[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091014000145.3a611c94@lxorguk.ukuu.org.uk>
Date: Wed, 14 Oct 2009 00:01:45 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Paul Fulghum <paulkf@...rogate.com>,
Boyan <btanastasov@...oo.co.uk>,
" Frédéric L. W. Meunier" <fredlwm@...il.com>,
"Justin P. Mattock" <justinmattock@...il.com>,
Nix <nix@...eri.org.uk>, "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Ed Tomlinson <edt@....ca>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Subject: Re: [Bug #14388] keyboard under X with 2.6.31
> And no, I'm not sure my patch helps. I'd have expected
> 'tty_buffer_flush()' to be something very rare, for example. But I also
> didn't really check if we may do it some other way.
It is rare for most applications
> But I _am_ sure that it makes the code a whole lot more straightforward.
> Bits that say "we're busy flushing" suddenly actually act that way, and
> pointers that say "this is the head of the buffers" also act that wy.
The more I look the more I think a mutex is the right answer. It also
provides us with a "stop feeding me" lock for ldisc changes and tty close
down bits.
--
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