Re: Security downgrade? CONFIG_HOTPLUG required in 2.6.16?

[Adrian Bunk <bunk@stusta.de>]

On Thu, Mar 23, 2006 at 09:03:03PM -0800, Linda Walsh wrote:
> I had this config'ed out in 2.6.15 for machine that didn't have
> any hotpluggable devices.  It is also configured with all the
> modules it needs and has kernel-module loading disabled.
> 
> What has changed in 2.6.16 that my "static" machine now
> needs hotplugging?  As I understand it, hotplugging requires 
> application-level support code (in /etc/) and a special
> application level "demon" to run in order to support these
> requests.
> 
> I'd prefer my kernel not to be dependent on a run-time demon
> to load "arbitrary" (user defined) segments of code that could
> come from any source -- usually outside the vanilla kernel tree.
> 
> If I don't want a specific kernel or machine to be dynamically
> reconfigurable after boot, why do I need to build in a mechanism for
> runtime loading of modules?

- hotplugging devices != module loading
- CONFIG_HOTPLUG does not load any code into the kernel.
- hotplugging devices can work without any userspace support

As an example, hotplugging an USB hard disk works fine with 
CONFIG_MODULES=n and without any userspace support (assuming
a static /dev).

> Linda

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed