From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Kilau, Scott" <Scott_Kilau@digi.com>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
Wen Xiong <wenxiong@us.ibm.com>
Subject: Re: [ patch 4/7] drivers/serial/jsm: new serial device driver
Date: Wed, 9 Mar 2005 16:16:22 +0000 [thread overview]
Message-ID: <20050309161622.G25398@flint.arm.linux.org.uk> (raw)
In-Reply-To: <71A17D6448EC0140B44BCEB8CD0DA36E04B9D9E2@minimail.digi.com>; from Scott_Kilau@digi.com on Tue, Mar 08, 2005 at 03:47:45PM -0600
On Tue, Mar 08, 2005 at 03:47:45PM -0600, Kilau, Scott wrote:
> For example, lets say a customer has a modem connected to a serial port.
>
> If you were to open up the port with an "stty -a" to get the current
> settings and signals, you would unintentionally raise RTS and DTR.
That isn't special to this driver though. Maybe it should be fixed for
all serial drivers, since the situation you mention above is not limited
to just this driver.
As you say, you may have a modem connected, which may have been configured
to automatically dial a predetermined number when DTR is raised.
Maybe we need a solution which applies to all drivers?
> This is why we export the various signals/stats/signals to sysfs (used
> to be proc), so our management tools can get the information about the
> serial port without being intrusive by opening up the port.
Note that exporting statistics can be a security bug, especially if that
includes the number of bytes sent/received. For an explaination of this,
please lookup the reason why the /proc/tty/driver directory was made
unreadable to userspace.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-03-09 16:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 21:47 [ patch 4/7] drivers/serial/jsm: new serial device driver Kilau, Scott
2005-03-09 0:02 ` Greg KH
2005-03-09 16:16 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 2:36 Kilau, Scott
2005-03-09 5:50 ` Greg KH
2005-02-27 23:39 Wen Xiong
2005-02-28 3:21 ` Christoph Hellwig
2005-02-28 6:39 ` Greg KH
2005-03-04 21:08 ` Wen Xiong
2005-03-04 22:01 ` Greg KH
2005-03-07 22:46 ` Wen Xiong
2005-03-08 6:44 ` Greg KH
2005-03-08 18:55 ` Wen Xiong
2005-03-08 23:58 ` Greg KH
2005-03-09 15:47 ` Wen Xiong
2005-03-09 16:35 ` Greg KH
2005-03-09 17:18 ` Wen Xiong
2005-03-09 18:58 ` Greg KH
2005-03-09 16:11 ` Russell King
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=20050309161622.G25398@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Scott_Kilau@digi.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wenxiong@us.ibm.com \
/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