linux-kernel - Re: patch driver-core-warn-about-duplicate-driver-names-on-the-same-bus.patch added to gregkh-2.6 tree

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]

Date:	Tue, 29 Apr 2008 12:41:56 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Greg KH <gregkh@...e.de>
Cc:	Stas Sergeev <stsp@...et.ru>,
	Linux kernel <linux-kernel@...r.kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: patch	driver-core-warn-about-duplicate-driver-names-on-the-same-bus.patch	added to gregkh-2.6 tree

At Mon, 28 Apr 2008 21:58:49 -0700,
Greg KH wrote:
> 
> On Tue, Apr 29, 2008 at 08:48:08AM +0400, Stas Sergeev wrote:
> > Hello.
> > 
> > gregkh@...e.de wrote:
> > > This is a note to let you know that I've just added the patch titled
> > >      Subject: driver core: warn about duplicate driver names on the same bus
> > > to my gregkh-2.6 tree.  Its filename is
> > Thanks.
> > 
> > Takashi, do you think this fixes the
> > pcspkr/snd-pcsp conflict sufficienly
> > well? I think the Kconfig protection
> > is no longer needed. For the better
> > convinience the modprobe rule can be
> > created that will remove one driver
> > before inserting another. But this is
> > optional.
> 
> No, don't rely on the driver core warning and catching code errors like
> this, that's not a good idea at all.  I like the warning and your patch,
> but don't assume it's always going to be there.

But multiple drivers for the same device are allowed on other buses
like PCI.  I think this is no reason to prohibit the multiple platform
drivers for the same platform device.

Though, I think the snd-pcsp driver could be better built on the top
of input pcspkr driver, or coexist with it.  Then we'll have no more
conflict about platform name space.

When you compare input pcspkr.c and sound pcsp_input.c, you can find
that most of codes are identical.  What we'd need is a hook on
pcspkr.c that adds a dynamic check whether snd-pcsp (or any ohter)
is running.


thanks,

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