linux-kernel - Re: [PATCH] serial: 8250: Make ISA ports optional

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1896224.oMI8M6J5T7@wuerfel>
Date:	Thu, 08 Jan 2015 23:05:12 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Peter Hurley <peter@...leysoftware.com>
Cc:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jiri Slaby <jslaby@...e.cz>, linux-serial@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	Tony Lindgren <tony@...mide.com>,
	Grant Likely <grant.likely@...aro.org>
Subject: Re: [PATCH] serial: 8250: Make ISA ports optional

On Thursday 08 January 2015 11:11:51 Peter Hurley wrote:
> 
> This interface is just storage and minor allocation, since the
> port-reuse behavior will be limited to the "universal" driver.
> From a sub-driver perspective, the shared storage is actually
> a hindrance, so that reduces the requirement to minor allocation.
> 
> And that's where I'm stuck at the moment -- how to share ttyS
> minor allocation. ttyS console is a related problem.

One idea that has come up in the past but never saw an implementation
is to make the ttyS namespace and minor numbers completely generic and
let any serial port driver use it. This would be a major rework, but
have the added advantage of cleaning up a number of other namespace
issues as well. There also lots of open question, in particular how
to maintain compatibility with existing drivers. One could imagine
that each uart always gets a ttyS device and optionally also gets
a device node for the same port with a driver specific chardev as
most of them do today. Or it could be an either/or decision that is
made at compile time or as a module parameter.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/