From: Russell King <rmk@arm.linux.org.uk>
To: Christoph Bartelmus <columbus@hit.handshake.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: serial port driver grabs occupied port
Date: Sun, 3 Feb 2002 00:33:09 +0000 [thread overview]
Message-ID: <20020203003309.E19201@flint.arm.linux.org.uk> (raw)
In-Reply-To: <8IBS9f7Xz9B@hit-columbus.hit.handshake.de>
In-Reply-To: <8IBS9f7Xz9B@hit-columbus.hit.handshake.de>; from columbus@hit.handshake.de on Sat, Feb 02, 2002 at 11:21:00PM +0000
On Sat, Feb 02, 2002 at 11:21:00PM +0000, Christoph Bartelmus wrote:
> Now the problem:
> 3. Open the /dev/ttySx for the port that is occupied by the lirc_serial
> module. rs_open() does not check the state of the serial port and returns
> no error. Now you can use setserial to hijack the port... lirc_serial
> stops working.
One of setserial's basic functions is to configure a ttyS device for a
serial port that you know is there. In this patch, you are preventing
any port that is in 'PORT_UNKNOWN' state from being changed, even if
you want to change the IRQ and IO base address. This is a different,
but nevertheless fundamental problem.
The real bug is that serial.c should allows you to change the port from
'PORT_UNKNOWN' even when it can't grab the resources for the port.
Thanks for finding it - are you able to work on this more to come up
with a better fix?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2002-02-03 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 23:21 PROBLEM: serial port driver grabs occupied port Christoph Bartelmus
2002-02-03 0:33 ` Russell King [this message]
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=20020203003309.E19201@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=columbus@hit.handshake.de \
--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