linux-kernel - Re: Serial: sc26xx device name

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4B07F7E4.1070207@gmail.com>
Date:	Sat, 21 Nov 2009 15:23:32 +0100
From:	Martin Fuzzey <mfuzzey@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	linux-serial@...r.kernel.org, tsbogend@...ha.franken.de,
	linux-kernel@...r.kernel.org
Subject: Re: Serial: sc26xx device name

Alan Cox wrote:
>> 2) How are device name conflicts handled?
>>     
>
> Badly - they should never occur but if someone didn't properly reserve
> the namespace they can and then whoever forgot to reserve the namespace
> loses.
>   
Currently this can't happen because the sc26xx driver uses ttySC205
in contradiction to ttySC0 shown in devices.txt

However if the driver were to be  "fixed" to use the name registered
in devices.txt a conflict could occur if a sc26xx chip were used on
a superH system.

The problem seems to be that while the major/minor numbers in devices.txt
are unique (and the drivers are correctly using their registered numbers),
the _names_ are not unique (at least in this case - I haven't checked for
others).

--
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/