public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: Diego Calleja <diegocg@gmail.com>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: pppd oopses current linu's git tree on disconnect
Date: Thu, 19 Jan 2006 16:39:51 -0600	[thread overview]
Message-ID: <43D01537.40705@microgate.com> (raw)
In-Reply-To: <20060119230746.ea78fcf4.diegocg@gmail.com>

Diego Calleja wrote:
>>Does this occur frequently?
> 
> Not at all - I've tried to trigger it tons of times and didn't happen again,
> I even put a pon/poff in a loop but nothing happened; so I can't confirm if
> your patch does fix it, but I'm running the patch and nothing bad seems to
> happen.

The only way I can see for the oops you reported to occur
is for the pending or free list of tty buffers to get corrupted.
This causes the oops when trying to free all the buffers.

The buffer handling code looks correct, but there is a locking
(or lack of) issue that could mess up the lists on an SMP machine.
The serial ISR does not hold the tty->read_lock when pushing data
which is used to synchronize access to the tty buffer list.
The test patch adds this lock to the function used
(by the standard serial driver) to push the data .

The chances of this happening increase with the speed and
continued use of the serial port. Your original report showed
a lengthy PPP session. So bringing the link down and up without
significant data transfer will probably not trigger this.

Thanks,
Paul

--
Paul Fulghum
Microgate Systems, Ltd


  reply	other threads:[~2006-01-19 22:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19  0:06 pppd oopses current linu's git tree on disconnect Diego Calleja
2006-01-19 17:33 ` Paul Fulghum
2006-01-19 22:07   ` Diego Calleja
2006-01-19 22:39     ` Paul Fulghum [this message]
2006-01-23  2:42       ` Diego Calleja
2006-01-24  3:48         ` Diego Calleja
2006-01-24 22:06           ` Paul Fulghum
2006-01-24 23:25             ` Alan Cox
2006-01-24 23:44               ` Paul Fulghum
2006-01-25  0:22                 ` Alan Cox
2006-01-25 21:00                   ` Paul Fulghum

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=43D01537.40705@microgate.com \
    --to=paulkf@microgate.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=diegocg@gmail.com \
    --cc=linux-kernel@vger.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