From: "MRU.Ilya" <utdilya@mail.ru>
To: stable@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: BUG: pty.c in linux 2.6.31-rc5+
Date: Thu, 04 Aug 2011 10:43:19 +0400 [thread overview]
Message-ID: <4E3A3F87.3050204@mail.ru> (raw)
Synchronic's line disciplines(ppp_synctty, hdlc) can't work with pseudo
terminals.
If frames send very fast from one side(master/slave) to other one,
frames merge in one (merge point "flip buffer") and the other side can
read only one big frame.
But sync line discipline need one frame in one read.
For push one frame to ldisc I propose small patch, but this regression for
commit e043e42bdb66885b3ac10d27a01ccb9972e2b0a3.
I don't find any mutexes and other things forbidden in not user context,
in function flush_to_ldisc() , and I think this patch
is true and this function can called from any context. But I not sure.
Relative commit 86d23a057e718f73adc15e463c643d6e014a19cd.
next reply other threads:[~2011-08-04 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 6:43 MRU.Ilya [this message]
2011-08-04 14:36 ` BUG: pty.c in linux 2.6.31-rc5+ Greg KH
2011-08-04 18:56 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2011-08-04 6:46 MRU.Ilya
2011-08-04 14:37 ` Greg KH
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=4E3A3F87.3050204@mail.ru \
--to=utdilya@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
/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