CONFIG_SECURITY_ROOTPLUG [was: Re: 2.6.27-rc7 no init found on the root partition?]
Hello,
I finally found my problems with no init found.
It was caused by the CONFIG_SECURITY_ROOTPLUG option.
I wonder why this option in 2.6.26.3 kernel allows the kernel boot up, while with 2.6.27-rc7, the kernel is unable to run even init.
Signature · 1 line
Lukáš Hejtmánek
Quoted 8 lines · Lukas Hejtmanek
Hello,
I finally found my problems with no init found.
It was caused by the
CONFIG_SECURITY_ROOTPLUGoption.I wonder why this option in 2.6.26.3 kernel allows the kernel boot up, while with 2.6.27-rc7, the kernel is unable to run even init.
Hmm, is there a difference in the device drivers such that root_plug simply isn't able to find the usb 'key' in 2.6.27-rc7?
When you boot with CONFIG_SECURITY_ROOTPLUG=n, can you read the usb key?
-serge
Quoted 4 lines · Serge E. Hallyn
Hmm, is there a difference in the device drivers such that
root_plugsimply isn't able to find the usb 'key' in 2.6.27-rc7?When you boot with
CONFIG_SECURITY_ROOTPLUG=n, can you read the usb key?
I do not have USB key at all. So maybe there is a security bug in 2.6.26.3?
Signature · 1 line
Lukáš Hejtmánek
Quoted 7 lines · Lukas Hejtmanek
Quoted 4 lines · Serge E. Hallyn
Hmm, is there a difference in the device drivers such that
root_plugsimply isn't able to find the usb 'key' in 2.6.27-rc7?When you boot with
CONFIG_SECURITY_ROOTPLUG=n, can you read the usb key?I do not have USB key at all. So maybe there is a security bug in 2.6.26.3?
It must be a bug in 26.3 - if you don't have the proper USB dongle/key/whatever inserted, it shouldn't have come up.
Quoted 8 lines · Lukas Hejtmanek
Hello,
I finally found my problems with no init found.
It was caused by the
CONFIG_SECURITY_ROOTPLUGoption.I wonder why this option in 2.6.26.3 kernel allows the kernel boot up, while with 2.6.27-rc7, the kernel is unable to run even init.
If you enable that option, you have to have the specific USB device plugged into your system in order for any process to run as root (like init).
So, odds are you don't have this specific device, so either specify a different device id, or don't build it into your kernel :)
thanks,
greg k-h