[OE-core] [PATCH] lttng-modules: upgrade 2.10.8 -> 2.10.9

[richard.purdie at linuxfoundation.org]

On Wed, 2019-05-08 at 23:30 +0300, Adrian Bunk wrote:
> On Wed, May 08, 2019 at 09:06:19PM +0100, Richard Purdie wrote:
> > On Tue, 2019-05-07 at 16:11 +0300, Adrian Bunk wrote:
> > > Remove the backported patches.
> > > 
> > > Signed-off-by: Adrian Bunk <bunk at stusta.de>
> > 
> > Unfortunately this seemed to cause:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/46/builds/574
> 
> ...
> recipe linux-yocto-4.19.14+gitAUTOINC+9bda6190bf_eebb51300a-r0: task do_compile: Succeeded
> ...
>  In file included from /home/pokybuild/yocto-worker/beaglebone-lsb/build/build/tmp/work/beaglebone_yocto-poky-linux-gnueabi/lttng-modules/2.10.9-r0/lttng-modules-2.10.9/probes/lttng-kprobes.c:31:
> > /home/pokybuild/yocto-worker/beaglebone-lsb/build/build/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."
> >     ^~~~~
> > make[4]: *** 
> [/home/pokybuild/yocto-worker/beaglebone-lsb/build/build/tmp/work/beaglebone_yocto-poky-linux-gnueabi/lttng-modules/2.10.9-r0/lttng-modules-2.10.9/probes/lttng-kprobes.o] Error 1
> ...
> 
> 
> Upstream turned a runtime breakage into a build failure:
> http://git.lttng.org/?p=lttng-modules.git;a=commit;h=2d16de12b197aed57212826187bcb0ab24ad071e
> 
> IOW, this needs an update of beaglebone-yocto in
> meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> (4.19.34 already seems to be in the git tree).

Right, sorry, I hadn't actually read the error :/.

CCing Kevin/Bruce.

Cheers,

Richard