Bug 493170

Description of problem:

Opting to build IPv6 into the kernel (default "m" --> "y") forces the setting of CONFIG_XFRM_NALGO=y.  So far, so good.  Here's the kicker: CONFIG_XFRM_NALGO=y requires CONFIG_CRYPTO_API=y but it not forced to this required state by the kernel config system (I used "make menuconfig").


Version-Release number of selected component (if applicable):

2.6.18-128.1.1.el5


How reproducible:

Always


Steps to Reproduce:
1. "rpm -ivh /tmp/kernel-2.6.18-128.1.1.el5.src.rpm"
2. "rpmbuild -bp --target i686 /usr/src/redhat/SPEC/kernel.spec"
3. Use "make menuconfig" to opt for static inclusion of IPv6 in kernel
4. Attempt to build kernel
  
Actual results:

  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
net/built-in.o: In function `xfrm_find_algo':
/usr/src/linux-2.6.18-128.1.1.el5.sws/net/xfrm/xfrm_nalgo.c:451: undefined reference to `crypto_has_alg'
make: *** [.tmp_vmlinux1] Error 1


Expected results:

Config menuing system should not allow danging symbols.  If CONFIG_XFRM_NALGO requires CONFIG_CRYPTO_API, then either CONFIG_CRYPTO_API should be selected or the use should be informed that CONFIG_XFRM_NALGO cannot be configured for inclusion into the static kernel.

Additional info:

I am fully aware that Red Hat doesn't support user-configured kernels.  That said, I think you may be interested to know that you have this unaddressed dependency.