From: Jurjen Oskam <jurjen@stupendous.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] 2.6.6 tty_io.c hangup locking
Date: Fri, 28 May 2004 22:11:39 +0200 [thread overview]
Message-ID: <20040528201139.GA12281@quadpro.stupendous.org> (raw)
In-Reply-To: <1085769769.2106.23.camel@deimos.microgate.com>
On Fri, May 28, 2004 at 01:42:50PM -0500, Paul Fulghum wrote:
> Up to now, this did not cause any actual problems.
> In 2.6.X this causes a warning if any of the called functions
> (flush_buffer/write_wakeup) call spin_xxx_bh() functions.
It was not only a warning here, but the pptp client also didn't work again
until after rebooting. Every time the connection was retried (every 10
seconds or so) the message appeared. Perhaps this is a problem in the pptp
client, but after rebooting it worked.
As for the patch: applied to vanilla 2.6.5 (applied cleanly, offset -5
lines) and compiling now.
One problem though: I'm running 2.6 for about two weeks now (with a 24x7
pptp connection), and I encountered this problem just once. I've seen a
report that someone got this error when his connection was severed, so
I'll try to pull the phone cable a few times and see how it recovers, both
with and without your patch. I'll report back when I know more.
Thanks,
--
Jurjen Oskam
"Avoid putting a paging file on a fault-tolerant drive, such as a mirrored
volume or a RAID-5 volume. Paging files do not need fault-tolerance."-MS Q308417
next prev parent reply other threads:[~2004-05-28 20:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 17:45 Badness in local_bh_enable at kernel/softirq.c:122 Jurjen Oskam
2004-05-27 18:19 ` Jurjen Oskam
2004-05-27 20:41 ` Paul Fulghum
2004-05-28 18:42 ` [PATCH][RFC] 2.6.6 tty_io.c hangup locking Paul Fulghum
2004-05-28 20:11 ` Jurjen Oskam [this message]
2004-05-28 20:33 ` Paul Fulghum
2004-05-28 23:06 ` Andrew Morton
2004-05-29 17:45 ` Paul Fulghum
2004-06-01 20:51 ` [PATCH] 2.6.6 synclinkmp.c Paul Fulghum
2004-06-01 20:57 ` Russell King
2004-06-01 21:25 ` Paul Fulghum
2004-06-02 21:22 ` Russell King
2004-06-02 22:04 ` Paul Fulghum
2004-06-02 14:13 ` Paul Fulghum
2004-06-01 20:51 ` [PATCH] 2.6.6 synclink.c Paul Fulghum
2004-06-02 14:15 ` Paul Fulghum
2004-06-01 20:53 ` [PATCH] 2.6.6 synclink_cs.c Paul Fulghum
2004-06-01 21:00 ` Russell King
2004-06-01 23:04 ` Paul Fulghum
2004-06-13 9:05 ` [PATCH][RFC] 2.6.6 tty_io.c hangup locking Jurjen Oskam
2004-06-13 13:29 ` Paul Fulghum
2004-06-13 14:24 ` Jurjen Oskam
2004-06-13 14:39 ` Paul Fulghum
-- strict thread matches above, loose matches on Subject: below --
2004-06-13 15:05 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=20040528201139.GA12281@quadpro.stupendous.org \
--to=jurjen@stupendous.org \
--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