Compilation error when using R17 legato and CONFIG_EXT4_FS=y

Legato Linux distribution (Yocto project)
1

Hello everyone,

I tried to build a BSP with the R17 legato and I noticed that when I have this config flag: CONFIG_EXT4_FS=y there are some compilation errors:

| /home/coj8brg/workspace/from_scratch/slimscaley_bsp/linux_distro/yocto_nonus/poky/build_production/tmp/work-shared/swi-mdm9x28-wp/kernel-source/fs/ext4/namei.c: In function 'ext4_resetent':
|  /home/coj8brg/workspace/from_scratch/slimscaley_bsp/linux_distro/yocto_nonus/poky/build_production/tmp/work-shared/swi-mdm9x28-wp/kernel-source/fs/ext4/namei.c:3686:11: error: too few arguments to function 'ext4_find_entry'
|   3686 |  old.bh = ext4_find_entry(old.dir, &old.dentry->d_name, &old.de, NULL);
|        |           ^~~~~~~~~~~~~~~
|  /home/coj8brg/workspace/from_scratch/slimscaley_bsp/linux_distro/yocto_nonus/poky/build_production/tmp/work-shared/swi-mdm9x28-wp/kernel-source/fs/ext4/namei.c:1662:28: note: declared here
|   1662 | static struct buffer_head *ext4_find_entry(struct inode *dir,
|        |                            ^~~~~~~~~~~~~~~
|  /home/coj8brg/workspace/from_scratch/slimscaley_bsp/linux_distro/yocto_nonus/poky/build_production/tmp/work-shared/swi-mdm9x28-wp/kernel-source/fs/ext4/namei.c: In function 'ext4_rename':
|  /home/coj8brg/workspace/from_scratch/slimscaley_bsp/linux_distro/yocto_nonus/poky/build_production/tmp/work-shared/swi-mdm9x28-wp/kernel-source/fs/ext4/namei.c:3865:6: error: implicit declaration of function 'ext4_encrypted_inode'; did you mean 'ext4_write_inode'? [-Werror=implicit-function-declaration]
|   3865 |      ext4_encrypted_inode(new.dir) &&
|        |      ^~~~~~~~~~~~~~~~~~~~
|        |      ext4_write_inode
|  cc1: some warnings being treated as errors

Has anyone had this error? Or does anyone know how to fix it (besides patching this file)?

2

I remember it works in R13.3:

did you try other version like R16.3?

https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-16,-d-,3-components/#sthash.UTFgtfqz.dpbs

Lastly, you might need to port the code from here: