From: Glen Turner <glen.turner@aarnet.edu.au>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 8250 serial console fixes -- issue
Date: Sat, 04 Feb 2006 00:57:28 +1030 [thread overview]
Message-ID: <43E36850.5030900@aarnet.edu.au> (raw)
In-Reply-To: <20060203094042.GB30738@flint.arm.linux.org.uk>
Hi Russell,
Thanks for your response.
> A normal user can't produce arbitarily formatted
> kernel messages
They don't need to provide an entire message, just a
AT string (a vector which a user could control
could be a volume label on removable media).
> You'd rather we threw away these messages?
When option 'r' is set, yes. Because Data Carrier Detect
is not asserted there can't be anything that is going to
read the messages. All we are doing is taking a long
time to drop each character off the end of the serial
cable.
Since the kernel takes a very long time to boot with
the 'r' option and no attached console the current
situation isn't correct.
There's one very nasty practical effect. Hayes modems
hang up if any character is typed during the interval
between off-hook and Data Carrier Detect (ie, the negotiation
period where the speaker outputs the tones). If you're
continually writing console messages (say from a failing
disk) then you can't successfully dial in to read the
messages to find out why the machine is hosed.
> It'd help if you talked to the right person - I've been looking after
> the serial layer since 2.5.something.
See my e-mail to you of 2003-10-21, which started:
Hi Russell,
I have ported the patch which fixes all kernel bugs
reported to me as the maintainer of the "Remote Serial
Console HOWTO" from 2.4 to Linus's BitKeeper (2.6.0-test8).
and contained the patch at
<http://www.aarnet.edu.au/~gdt/patch/console/serial-console.patch>
The previous patch of 2002-10-13 gave a much longer description
of the bugs and fixes:
[PATCH] 0/3 Fix serial console flow control
<http://www.ussg.iu.edu/hypermail/linux/kernel/0210.1/1790.html>
[PATCH] 1/3 Fix serial console flow control, serial.c
<http://www.ussg.iu.edu/hypermail/linux/kernel/0210.1/1791.html>
As I said earlier I'm happy to once more forward-port the
patch, test it and present it using the current version control
system as long as the effort is worth doing.
Regards,
Glen
--
Glen Turner Tel: (08) 8303 3936 or +61 8 8303 3936
Australia's Academic & Research Network www.aarnet.edu.au
next prev parent reply other threads:[~2006-02-03 14:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 1:21 Kumar Gala
2006-02-02 1:47 ` Alan Cox
2006-02-02 5:54 ` Kumar Gala
2006-02-02 8:05 ` Kumar Gala
2006-02-02 17:10 ` Kumar Gala
2006-02-03 1:58 ` Glen Turner
2006-02-03 9:40 ` Russell King
2006-02-03 14:27 ` Glen Turner [this message]
2006-02-03 16:02 ` Russell King
2006-02-03 17:08 ` Glen Turner
2006-02-03 22:23 ` Russell King
2006-02-04 11:15 ` Russell King
2006-02-04 16:18 ` Krzysztof Halasa
2006-02-04 23:16 ` Russell King
2006-02-04 23:54 ` Krzysztof Halasa
2006-02-05 0:00 ` Russell King
2006-02-05 12:57 ` Krzysztof Halasa
2006-02-03 17:46 ` Krzysztof Halasa
2006-02-03 22:13 ` Russell King
2006-02-04 16:08 ` Krzysztof Halasa
2006-02-04 23:20 ` Russell King
2006-02-05 3:12 ` Glen Turner
2006-02-05 21:26 ` Krzysztof Halasa
2006-02-06 9:47 ` Russell King
2006-02-07 3:27 ` Glen Turner
2006-02-03 15:05 ` Kumar Gala
2006-02-06 20:26 ` Pavel Machek
2006-02-06 20:55 ` Russell King
2006-02-07 4:00 ` Glen Turner
2006-02-07 9:18 ` Pavel Machek
2006-02-07 17:43 ` Russell King
2006-02-07 22:23 ` Krzysztof Halasa
2006-02-08 0:59 ` Junio C Hamano
2006-02-08 1:19 ` Lee Revell
2006-02-03 10:00 linux
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=43E36850.5030900@aarnet.edu.au \
--to=glen.turner@aarnet.edu.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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