public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Paul Mackerras <paulus@samba.org>
Cc: akpm@osdl.org, torvalds@osdl.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, xxebxebx@gmail.com,
	Greg KH <gregkh@suse.de>
Subject: Re: [PATCH] Fix for the PPTP hangs that have been reported
Date: Mon, 12 Jun 2006 19:22:22 +0200	[thread overview]
Message-ID: <200606121922.23431.mb@bu3sch.de> (raw)
In-Reply-To: <17548.52858.22555.610055@cargo.ozlabs.ibm.com>

On Monday 12 June 2006 04:16, Paul Mackerras wrote:
> Signed-off-by: Paul Mackerras <paulus@samba.org>
> ---
> Linus & Andrew, I think this one is a 2.6.17 candidate.

What about 2.6.16-stable?
I just applied that patch to my server running 2.6.16.20.
Seems to be ok, but I did not stresstest it.

> It's a small 
> and harmless patch and it fixes a bug that has been annoying quite a
> few people, if the bugzilla reports are anything to go by.  I think it
> should solve bugzilla 6402 as well.
> 
> diff --git a/drivers/char/n_tty.c b/drivers/char/n_tty.c
> index ede365d..b9371d5 100644
> --- a/drivers/char/n_tty.c
> +++ b/drivers/char/n_tty.c
> @@ -1384,8 +1384,10 @@ do_it_again:
>  		 * longer than TTY_THRESHOLD_UNTHROTTLE in canonical mode,
>  		 * we won't get any more characters.
>  		 */
> -		if (n_tty_chars_in_buffer(tty) <= TTY_THRESHOLD_UNTHROTTLE)
> +		if (n_tty_chars_in_buffer(tty) <= TTY_THRESHOLD_UNTHROTTLE) {
> +			n_tty_set_room(tty);
>  			check_unthrottle(tty);
> +		}
>  
>  		if (b - buf >= minimum)
>  			break;

-- 
Greetings Michael.

  reply	other threads:[~2006-06-12 17:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12  2:16 [PATCH] Fix for the PPTP hangs that have been reported Paul Mackerras
2006-06-12 17:22 ` Michael Buesch [this message]
2006-06-12 21:38 ` Lee Revell

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=200606121922.23431.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=torvalds@osdl.org \
    --cc=xxebxebx@gmail.com \
    /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