From: Chuck Ebbert <76306.1226@compuserve.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-stable <stable@kernel.org>
Subject: Re: Success: tty_io flush_to_ldisc() error message triggered
Date: Sat, 22 Jul 2006 12:07:00 -0400 [thread overview]
Message-ID: <200607221209_MC3-1-C5CA-50EB@compuserve.com> (raw)
In-Reply-To: <44C2307C.9060607@microgate.com>
On Sat, 22 Jul 2006 09:04:44 -0500, Paul Fulghum wrote:
> That confirms my thoughts on what went wrong:
> multiple copies of the queued work (flush_to_ldisc)
> running in parallel and corrupting the free buffer list.
>
> A cleaner fix for this is already
> in the 2.6.18 rc series.
The cleaner fix looks more intrusive, though.
Is this simpler change (what I'm running but without the warning
messages) the preferred fix for -stable?
From: Paul Fulghum <paulkf@microgate.com>
Serialize flush_to_ldisc() per-device. Fixes free list corruption
that causes lockup on SMP systems.
Signed-off-by: Paul Fulghum <paulkf@microgate.com>
Acked-by: Chuck Ebbert <76306.1226@compuserve.com>
--- 2.6.16.20-d4.orig/include/linux/tty.h
+++ 2.6.16.20-d4/include/linux/tty.h
@@ -266,6 +266,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))
--- 2.6.16.20-d4.orig/drivers/char/tty_io.c
+++ 2.6.16.20-d4/drivers/char/tty_io.c
@@ -2780,10 +2780,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;
}
@@ -2805,6 +2803,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);
}
--
Chuck
next reply other threads:[~2006-07-22 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 16:07 Chuck Ebbert [this message]
2006-07-22 16:41 ` Paul Fulghum
2006-07-25 18:41 ` [stable] " Greg KH
2006-07-25 19:12 ` Paul Fulghum
2006-07-26 7:16 ` Greg KH
[not found] ` <1153941029.6903.5.camel@amdx2.microgate.com>
2006-07-28 13:53 ` [PATCH]: tty buffering limit Alan Cox
2006-07-28 15:36 ` Paul Fulghum
-- strict thread matches above, loose matches on Subject: below --
2006-07-22 2:58 Success: tty_io flush_to_ldisc() error message triggered Chuck Ebbert
2006-07-22 14:02 ` Paul Fulghum
2006-07-22 14:04 ` 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=200607221209_MC3-1-C5CA-50EB@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=stable@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
Powered by JetHome