| 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
| ||
|
Date: Wed, 08 Aug 2007 22:02:07 +0200 From: Kay Sievers <kay.sievers@...y.org> To: Bill Nottingham <notting@...hat.com> Cc: Chuck Ebbert <cebbert@...hat.com>, Jeff Garzik <jeff@...zik.org>, linux-kernel <linux-kernel@...r.kernel.org>, Dmitry Torokhov <dtor@...ightbb.com>, Greg KH <greg@...ah.com> Subject: Re: 2.6.22: pcspkr driver no longer loads automatically On Wed, 2007-08-08 at 15:32 -0400, Bill Nottingham wrote: > Kay Sievers (kay.sievers@...y.org) said: > > It doesn't have any aliases, so seems it was never autoloaded. > > It was - prior kernels loaded it via the uevent generated from > /devices/platform/pcspkr. Newer kernels seem to never actually > trigger a uevent from that (tested with a combination of > udevmonitor and 'udevtrigger --subsystem-match=platform'.) Ah, ok, makes sense. Yeah, that weird "platform devices loads itself by the name" thing got disabled in the platform subsystem. It caused modprobe loops for other devices. The whole idea of issuing MODALIAS with plain module names instead of aliases can't really work, but the platform maintainer didn't like to use the usual aliases and the matches in the modules, for a reason I didn't understand while we talked about the problem last time. 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