Re: [integrity:next-integrity-testing 5/5] security/integrity/ima/ima_asymmetric_keys.c:53:6: error: redefinition of 'ima_init_key_queue'

[James Bottomley <James.Bottomley@HansenPartnership.com>]

On Sun, 2020-01-05 at 19:58 -0800, Lakshmi Ramasubramanian wrote:
> On 1/5/20 11:16 AM, James Bottomley wrote:
> 
> > Well, yes, you just need to condition the build of
> > ima_asymmetric_keys
> > on a boolean instead of a tristate, so you introduce an
> > intermediate
> > one:
> > 
> > config IMA_ASYMMETRIC_KEYS
> > 	bool
> > 	default y
> > 	depends on ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
> > 
> > James
> 
> Thanks for your help James.
> 
> Hi Mimi,
> 
> I have defined a new config as James has suggested above and
> verified the kernel builds fine with the ".config" files given by
> "kbuild test robot <lkp@intel.com>".
> 
> Would it be possible to share all the ".config" files that
> "kbuild test robot" would build with? I'll make sure my changes
> build fine with all those.

I'm afraid it's not possible: the kbuild robot is doing make
randconfig, which generates a random configuration for the kernel.  The
randconfig testing is the easiest way to detect Kconfig problems like
this one.  You can, of course, do make randconfig yourself, but you
have to run through it a lot of times to get the coverage the robot
gets.

James