All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "MRU.Ilya" <utdilya@mail.ru>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: pty.c  in linux 2.6.31-rc5+
Date: Thu, 4 Aug 2011 07:37:33 -0700	[thread overview]
Message-ID: <20110804143733.GC18468@kroah.com> (raw)
In-Reply-To: <4E3A4053.6020107@mail.ru>

On Thu, Aug 04, 2011 at 10:46:43AM +0400, MRU.Ilya wrote:
> 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.
> 
> 

> --- orig/pty.c	2011-07-13 07:29:43.000000000 +0400
> +++ work/pty.c	2011-08-03 20:59:01.000000000 +0400
> @@ -204,6 +204,7 @@
>  	clear_bit(TTY_OTHER_CLOSED, &tty->link->flags);
>  	set_bit(TTY_THROTTLED, &tty->flags);
>  	retval = 0;
> +	tty->low_latency = 1;

I really don't think this is correct.

Also, you forgot to read Documentation/SubmittingPatches for how to
properly format and send a patch and who to send it to...

thanks,

greg k-h

  reply	other threads:[~2011-08-04 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04  6:46 BUG: pty.c in linux 2.6.31-rc5+ MRU.Ilya
2011-08-04 14:37 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-04  6:43 MRU.Ilya
2011-08-04 14:36 ` Greg KH
2011-08-04 18:56 ` Alan Cox

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=20110804143733.GC18468@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=utdilya@mail.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.