From: Paul Fulghum <paulkf@microgate.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16.18 kernel freezes while pppd is exiting
Date: Mon, 12 Jun 2006 10:07:10 -0500 [thread overview]
Message-ID: <1150124830.3703.6.camel@amdx2.microgate.com> (raw)
In-Reply-To: <200606081909_MC3-1-C1F0-8B6B@compuserve.com>
Chuck:
Here is a patch to serialize flush_to_ldisc
with per device granularity. It should fix the
corruption of the free list that is the probably
cause of the freeze you are seeing. Test it to
see if there are any ill effects (it works fine here
on an AMD x2 SMP kernel). I realize that
the problem happens infrequently, so you won't
be able to tell quickly if it fixed the freeze.
This is a necessary change regardless, but I'm
confident it is the cause of your problem.
Just keep using it and keep me posted on the results.
Thanks,
Paul
--- a/include/linux/tty.h 2006-06-09 09:33:16.000000000 -0500
+++ b/include/linux/tty.h 2006-06-12 09:22:10.000000000 -0500
@@ -267,6 +267,7 @@ struct tty_struct {
#define TTY_PTY_LOCK 16 /* pty private */
#define TTY_NO_WRITE_SPLIT 17 /* Preserve write boundaries to driver */
#define TTY_HUPPED 18 /* Post driver->hangup() */
+#define TTY_FLUSHING 19 /* Flushing tty buffers to line discipline */
#define TTY_WRITE_FLUSH(tty) tty_write_flush((tty))
--- a/drivers/char/tty_io.c 2006-06-12 09:27:35.000000000 -0500
+++ b/drivers/char/tty_io.c 2006-06-12 09:31:41.000000000 -0500
@@ -2785,10 +2785,8 @@ static void flush_to_ldisc(void *private
if (disc == NULL) /* !TTY_LDISC */
return;
- if (test_bit(TTY_DONT_FLIP, &tty->flags)) {
- /*
- * Do it after the next timer tick:
- */
+ if (test_bit(TTY_DONT_FLIP, &tty->flags) ||
+ test_and_set_bit(TTY_FLUSHING, &tty->flags)) {
schedule_delayed_work(&tty->buf.work, 1);
goto out;
}
@@ -2810,6 +2808,7 @@ static void flush_to_ldisc(void *private
tty_buffer_free(tty, tbuf);
}
spin_unlock_irqrestore(&tty->buf.lock, flags);
+ clear_bit(TTY_FLUSHING, &tty->flags);
out:
tty_ldisc_deref(disc);
}
next prev parent reply other threads:[~2006-06-12 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 23:07 2.6.16.18 kernel freezes while pppd is exiting Chuck Ebbert
2006-06-09 13:35 ` Paul Fulghum
2006-06-12 15:07 ` Paul Fulghum [this message]
2006-06-12 15:53 ` Alan Cox
2006-06-12 16:11 ` Paul Fulghum
2006-06-12 16:36 ` Alan Cox
2006-06-12 16:25 ` Paul Fulghum
-- strict thread matches above, loose matches on Subject: below --
2006-06-12 16:36 Chuck Ebbert
2006-06-12 18:06 ` Paul Fulghum
2006-06-12 18:11 ` Paul Fulghum
2006-06-08 18:09 Chuck Ebbert
2006-06-08 20:08 ` Paul Fulghum
2006-06-08 21:17 ` 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=1150124830.3703.6.camel@amdx2.microgate.com \
--to=paulkf@microgate.com \
--cc=76306.1226@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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