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: <ac3eb2510811041155s3ef2df93w8fdd7ce7c009e994@mail.gmail.com>
Date:	Tue, 4 Nov 2008 20:55:15 +0100
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Nathaniel McCallum" <nathaniel@...emccallum.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] [PATCH] Loaded driver modalias

On Tue, Nov 4, 2008 at 19:39, Nathaniel McCallum
<nathaniel@...emccallum.com> wrote:
> Please CC me to responses as I'm not subscribed to LKML.  Also, this is my
> first kernel patch, advise is certainly welcome.
>
> For something I'm working on I have the need to answer the question, "given
> a hardware ID, does Linux distro X have a driver to support this hardware?"
> and more specifically, "which drivers support this hardware?" I can,
> generally speaking, get this data from files like
> /lib/modules/*/modules.alias.  However, this does not work for drivers built
> into the kernel.  With that in mind, I've cooked up a little proof of
> concept. Basically, its a sysfs file
> /sys/modules/$module/drivers/$driver/modalias that, when read, contains
> modalias-style filters for this driver.
>
> The attached patch only does this for PCI drivers, each subsystem would need
> a patch like this.  Is this idea crazy?  Is there a better implementation?

Hmm, what if that gets larger than 4k? It seems not really like
something for sysfs. There are also drivers which export a modalias
which matches more devices, than the device it actually would accept
to bind to. Some driver have logic in the match() function to exclude
stuff.

What's the exact information you need? Would it be sufficient  to ask
a bus with a modalias string, which driver of that bus matched that
device?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ