linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: terry white <twhite@aniota.com>
Cc: linux-ppp@vger.kernel.org, linux-serial@vger.kernel.org,
	"Mats Kärrman" <Mats.Karrman@tritech.se>,
	"Greg KH" <gregkh@linuxfoundation.org>
Subject: Re: Suspecting kernel timing bug in ppp or tty drivers
Date: Wed, 12 Mar 2014 10:04:10 -0400	[thread overview]
Message-ID: <5320695A.2070503@hurleysoftware.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1403120452230.17831@yossarian>

On 03/12/2014 08:14 AM, terry white wrote:
>     my reading of this 'thread' suggests that "pppd" and/or "serial" have
> started "DEMANDING" bleeding edge kernel versions.  if that 'correct', for
> me anyway, it's going to prove problematic.  that aside, it doesn't seem
> like the most elegant solution, to problems it's meant to address ...

There have been _hundreds of changes_ to the tty core since 3.2, many
to specifically fix the type of error reported.

Very few of these changes are trivial; there are at least a dozen patchsets
with 10 or more patches. I doubt these will ever be backported to -stable;
the changes are just too extensive.

It makes sense to establish if these changes have indeed fixed the observed
error already or if more in-depth debugging is necessary to uncover the root
cause.

Regards,
Peter Hurley


  reply	other threads:[~2014-03-12 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 13:36 Suspecting kernel timing bug in ppp or tty drivers Mats Kärrman
2014-03-10 19:40 ` Greg KH
2014-03-11  9:41   ` Mats Kärrman
2014-03-11 18:50     ` Greg KH
2014-03-12  7:54       ` Mats Kärrman
2014-03-12 12:14       ` terry white
2014-03-12 14:04         ` Peter Hurley [this message]
2014-03-25  9:51       ` Mats Kärrman

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=5320695A.2070503@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=Mats.Karrman@tritech.se \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=twhite@aniota.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;
as well as URLs for NNTP newsgroup(s).