TOPDIR/tmp/work/beaglebone_yocto-poky-linux-gnueabi/lttng-modules/2.10.9-r0/lttng-modules-2.10.9/probes/../blacklist/kprobes.h:19:4: error: #error "Your kernel is known to have buggy optimized kprobes implementation. Fixed by commit 0ac569bf6a7983c0c5747d6df8db9dc05bc92b6c \"ARM: 8834/1: Fix: kprobes: optimized kprobes illegal instruction\" in Linux. Disable CONFIG_OPTPROBES or upgrade your kernel." # error "Your kernel is known to have buggy optimized kprobes implementation. Fixed by commit 0ac569bf6a7983c0c5747d6df8db9dc05bc92b6c \"ARM: 8834/1: Fix: kprobes: optimized kprobes illegal instruction\" in Linux. Disable CONFIG_OPTPROBES or upgrade your kernel." ^~~~~ The 4.14 got updated and now we see this error. https://github.com/lttng/lttng-modules/commit/2d16de12b197aed57212826187bcb0ab24ad071e
commit e46daee53bb50bde38805f1823a182979724c229 Author: Kees Cook <keescook@chromium.org> Date: Tue Oct 30 22:12:56 2018 +0100 ARM: 8806/1: kprobes: Fix false positive with FORTIFY_SOURCE The arm compiler internally interprets an inline assembly label as an unsigned long value, not a pointer. As a result, under CONFIG_FORTIFY_SOURCE, the address of a label has a size of 4 bytes, which was tripping the runtime checks. Instead, we can just cast the label (as done with the size calculations earlier). Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1639397 Reported-by: William Cohen <wcohen@redhat.com> Fixes: 6974f0c4555e ("include/linux/string.h: add the option of fortified string.h functions") Cc: stable@vger.kernel.org Acked-by: Laura Abbott <labbott@redhat.com> Acked-by: Masami Hiramatsu <mhiramat@kernel.org> Tested-by: William Cohen <wcohen@redhat.com> Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk> It was introduced in the 4.20 cycle. It was also backported to the 4.19 and 4.14 branch.
This issue is fixed upstream by [1] and is present in the 5.0 kernel release. [1] 0ac569bf6a7983c0c5747d6df8db9dc05bc92b6c The fix was backported to 4.20, 4.19 and 4.14 branch. It is included starting at: v5.0.0 v4.20.13 v4.19.26 v4.14.104
I believe updating thud's 4.14 to .120 should address this error. Fix is pending kernel updates that should be done in the next few weeks. Not hold up dot release.
Created attachment 4561 [details] bump to v4.14.143 Try the following patch, it takes 4.14 to .143
giving it a try today
in AB being build tested.
heheheh, it kept failing even after applying patch.. is a meta-yocto-bsp so it needs patching too. I have one tested.
Created attachment 4562 [details] bump yp bsps to 4.14.143 too
bsp patch sent to list.
(In reply to comment #4) > Created attachment 4561 [details] > bump to v4.14.143 > > Try the following patch, it takes 4.14 to .143 want me to send it to the list?
patches sent to list
in stable/thud-next https://git.openembedded.org/openembedded-core-contrib/commit/?h=stable/thud-nmut&id=f5be8c8309a932cde507ba24d042880a922df0b6
waiting for merge.
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=meta-yocto/stable/thud-nmut&id=f864a48c9397073e82eaaf1bbbf49fbedb08c8e9 http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=meta-yocto/stable/thud-nmut&id=e052e84e8a77e6ae4d21630dbb0ec60c751f7e1a need to be merged
http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto/commit/?h=thud&id=347093d4d24eac8165e2be66a4a7503af4bfc833
closing