The attached patch improves blacklisting to work on all aliases, and not just the ones provided by modules internally (pci:* and similar). Original description: From d2a39380938b248f721066fff43746bcfd2558e6 Mon Sep 17 00:00:00 2001 From: Kay Sievers <kay.sievers@vrfy.org> Date: Thu, 30 Aug 2007 02:16:01 +0200 Subject: [PATCH] modprobe: apply the blacklist to all aliases Module blacklist entries did not get applied to configured aliases. Modprobe configuration files are often used to supply missing aliases which are (now) not provided by kernel modules itself. This lets possibly configured blacklist entries disable all alias resolving, regardless of the source of the alias. Signed-off-by: Kay Sievers <kay.sievers@vrfy.org> The easiest test-case for this is: modprobe pnp:dPNP0800 it loads pcspkt even when it is blacklisted, as this uses a user alias from /etc/modprobe.d/pnp-aliases alias pnp:dPNP0800 pcspkr with patch applied it no longer loads pcspkr.
Created attachment 130610 [details, diff] modprobe-apply-the-blacklist-to-all-aliases.patch
where was that e-mail sent to ? cant find it via google ...
The quoted text is from a git patch and no mail. It is from Kay Sievers branch, but as he told me it should already be pulled to upstream branch.
Is there any reason not to apply this?
3.4 now in the tree with this fix
*** Bug 201653 has been marked as a duplicate of this bug. ***
