From: Russell King <rmk@arm.linux.org.uk>
To: Ed Vance <EdV@macrolink.com>
Cc: "'Roman Kurakin'" <rik@cronyx.ru>, linux-kernel@vger.kernel.org
Subject: Re: Serial.c BUG 2.4.x-2.5x
Date: Wed, 6 Mar 2002 20:39:36 +0000 [thread overview]
Message-ID: <20020306203936.C26344@flint.arm.linux.org.uk> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A76CB@EXCHANGE>
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A76CB@EXCHANGE>; from EdV@macrolink.com on Fri, Mar 01, 2002 at 11:07:03AM -0800
On Fri, Mar 01, 2002 at 11:07:03AM -0800, Ed Vance wrote:
> On Fri, Mar 01, 2002 at 4:19 AM, Roman Kurakin wrote:
> >
> > Who is responsible person for applying [serial driver] patches
> > to main tree?
This particular bug has already been fixed in the rewrite, as I originally
said back on 14 November 2001.
The patch does fine for the most part, but I have two worries:
1. the possibilities of pushing through changes in the IO or memory space
by changing the other space at the same time. (ie, port = 1, iomem =
0xfe007c00 and you already have a line at port = 0, iomem = 0xfe007c00).
I delt with this properly using the resource management subsystem.
2. there seems to be a lack of security considerations for changing the
iomem address. (ie, changing the iomem address without CAP_SYS_ADMIN.
I added this as an extra check for change_port)
> I then asked Russell to set the rules for this co-ordination and no response
> has been forthcoming. Perhaps he missed my question?
I have a fair bit of email backed up at the moment, but I have been in
contact with Ted T'so recently. I won't say much more at the moment,
but should have something in a month or two. Until then I'd rather not
say too much publically.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-03-06 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 19:07 Serial.c BUG 2.4.x-2.5x Ed Vance
2002-03-06 20:39 ` Russell King [this message]
2002-03-07 13:53 ` Roman Kurakin
-- strict thread matches above, loose matches on Subject: below --
2002-03-19 0:16 Ed Vance
2002-03-07 16:51 Ed Vance
2002-03-01 12:18 Roman Kurakin
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=20020306203936.C26344@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=EdV@macrolink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rik@cronyx.ru \
/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;
as well as URLs for NNTP newsgroup(s).