From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andreas Schwab <schwab@suse.de>, Andrew Morton <akpm@osdl.org>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Pty is losing bytes
Date: Tue, 15 Feb 2005 22:13:22 +0000 [thread overview]
Message-ID: <1108505601.4915.23.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0502151129210.5570@ppc970.osdl.org>
On Maw, 2005-02-15 at 19:44, Linus Torvalds wrote:
> However, then when I start looking at n_tty_receive_room() and
> n_tty_receive_buf(), my stomach gets a bit queasy. I have this horrid
> feeling that I had something to do with the mess, but I'm going to lash
You did.
Then Ted tided it up
Then Bill added hacks to "fix" up the locking
The real fix is shooting the flip buffers, at that point a lot of the
locking goes away (because the tty owns everything relevant). I just
don't have time to do major kernel hacking and finish the MBA thesis at
the same time.
Sorry yes I know how n_tty works, and no I'm not going to fix it
next prev parent reply other threads:[~2005-02-15 22:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 0:54 Pty is losing bytes Andreas Schwab
2005-02-15 19:08 ` Linus Torvalds
2005-02-15 19:44 ` Linus Torvalds
2005-02-15 22:13 ` Alan Cox [this message]
2005-02-15 19:58 ` Sergey Vlasov
2005-02-15 20:13 ` Sergey Vlasov
2005-02-15 20:06 ` Alan Curry
2005-02-15 20:30 ` Andreas Schwab
2005-02-15 20:56 ` Linus Torvalds
2005-02-15 21:54 ` Andreas Schwab
2005-02-16 3:12 ` Roman Zippel
2005-02-16 4:05 ` Linus Torvalds
2005-02-16 14:42 ` Theodore Ts'o
2005-02-16 16:06 ` Linus Torvalds
2005-02-17 4:44 ` Theodore Ts'o
2005-02-17 15:45 ` Linus Torvalds
2005-02-18 16:32 ` Theodore Ts'o
2005-02-16 19:49 ` Roman Zippel
2005-02-16 19:58 ` Linus Torvalds
2005-02-16 22:46 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-02-15 2:00 Alex Davis
2005-02-15 10:48 ` Andreas Schwab
2005-02-15 11:01 ` Jan De Luyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1108505601.4915.23.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox