On Tue, 14 Jun 2016, Christoph Hellwig wrote: > On Mon, Jun 13, 2016 at 08:32:41AM -0400, Prarit Bhargava wrote: > > Blacklisting a module in linux has long been a problem. The process of > > blacklisting a module has changed over time, and it seems that every OS > > does it slightly differently and depends on the age of the init system > > used on that OS. > > And why would we care about blacklisting a module? Because the "Current Best Practice" way to help users blacklist modules that won't drag you to nasty places trying to ensure they did it right (i.e. "mv" the .ko file away then trigger an initramfs update and reboot) just covers situations where the system actually boots/installs mostly fine in the first place. So, yes, such a feature looks like it would be rather useful, to the point that I'd even advocate for it to be backported (once it has been in a released mainline kernel for a while to remove any risk of regressions, of course). And if such a module blacklist feature ends up being invoked by the "nuke_module_from_orbit=<modules list>" parameter, I will pay the author (and the subsystem maintainer that manages to get that merged) a couple beers should we ever meet in real life :-) -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
