From: Alex Williamson <alex.williamson@hp.com>
To: rmk+serial@arm.linux.org.uk
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] set membase in serial8250_request_port
Date: Mon, 04 Oct 2004 12:54:22 -0600 [thread overview]
Message-ID: <1096916062.4510.20.camel@tdi> (raw)
I'm running into a problem that seems to be caused by this really old
changeset:
http://linux.bkbits.net:8080/linux-2.5/cset@3d9f67f2BWvXiLsZCFwD-8s_E9AN6A
When I run 'setserial /dev/ttyS1 uart 16450' on an ia64 system w/ MMIO
UARTs, I get a NAT consumption oops from the kernel. The problem is
that this code path calls serial8250_release_port() where the membase
gets cleared. However, the subsequent call to serial8250_request_port()
doesn't restore membase, causing a read from a bad address. I don't see
many users of the UPF_IOREMAP flag, so I think the solution is to simply
make the remap case symmetric to the unmap case. Patch below. Thanks,
Alex
--
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
===== drivers/serial/8250.c 1.67 vs edited =====
--- 1.67/drivers/serial/8250.c 2004-09-13 18:23:24 -06:00
+++ edited/drivers/serial/8250.c 2004-10-04 12:12:34 -06:00
@@ -1733,7 +1733,7 @@
/*
* If we have a mapbase, then request that as well.
*/
- if (ret == 0 && up->port.flags & UPF_IOREMAP) {
+ if (ret == 0 && up->port.iotype == UPIO_MEM && up->port.mapbase) {
int size = res->end - res->start + 1;
up->port.membase = ioremap(up->port.mapbase, size);
next reply other threads:[~2004-10-04 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 18:54 Alex Williamson [this message]
2004-10-04 21:04 ` [PATCH] set membase in serial8250_request_port Russell King
2004-10-04 21:43 ` Alex Williamson
2004-10-18 14:56 ` Alex Williamson
2004-10-28 19:24 ` Alex Williamson
2004-10-30 10:28 ` 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=1096916062.4510.20.camel@tdi \
--to=alex.williamson@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+serial@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