[yocto] kernel config fragments not applied

[Schmitt, Richard]

I think I have an apology to make.

My issue was that the config fragment I used (overlayfs.cfg) was:
CONFIG_OVERLAY_FS = yes

Note the spaces around the = sign.  With spaces, the setting is ignored.  When I changed the config fragment to:
CONFIG_OVERLAY_FS=yes
(without spaces), the setting took.

This was difficult to debug because there is no indication anywhere that the config fragment was bad.  There's not even notification anywhere that the config fragment tried to be applied.  So I assumed it wasn't even getting attempted.

Sorry for taking your time.  But thanks a lot for helping.  The fact that you had it working made me look even closer.

Rich

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield at windriver.com] 
Sent: Tuesday, January 10, 2017 5:36 PM
To: Schmitt, Richard <Richard.Schmitt at commscope.com>; yocto at yoctoproject.org
Subject: Re: [yocto] kernel config fragments not applied

On 2017-01-10 4:27 PM, Bruce Ashfield wrote:
> On 2017-01-10 4:20 PM, Bruce Ashfield wrote:
>> On 2017-01-10 4:13 PM, Schmitt, Richard wrote:
>>>
>>>
>>> -----Original Message-----
>>> From: Bruce Ashfield [mailto:bruce.ashfield at windriver.com]
>>> Sent: Tuesday, January 10, 2017 2:58 PM
>>> To: Schmitt, Richard <Richard.Schmitt at commscope.com>; 
>>> yocto at yoctoproject.org
>>> Subject: Re: [yocto] kernel config fragments not applied
>>>
>>> On 2017-01-10 1:05 PM, Schmitt, Richard wrote:
>>>>> I am having a heck of a hard time getting a minor kernel config 
>>>>> fragment applied.
>>>>>
>>>>>
>>>>>
>>>>> In order to minimize all variables, I am simply trying to build 
>>>>> linux-yocto for a qemux86 MACHINE target.
>>>>>
>>>>>
>>>>>
>>>>
>>>> What release ? Everything is working here, but I can switch to 
>>>> whatever release you are using and run the test there (I'm using 
>>>> master).
>>>
>>> I'm using krogoth.  I'll try a build based on master and see if it's 
>>> release specific.
>>
>> Thanks. I'm also spinning up a krogoth build .. you never know if 
>> something crept in. krogoth is before my audit code was visible, so 
>> hints as to why it failed likely aren't visible.
>
> Well I'll be .... different behaviour with krogoth. I just updated it 
> and some patches came in from what I had been using before. It could 
> be something that merged recently.
>
> Anyway, leave this with me. I'll debug it tonight and spin a fix.

I take that back.

My first build was tainted with old sstate and didn't actually do anything. Now that I'm building with a clean slate on krogoth, I can create a local layer, add a linux-yocto_4.4.bbappend and add a overlay.cfg to enable CONFIG_OVERLAYFS.

Is it possible that you could tar up your test layer and send it with me, so I can try it directly ?

Bruce

>
> Bruce
>
>
>>
>> Bruce
>>
>>>
>>>> Bruce
>>>
>>>>> There had been some discussion on the mailing list previously that 
>>>>> suggested making sure linux-yocto.inc was included within the recipes.
>>>>> The ones being used are standard poky recipes and they do include 
>>>>> the linux-yocto.inc file.
>>>>>
>>>>> My configuration is very simple.  I have my own layer and 
>>>>> linux-yocto
>>>>> bbappend:
>>>>>
>>>>> meta-mylayer/recipes-kernel/linux/linux-yocto_4.4.bbappend
>>>>>
>>>>> Whose contents are:
>>>>>
>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>>>>>
>>>>> SRC_URI += " \
>>>>>         file://overlayfs.cfg \
>>>>>         "
>>>>>
>>>>> With the config fragment in:
>>>>>
>>>>> meta-mylayer/recipes-kernel/linux/linux-yocto/overlayfs.cfg
>>>>>
>>>>> whose contents is:
>>>>>
>>>>> CONFIG_OVERLAY_FS=y
>>>>>
>>>>> If I do a "bitbake linux-yocto" I would expect it to generate a 
>>>>> config file that includes CONFIG_OVERLAY_FS=y and a kernel that 
>>>>> includes this filesystem.  I don't.
>>>>>
>>>>> My layer is parsed correctly and the bbappend is found and parsed.  
>>>>> I know this because in the tmp directory:
>>>>>
>>>>> tmp/work/qemux86-poky-linux/linux-yocto/4.4.26+gitAUTOINC+3030330b
>>>>> 06_c
>>>>> a6a08bd7f-r0/
>>>>>
>>>>> the file overlayfs.cfg exists.
>>>>>
>>>>> Searching the log files, the only one that references this file 
>>>>> though is log.do_unpack.  I do not see any reference to it in
>>>>> log.do_kernel_configme or log.do_configure.    I'm not sure how kernel
>>>>> fragments are applied, but looking through the classes and recipes 
>>>>> for linux-yocto in poky/meta, I do not see any code that would 
>>>>> apply kernel fragments.  So I'm not sure if I'm missing some piece.
>>>>>
>>>>> Searching through the files in poky/meta, I find meta-config.sh 
>>>>> only in recipes-core/uclibc and recipes-core/busybox.  That's why 
>>>>> I think I'm missing something.
>>>>>
>>>>> I'm using the krogoth branch of poky.
>>>>>
>>>>> What am I missing?
>>>>>
>>>>> Thanks,
>>>>> Rich
>>>
>>
>