realtime-lsm and Debian kernel

[Guenter Geiger <geiger@xdv.org>]

Hi,

I am maintaining a linux security module (LSM) called realtime
for the Debian system. Loading the module into the stock Debian
kernel only works if
CONFIG_SECURITY=y
and
CONFIG_SECURITY_CAPABILITIES=m,
which means that the kernel has to be security enabled and the
standard security setting (capability.ko) is a module.

For most of the time this has actually been the case for Debian kernels,
unfortunately these setting seem to have changed, so that with the new 
2.6.13 release the capability.ko is compiled into the kernel, which makes 
it impossible to influence security aspects of a running kernel.

Is there a reason for these changes ?
Would it be possible to stick to CONFIG_SECURITY=y and 
CONFIG_SECURITY_CAPABILITIES=m ?
If not, why ?
Can this be considered a bug and should I file a bug report ?

Cheers,

Guenter
(Please CC as I am not subscribed anymore)