Re: [OE-core] [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds

[Jens Rehsack]

> Am 15.09.2020 um 00:34 schrieb Bruce Ashfield :
> 
> From: Jens Rehsack 
> 
> Backporting the 10 patches since the lttng 2.12.2 release. We'll drop
> them once .3 is released, but for now, we need the fixes to build

Yet another question: there is a stable-2.12 branch ... wouldn't it be 
reasonable to use this one as upstream source instead of the tarball?

> against the latest 5.4, 5.8 and 5.9 kernels.
> 
> We also bump the devupstream SRCREV to pickup the same changes.
> -=-=-=-=-=-=-=-=-=-=-=-

--
Jens Rehsack - rehs...@gmail.com



signature.asc
Description: Message signed with OpenPGP
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142575): 
https://lists.openembedded.org/g/openembedded-core/message/142575
Mute This Topic: https://lists.openembedded.org/mt/76853782/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds

[Jens Rehsack]

> Am 15.09.2020 um 00:35 schrieb Bruce Ashfield :
> 
> I squashed the other lttng patch to create this, and it looks like the
> author is messed up and some kind of strange encoding on one of the

No worries about that :)

> embedded patches.
> 
> git send email complained on the way out.
> 
> Bruce
> 
> On Mon, Sep 14, 2020 at 6:34 PM  wrote:
>> 
>> From: Jens Rehsack 
>> 
>> Backporting the 10 patches since the lttng 2.12.2 release. We'll drop
>> them once .3 is released, but for now, we need the fixes to build
>> against the latest 5.4, 5.8 and 5.9 kernels.
>> 
>> We also bump the devupstream SRCREV to pickup the same changes.
>> 
>> Signed-off-by: Bruce Ashfield 
>> ---
>> ...ndency-issue-when-building-in-tree-w.patch |  54 ++
>> ...ce.h-into-the-mmu-sub-directory-v5.9.patch |  41 +
>> ...Make-kvm_mmu_page-definition-and-acc.patch |  39 +
>> ...he-length-of-per-inode-prealloc-list.patch |  84 ++
>> ...e-via-a-block-bitmap-read-is-prefetc.patch |  63 ++
>> ...al-of-smp_-read_barrier_depends-v5.9.patch | 391 
>> ...teback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch |  59 ++
>> ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 +++
>> ...es-for-ext4_discard_preallocations-a.patch |  52 +
>> .../0010-Fix-system-call-filter-table.patch   | 918 ++
>> .../lttng/lttng-modules_2.12.2.bb |  12 +-
>> 11 files changed, 1829 insertions(+), 1 deletion(-)
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0003-fix-KVM-x86-mmu-Make-kvm_mmu_page-definition-and-acc.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0004-fix-ext4-limit-the-length-of-per-inode-prealloc-list.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0005-fix-ext4-indicate-via-a-block-bitmap-read-is-prefetc.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0006-fix-removal-of-smp_-read_barrier_depends-v5.9.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0007-fix-writeback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0008-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0009-fix-version-ranges-for-ext4_discard_preallocations-a.patch
>> create mode 100644 
>> meta/recipes-kernel/lttng/lttng-modules/0010-Fix-system-call-filter-table.patch
>> 
>> diff --git 
>> a/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
>>  
>> b/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
>> new file mode 100644
>> index 00..ae8bec45de
>> --- /dev/null
>> +++ 
>> b/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
>> @@ -0,0 +1,54 @@
>> +From ff4d1d7e85be94ef43709cd698f0ec9a12f247d1 Mon Sep 17 00:00:00 2001
>> +From: Beniamin Sandu 
>> +Date: Thu, 13 Aug 2020 16:24:39 +0300
>> +Subject: [PATCH 01/10] Kconfig: fix dependency issue when building in-tree
>> + without CONFIG_FTRACE
>> +
>> +When building in-tree, one could disable CONFIG_FTRACE from kernel
>> +config which will leave CONFIG_TRACEPOINTS selected by LTTNG modules,
>> +but generate a lot of linker errors like below because it leaves out
>> +other stuff, e.g.:
>> +
>> +trace.c:(.text+0xd86b): undefined reference to `trace_event_buffer_reserve'
>> +ld: trace.c:(.text+0xd8de): undefined reference to 
>> `trace_event_buffer_commit'
>> +ld: trace.c:(.text+0xd926): undefined reference to `event_triggers_call'
>> +ld: trace.c:(.text+0xd942): undefined reference to 
>> `trace_event_ignore_this_pid'
>> +ld: net/mac80211/trace.o: in function 
>> `trace_event_raw_event_drv_tdls_cancel_channel_switch':
>> +
>> +It appears to be caused by the fact that TRACE_EVENT macros in the Linux
>> +kernel depend on the Ftrace ring buffer as soon as CONFIG_TRACEPOINTS is
>> +enabled.
>> +
>> +Steps to reproduce:
>> +
>> +- Get a clone of an upstream stable kernel and use scripts/built-in.sh on it
>> +
>> +- Configure a standard x86-64 build, enable built-in LTTNG but disable
>> +  CONFIG_FTRACE from Kernel Hacking-->Tracers using menuconfig
>> +
>> +- Build will fail at linking stage
>> +
>> +Upstream-Status: Backport
>> +
>> +Signed-off-by: Beniamin Sandu 
>> +Signed-off-by: Mathieu Desnoyers 
>> +---
>> + Kconfig | 2 +-
>> + 1 file changed, 1 insertion(+), 1 deletion(-)
>> +
>> +diff --git a/Kconfig b/Kconfig
>> +index acdab73..10eccff 100644
>> +--- a/Kconfig
>>  b/Kconfig
>> +@@ -2,7 +2,7 @@
>> +
>> + config LTTNG
>> +   tristate "LTTng support"
>> +-  select TRACEPOINTS
>> ++  select TRACING
>> +   help
>> + LTTng is an

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[Stephen Jolley]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 338
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142573): 
https://lists.openembedded.org/g/openembedded-core/message/142573
Mute This Topic: https://lists.openembedded.org/mt/76858128/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] nativesdk: Set TARGET_CC_KERNEL_ARCH for sdk

[Douglas via lists.openembedded.org]

We install the linux-libc-headers for the build machine, so
take control of the TARGET_CC_KERNEL_ARCH.
In this way, we get no task signature changes when we build
nativesdk-linux-libc-headers with different MACHINEs,
avoiding a build-through from glibc up.

Signed-off-by: Douglas Royds 
---
 meta/classes/nativesdk.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
index 7f2692c51a..420ee52be2 100644
--- a/meta/classes/nativesdk.bbclass
+++ b/meta/classes/nativesdk.bbclass
@@ -47,6 +47,7 @@ TARGET_VENDOR = "${SDK_VENDOR}"
 TARGET_OS = "${SDK_OS}"
 TARGET_PREFIX = "${SDK_PREFIX}"
 TARGET_CC_ARCH = "${SDK_CC_ARCH}"
+TARGET_CC_KERNEL_ARCH = "${SDK_CC_ARCH}"
 TARGET_LD_ARCH = "${SDK_LD_ARCH}"
 TARGET_AS_ARCH = "${SDK_AS_ARCH}"
 TARGET_CPPFLAGS = "${BUILDSDK_CPPFLAGS}"
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142572): 
https://lists.openembedded.org/g/openembedded-core/message/142572
Mute This Topic: https://lists.openembedded.org/mt/76858109/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] nativesdk-linux-libc-headers with two different MACHINEs

[Khem Raj]

OK please test this patch for full SDK builds and any other testing
you do and report back if it works in all cases.

On Mon, Sep 14, 2020 at 5:42 PM Douglas Royds
 wrote:
>
> Yes it did, thanks!
>
>
> On 15/09/20 12:31 pm, Khem Raj wrote:
>
> > I think MACHINE should not matter for nativesdk packages. Does
> > something like this work
> >
> > diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
> > index 7f2692c51a..bb1dfd84c0 100644
> > --- a/meta/classes/nativesdk.bbclass
> > +++ b/meta/classes/nativesdk.bbclass
> > @@ -10,7 +10,7 @@ LIBCOVERRIDE = ":${NATIVESDKLIBC}"
> >   CLASSOVERRIDE = "class-nativesdk"
> >   MACHINEOVERRIDES = ""
> >   MACHINE_FEATURES = ""
> > -
> > +MACHINE = "${SDKMACHINE}"
> >   MULTILIBS = ""
> >
> >   # we need consistent staging dir whether or not multilib is enabled
> >
> > On Mon, Sep 14, 2020 at 5:13 PM Douglas via lists.openembedded.org
> >  wrote:
> >> For the experiment, I wanted to see whether I could achieve no task 
> >> signature change when building nativesdk-glibc for two different MACHINEs, 
> >> but I found that the do_install sigdata for nativesdk-linux-libc-headers 
> >> changed. We're installing the linux-libc-headers for the build machine, so 
> >> it seems to make sense to take control of the TARGET_CC_KERNEL_ARCH:
> >>
> >> diff --git a/meta/classes/nativesdk.bbclass 
> >> b/meta/classes/nativesdk.bbclass
> >> index 32c3aa32ad..655439dd73 100644
> >> --- a/meta/classes/nativesdk.bbclass
> >> +++ b/meta/classes/nativesdk.bbclass
> >> @@ -47,6 +47,7 @@ TARGET_VENDOR = "${SDK_VENDOR}"
> >>   TARGET_OS = "${SDK_OS}"
> >>   TARGET_PREFIX = "${SDK_PREFIX}"
> >>   TARGET_CC_ARCH = "${SDK_CC_ARCH}"
> >> +TARGET_CC_KERNEL_ARCH = "${SDK_CC_ARCH}"
> >>   TARGET_LD_ARCH = "${SDK_LD_ARCH}"
> >>
> >> Which leaves me with:
> >>
> >> basehash changed from 42ed3480096bb7ea53b60dc876da0613 to 
> >> 38ea60bdac041673f2c491d7bbabe17c
> >> Variable MACHINE value changed from 'qemuarm' to 'qemux86-64'
> >> runtaskdeps changed:
> >> linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk 
> >> with hash cbb186fe33cd69cb0b06384e4d50a244
> >>   changed to
> >> linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk 
> >> with hash 4d34d6981b79d0fccc768566bf2fa533
> >> Hash for dependent task 
> >> linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk 
> >> changed from cbb186fe33cd69cb0b06384e4d50a244 to 
> >> 4d34d6981b79d0fccc768566bf2fa533
> >>
> >> The configure and compile tasks for linux-libc-headers are both set to 
> >> noexec. For the experiment, I added an empty do_configure task, with this 
> >> result on the do_configure sigdata:
> >>
> >> basehash changed from f13c2a2066fa48f0ccac35c085537c71 to 
> >> bb13f2b1b1e7e376f3fb5a8ec888
> >> Variable MACHINE value changed from 'qemux86-64' to 'qemuarm'
> >>
> >> What to do? Why is the MACHINE variable included in the task signature (it 
> >> is unset in run.do_configure)? Adding it to BB_HASHBASE_WHITELIST had no 
> >> effect. What am I missing here?
> >>
> >> 
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142571): 
https://lists.openembedded.org/g/openembedded-core/message/142571
Mute This Topic: https://lists.openembedded.org/mt/76855451/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] nativesdk: Re-define MACHINE = SDKMACHINE

[Khem Raj]

Ensures, that change in MACHINE variable does not trigger rebuilds
of nativesdk packages, target machine should not matter for nativesk
packages

Signed-off-by: Khem Raj 
---
 meta/classes/nativesdk.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
index 7f2692c51a..bb1dfd84c0 100644
--- a/meta/classes/nativesdk.bbclass
+++ b/meta/classes/nativesdk.bbclass
@@ -10,7 +10,7 @@ LIBCOVERRIDE = ":${NATIVESDKLIBC}"
 CLASSOVERRIDE = "class-nativesdk"
 MACHINEOVERRIDES = ""
 MACHINE_FEATURES = ""
-
+MACHINE = "${SDKMACHINE}"
 MULTILIBS = ""
 
 # we need consistent staging dir whether or not multilib is enabled
-- 
2.28.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142570): 
https://lists.openembedded.org/g/openembedded-core/message/142570
Mute This Topic: https://lists.openembedded.org/mt/76856300/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] nativesdk-linux-libc-headers with two different MACHINEs

[Douglas via lists.openembedded.org]

Yes it did, thanks!


On 15/09/20 12:31 pm, Khem Raj wrote:


I think MACHINE should not matter for nativesdk packages. Does
something like this work

diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
index 7f2692c51a..bb1dfd84c0 100644
--- a/meta/classes/nativesdk.bbclass
+++ b/meta/classes/nativesdk.bbclass
@@ -10,7 +10,7 @@ LIBCOVERRIDE = ":${NATIVESDKLIBC}"
  CLASSOVERRIDE = "class-nativesdk"
  MACHINEOVERRIDES = ""
  MACHINE_FEATURES = ""
-
+MACHINE = "${SDKMACHINE}"
  MULTILIBS = ""

  # we need consistent staging dir whether or not multilib is enabled

On Mon, Sep 14, 2020 at 5:13 PM Douglas via lists.openembedded.org
 wrote:

For the experiment, I wanted to see whether I could achieve no task signature 
change when building nativesdk-glibc for two different MACHINEs, but I found 
that the do_install sigdata for nativesdk-linux-libc-headers changed. We're 
installing the linux-libc-headers for the build machine, so it seems to make 
sense to take control of the TARGET_CC_KERNEL_ARCH:

diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
index 32c3aa32ad..655439dd73 100644
--- a/meta/classes/nativesdk.bbclass
+++ b/meta/classes/nativesdk.bbclass
@@ -47,6 +47,7 @@ TARGET_VENDOR = "${SDK_VENDOR}"
  TARGET_OS = "${SDK_OS}"
  TARGET_PREFIX = "${SDK_PREFIX}"
  TARGET_CC_ARCH = "${SDK_CC_ARCH}"
+TARGET_CC_KERNEL_ARCH = "${SDK_CC_ARCH}"
  TARGET_LD_ARCH = "${SDK_LD_ARCH}"

Which leaves me with:

basehash changed from 42ed3480096bb7ea53b60dc876da0613 to 
38ea60bdac041673f2c491d7bbabe17c
Variable MACHINE value changed from 'qemuarm' to 'qemux86-64'
runtaskdeps changed:
linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk with 
hash cbb186fe33cd69cb0b06384e4d50a244
  changed to
linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk with 
hash 4d34d6981b79d0fccc768566bf2fa533
Hash for dependent task 
linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk 
changed from cbb186fe33cd69cb0b06384e4d50a244 to 
4d34d6981b79d0fccc768566bf2fa533

The configure and compile tasks for linux-libc-headers are both set to noexec. 
For the experiment, I added an empty do_configure task, with this result on the 
do_configure sigdata:

basehash changed from f13c2a2066fa48f0ccac35c085537c71 to 
bb13f2b1b1e7e376f3fb5a8ec888
Variable MACHINE value changed from 'qemux86-64' to 'qemuarm'

What to do? Why is the MACHINE variable included in the task signature (it is 
unset in run.do_configure)? Adding it to BB_HASHBASE_WHITELIST had no effect. 
What am I missing here?





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142569): 
https://lists.openembedded.org/g/openembedded-core/message/142569
Mute This Topic: https://lists.openembedded.org/mt/76855451/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] nativesdk-linux-libc-headers with two different MACHINEs

[Khem Raj]

I think MACHINE should not matter for nativesdk packages. Does
something like this work

diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
index 7f2692c51a..bb1dfd84c0 100644
--- a/meta/classes/nativesdk.bbclass
+++ b/meta/classes/nativesdk.bbclass
@@ -10,7 +10,7 @@ LIBCOVERRIDE = ":${NATIVESDKLIBC}"
 CLASSOVERRIDE = "class-nativesdk"
 MACHINEOVERRIDES = ""
 MACHINE_FEATURES = ""
-
+MACHINE = "${SDKMACHINE}"
 MULTILIBS = ""

 # we need consistent staging dir whether or not multilib is enabled

On Mon, Sep 14, 2020 at 5:13 PM Douglas via lists.openembedded.org
 wrote:
>
> For the experiment, I wanted to see whether I could achieve no task signature 
> change when building nativesdk-glibc for two different MACHINEs, but I found 
> that the do_install sigdata for nativesdk-linux-libc-headers changed. We're 
> installing the linux-libc-headers for the build machine, so it seems to make 
> sense to take control of the TARGET_CC_KERNEL_ARCH:
>
> diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
> index 32c3aa32ad..655439dd73 100644
> --- a/meta/classes/nativesdk.bbclass
> +++ b/meta/classes/nativesdk.bbclass
> @@ -47,6 +47,7 @@ TARGET_VENDOR = "${SDK_VENDOR}"
>  TARGET_OS = "${SDK_OS}"
>  TARGET_PREFIX = "${SDK_PREFIX}"
>  TARGET_CC_ARCH = "${SDK_CC_ARCH}"
> +TARGET_CC_KERNEL_ARCH = "${SDK_CC_ARCH}"
>  TARGET_LD_ARCH = "${SDK_LD_ARCH}"
>
> Which leaves me with:
>
> basehash changed from 42ed3480096bb7ea53b60dc876da0613 to 
> 38ea60bdac041673f2c491d7bbabe17c
> Variable MACHINE value changed from 'qemuarm' to 'qemux86-64'
> runtaskdeps changed:
> linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk 
> with hash cbb186fe33cd69cb0b06384e4d50a244
>  changed to
> linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk 
> with hash 4d34d6981b79d0fccc768566bf2fa533
> Hash for dependent task 
> linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk 
> changed from cbb186fe33cd69cb0b06384e4d50a244 to 
> 4d34d6981b79d0fccc768566bf2fa533
>
> The configure and compile tasks for linux-libc-headers are both set to 
> noexec. For the experiment, I added an empty do_configure task, with this 
> result on the do_configure sigdata:
>
> basehash changed from f13c2a2066fa48f0ccac35c085537c71 to 
> bb13f2b1b1e7e376f3fb5a8ec888
> Variable MACHINE value changed from 'qemux86-64' to 'qemuarm'
>
> What to do? Why is the MACHINE variable included in the task signature (it is 
> unset in run.do_configure)? Adding it to BB_HASHBASE_WHITELIST had no effect. 
> What am I missing here?
>
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142568): 
https://lists.openembedded.org/g/openembedded-core/message/142568
Mute This Topic: https://lists.openembedded.org/mt/76855451/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] nativesdk-linux-libc-headers with two different MACHINEs

[Douglas via lists.openembedded.org]

For the experiment, I wanted to see whether I could achieve no task 
signature change when building nativesdk-glibc for two different 
MACHINEs, but I found that the do_install sigdata for 
nativesdk-linux-libc-headers changed. We're installing the 
linux-libc-headers for the build machine, so it seems to make sense to 
take control of the TARGET_CC_KERNEL_ARCH:


   diff --git a/meta/classes/nativesdk.bbclass
   b/meta/classes/nativesdk.bbclass
   index 32c3aa32ad..655439dd73 100644
   --- a/meta/classes/nativesdk.bbclass
   +++ b/meta/classes/nativesdk.bbclass
   @@ -47,6 +47,7 @@ TARGET_VENDOR = "${SDK_VENDOR}"
 TARGET_OS = "${SDK_OS}"
 TARGET_PREFIX = "${SDK_PREFIX}"
 TARGET_CC_ARCH = "${SDK_CC_ARCH}"
   +TARGET_CC_KERNEL_ARCH = "${SDK_CC_ARCH}"
 TARGET_LD_ARCH = "${SDK_LD_ARCH}"

Which leaves me with:

   basehash changed from 42ed3480096bb7ea53b60dc876da0613 to
   38ea60bdac041673f2c491d7bbabe17c
   Variable MACHINE value changed from 'qemuarm' to 'qemux86-64'
   runtaskdeps changed:
   linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk
   with hash cbb186fe33cd69cb0b06384e4d50a244
 changed to
   linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk
   with hash 4d34d6981b79d0fccc768566bf2fa533
   Hash for dependent task
   linux-libc-headers/linux-libc-headers_4.18.bb.do_compile:virtual:nativesdk
   changed from cbb186fe33cd69cb0b06384e4d50a244 to
   4d34d6981b79d0fccc768566bf2fa533

The configure and compile tasks for linux-libc-headers are both set to 
noexec. For the experiment, I added an empty do_configure task, with 
this result on the do_configure sigdata:


   basehash changed from f13c2a2066fa48f0ccac35c085537c71 to
   bb13f2b1b1e7e376f3fb5a8ec888
   Variable MACHINE value changed from 'qemux86-64' to 'qemuarm'

What to do? Why is the MACHINE variable included in the task signature 
(it is unset in run.do_configure)? Adding it to BB_HASHBASE_WHITELIST 
had no effect. What am I missing here?


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142567): 
https://lists.openembedded.org/g/openembedded-core/message/142567
Mute This Topic: https://lists.openembedded.org/mt/76855451/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] insane: check for missing update-alternatives inherit

[Andrey Zhizhikin]

Add a package QA check to test if the recipe sets ALTERNATIVE variable
for any of its packages, and does not inherit update-alternatives class.
This causes the do_rootfs to fail since a proper alternative cannot be
created.

Signed-off-by: Andrey Zhizhikin 
---
 meta/classes/insane.bbclass | 9 +
 1 file changed, 9 insertions(+)

diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index c38720afdb..c6dff9659c 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -27,6 +27,7 @@ WARN_QA ?= " libdir xorg-driver-abi \
 infodir build-deps src-uri-bad symlink-to-sysroot multilib \
 invalid-packageconfig host-user-contaminated uppercase-pn 
patch-fuzz \
 mime mime-xdg unlisted-pkg-lics unhandled-features-check \
+missing-update-alternatives \
 "
 ERROR_QA ?= "dev-so debug-deps dev-deps debug-files arch pkgconfig la \
 perms dep-cmp pkgvarcheck perm-config perm-line perm-link \
@@ -989,6 +990,14 @@ def package_qa_check_unhandled_features_check(pn, d, 
messages):
 if var_set:
 package_qa_handle_error("unhandled-features-check", "%s: recipe 
doesn't inherit features_check" % pn, d)
 
+QARECIPETEST[missing-update-alternatives] = 
"package_qa_check_missing_update_alternatives"
+def package_qa_check_missing_update_alternatives(pn, d, messages):
+# Look at all packages and find out if any of those sets ALTERNATIVE 
variable
+# without inheriting update-alternatives class
+for pkg in (d.getVar('PACKAGES') or '').split():
+if d.getVar('ALTERNATIVE_%s' % pkg) and not 
bb.data.inherits_class('update-alternatives', d):
+package_qa_handle_error("missing-update-alternatives", "%s: recipe 
defines ALTERNATIVE_%s but doesn't inherit update-alternatives. This might fail 
during do_rootfs later!" % (pn, pkg), d)
+
 # The PACKAGE FUNC to scan each package
 python do_package_qa () {
 import subprocess
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142566): 
https://lists.openembedded.org/g/openembedded-core/message/142566
Mute This Topic: https://lists.openembedded.org/mt/76854816/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [meta-oe][PATCH 0/5] ARMv8 Tune reorg

[Jon Mason]

On Mon, Sep 14, 2020 at 11:32 AM Martin Jansa  wrote:
>
> > This reduces the number of files from 12 to 2 for ARMv8a, and that is 
> > excluding the 13 I am adding in this series that would otherwise be unique 
> > files.
>
> I don't have a strong opinion on this anymore, but is the number of the 
> include files the issue here?

This is the reason why I'm doing it.  Arm needs to support all the
cortex-a and cortex-m cores.  This would make the majority of the tune
files for only Arm cores.  We could move them into
meta/conf/machine/include/arm and not make the level down directory so
messy, but I think this is cleaner.

> I think the issue is the number of possible combinations and using the same 
> TUNE_PKGARCH for different tunes (unlike 32bit arm tune files which use 
> different). Bundling all these combinations in fewer include files doesn't 
> IMHO improve it.

The multitude of combinations and redundancy code entries makes it
very error prone.  By putting them all in the same file, it makes it
much easier to see the differences in entries and catch errors.
Longer term, I'd like to see something that removes the redundancies
completely, but it will take some work.

> With 32bit arm include files it was useful to be able to compare various 
> include files to check that they follow the same "structure" (or to add new 
> cortexa* one by copying existing and regex-replace).
>
> Also AVAILTUNES will now contain all possible tunes from given family (which 
> makes it almost useless for aarch64 tunes). So instead of BSP including .inc 
> file corresponding with the core used in the MACHINE and getting some "sane" 
> default DEFAULTTUNE (plus some other possible options listed in AVAILTUNES) 
> we now force every BSP to set more specific DEFAULTTUNE and then let user 
> figure out what other DEFAULTTUNEs might be compatible with it, e.g. when 
> someone is doing multi MACHINE builds and wants to share TUNE_PKGARCH between 
> them (to save build time, package feed size etc).

You can still set a generic default for all the machines of a given
family.  By including armv8a.inc, you still get 'DEFAULTTUNE ?=
"armv8a-crc"'.  This will allow for a generic for an entire family.
I'm not seeing the issue.

Thanks,
Jon


>
> Cheers,
>
> On Mon, Sep 14, 2020 at 5:14 PM Jon Mason  wrote:
>>
>> There is a large number of Arm Tune files located in
>> meta/conf/machine/include/, and to support the current and upcoming Arm
>> cores, more are needed.  Adding more files is simply going to make it
>> harder to find the relevant ones for an OE/YP developer/user.  Also,
>> there are problems with stale and erroneous configs (see my previous
>> series), which will only be exacerbated by having more files.
>>
>> I am proposing a reorganization of the existing tune files by including
>> them in the generic family include file.  For example, the
>> tune-cortexa55.inc would be moved into arch-armv8-2a.inc, and
>> tune-cortexa57.inc would be moved into arch-armv8a.inc.  This reduces
>> the number of files from 12 to 2 for ARMv8a, and that is excluding the
>> 13 I am adding in this series that would otherwise be unique files.
>>
>> To use, simply add
>> ...
>> DEFAULTTUNE ?= "neoversen1"
>> require conf/machine/include/arm/arch-armv8-2a.inc
>> ...
>>
>> Which is arguably what should be done anyway (instead of taking the
>> default of the tune include file).
>> See the qemuarm64 patch in the series for a working example.
>>
>> Of course, by removing the existing tune files, current users are going
>> to break.  A simple script can be written to use sed (or similar) to
>> replace the relevant parts for those users that would be affected (at
>> least for those that are in the layer index and update regularly).
>>
>> Thanks,
>> Jon
>>
>> ---
>>
>> Originally sent as a RFC in
>> https://lists.openembedded.org/g/openembedded-core/message/142324
>>
>> Given the generally positive feedback, sending as a patch series.
>> Keeping the "hard fail" of the file removal (per Richards comment in
>> https://lists.openembedded.org/g/openembedded-core/message/142356).
>> Only difference of note is the removal of the "arm64: set BASE_LIB to
>> lib64", as there needs to be more investigation (see
>> https://lists.openembedded.org/g/openembedded-core/message/142414).
>>
>>
>> Jon Mason (5):
>>   arch-armv8-2a.inc: Add Cortex-A55 tunings
>>   arch-armv8a.inc: Add existing tunings
>>   qemuarm64: change tuning
>>   arch-armv8a.inc: Add tunes for supported ARMv8a cores
>>   arch-armv8-2a.inc: Add tunes for supported ARMv8.2a cores
>>
>>  .../machine/include/arm/arch-armv8-2a.inc | 175 ++-
>>  meta/conf/machine/include/arm/arch-armv8a.inc | 206 +-
>>  meta/conf/machine/include/tune-cortexa32.inc  |  18 --
>>  meta/conf/machine/include/tune-cortexa35.inc  |  17 --
>>  meta/conf/machine/include/tune-cortexa53.inc  |  18 --
>>  meta/conf/machine/include/tune-cortexa55.inc  |  13 --
>>  .../include/tune-cortexa57-cortexa53.inc 

Re: [OE-core][PATCH] lttng-modules: backport patch to fix build for linux-5.4.62+

[Bruce Ashfield]

For my 5.4 and 5.8 and 5.9 builds of linux-yocto, I went ahead and
backported the 10 changes that are on the tip of the 2.12 branch,
since they are all bug fixes and support changes, they were safe to
grab.

My builds across the versions worked with that, and I sent that
variant in my series a few minutes ago.

Bruce

On Mon, Sep 14, 2020 at 4:46 PM Martin Jansa  wrote:
>
> Is this exact backport from lttng-modules repo?
>
> I came across this issue in 
> https://github.com/agherzan/meta-raspberrypi/pull/722
> and
> https://github.com/lttng/lttng-modules/commit/817e02f9e256b8f2cbb9e3125eb061757b83bd4a
> +
> https://github.com/lttng/lttng-modules/commit/b6af46d166c48c9e59600a60b5a2a7ead10f179a
> look a bit different than this one (and are more correct with fixed kernel 
> ranges as not every > 5.4.62 kernel had this change).
>
> On Mon, Sep 14, 2020 at 10:11 PM Bruce Ashfield  
> wrote:
>>
>> In my latest round of linux-yocto reference updates, I ran into these
>> same issues, but I needed to pull in more of the fixes on the 2.12
>> branch than just this to get things building against 5.8.9.
>>
>> I didn't need to tweak any of the patches for v5.4.64+ here.
>>
>> I have 10 backported patches and confirmed my 5.8.9 and 5.4.65 both
>> build with the changes.
>>
>> I can submit that patch along with my reference kernel bumps later today.
>>
>> Bruce
>>
>>
>> On Mon, Sep 14, 2020 at 3:52 AM Jens Rehsack  wrote:
>> >
>> > From: Jens Rehsack 
>> >
>> > Backport patch from lttng-modules/stable-2.12
>> > 87b2aff fix: writeback: Fix sync livelock due to b_dirty_time 
>> > processing (v5.9)
>> >
>> > with minor modfication to catch
>> > 6623c19042b6 writeback: Fix sync livelock due to b_dirty_time 
>> > processing
>> >
>> > from linux/stable-5.4 v5.4.62+
>> >
>> > Signed-off-by: Jens Rehsack 
>> > ---
>> >  ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 ++
>> >  .../lttng/lttng-modules_2.12.2.bb |   1 +
>> >  2 files changed, 118 insertions(+)
>> >  create mode 100644 
>> > meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>> >
>> > diff --git 
>> > a/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>> >  
>> > b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>> > new file mode 100644
>> > index 00..96a1c486ef
>> > --- /dev/null
>> > +++ 
>> > b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>> > @@ -0,0 +1,117 @@
>> > +From 87b2affc3eb06f3fb2d0923f18af37713eb6814b Mon Sep 17 00:00:00 2001
>> > +From: Michael Jeanson 
>> > +Date: Mon, 31 Aug 2020 14:16:01 -0400
>> > +Subject: [PATCH] fix: writeback: Fix sync livelock due to b_dirty_time
>> > + processing (v5.9)
>> > +
>> > +See upstream commit:
>> > +
>> > +  commit f9cae926f35e8230330f28c7b743ad088611a8de
>> > +  Author: Jan Kara 
>> > +  Date:   Fri May 29 16:08:58 2020 +0200
>> > +
>> > +writeback: Fix sync livelock due to b_dirty_time processing
>> > +
>> > +When we are processing writeback for sync(2), move_expired_inodes()
>> > +didn't set any inode expiry value (older_than_this). This can result 
>> > in
>> > +writeback never completing if there's steady stream of inodes added to
>> > +b_dirty_time list as writeback rechecks dirty lists after each 
>> > writeback
>> > +round whether there's more work to be done. Fix the problem by using
>> > +sync(2) start time is inode expiry value when processing b_dirty_time
>> > +list similarly as for ordinarily dirtied inodes. This requires some
>> > +refactoring of older_than_this handling which simplifies the code
>> > +noticeably as a bonus.
>> > +
>> > +Change-Id: I8b894b13ccc14d9b8983ee4c2810a927c319560b
>> > +Signed-off-by: Michael Jeanson 
>> > +Signed-off-by: Mathieu Desnoyers 
>> > +---
>> > + .../events/lttng-module/writeback.h   | 39 ---
>> > + 1 file changed, 26 insertions(+), 13 deletions(-)
>> > +
>> > +Upstream Status: Backport
>> > +
>> > +diff --git a/instrumentation/events/lttng-module/writeback.h 
>> > b/instrumentation/events/lttng-module/writeback.h
>> > +index ece67ad..e9018dd 100644
>> > +--- a/instrumentation/events/lttng-module/writeback.h
>> >  b/instrumentation/events/lttng-module/writeback.h
>> > +@@ -384,34 +384,48 @@ 
>> > LTTNG_TRACEPOINT_EVENT_WBC_INSTANCE(wbc_balance_dirty_wait, 
>> > writeback_wbc_balanc
>> > + #endif
>> > + LTTNG_TRACEPOINT_EVENT_WBC_INSTANCE(wbc_writepage, 
>> > writeback_wbc_writepage)
>> > +
>> > +-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,1,0))
>> > ++#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,9,0)) || (LINUX_VERSION_CODE 
>> > >= KERNEL_VERSION(5,4,62))
>> > ++LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
>> > ++  TP_PROTO(struct bdi_writeback *wb,
>> > ++   struct wb_writeback_work *work,
>> > ++   unsig

Re: [OE-core] [PATCH 0/6] linux-yocto: consolidated pull request

[Bruce Ashfield]

And also for the record, there's a 7th patch in my series that didn't
make it into my pull request (a configuration change)

Richard grabbed it from the branch.

If anyone is trying to manually apply the series, it will fail.

Bruce

On Mon, Sep 14, 2020 at 6:34 PM Bruce Ashfield via
lists.openembedded.org
 wrote:
>
> From: Bruce Ashfield 
>
> Richard,
>
> Here's the latest round of -stable updates for the active kernels in
> master.
>
> My first runs ran into the lttng-modules issues, and I've included a
> 10 patch backport of changes from lttng 2.12.x to address the various
> build issues I found against 5.4 and 5.8.
>
> There's a different lttng patch on the list, but it didn't address all
> of my build failures, so I generated this full backport change.
>
> Cheers,
>
> Bruce
>
> The following changes since commit 070d9b8f5e753e8928d2d7048e0c7bd9adbb3c29:
>
>   linux-yocto/config: netfilter: Enable nat for ipv4 and ipv6 (2020-09-14 
> 12:13:47 -0400)
>
> are available in the Git repository at:
>
>   git://git.yoctoproject.org/poky-contrib zedd/kernel
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
>   linux-yocto/5.8: update to v5.8.8
>   linux-yocto/5.4: update to v5.4.64
>   linux-yocto/config: configuration warning cleanup
>   linux-yocto/5.8: update to v5.8.9
>   linux-yocto/5.4: update to v5.4.65
>
> Jens Rehsack (1):
>   lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+
> builds
>
>  .../linux/linux-yocto-rt_5.4.bb   |   6 +-
>  .../linux/linux-yocto-rt_5.8.bb   |   6 +-
>  .../linux/linux-yocto-tiny_5.4.bb |   8 +-
>  .../linux/linux-yocto-tiny_5.8.bb |   8 +-
>  meta/recipes-kernel/linux/linux-yocto_5.4.bb  |  22 +-
>  meta/recipes-kernel/linux/linux-yocto_5.8.bb  |  22 +-
>  ...ndency-issue-when-building-in-tree-w.patch |  54 ++
>  ...ce.h-into-the-mmu-sub-directory-v5.9.patch |  41 +
>  ...Make-kvm_mmu_page-definition-and-acc.patch |  39 +
>  ...he-length-of-per-inode-prealloc-list.patch |  84 ++
>  ...e-via-a-block-bitmap-read-is-prefetc.patch |  63 ++
>  ...al-of-smp_-read_barrier_depends-v5.9.patch | 391 
>  ...teback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch |  59 ++
>  ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 +++
>  ...es-for-ext4_discard_preallocations-a.patch |  52 +
>  .../0010-Fix-system-call-filter-table.patch   | 918 ++
>  .../lttng/lttng-modules_2.12.2.bb |  12 +-
>  17 files changed, 1865 insertions(+), 37 deletions(-)
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0003-fix-KVM-x86-mmu-Make-kvm_mmu_page-definition-and-acc.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0004-fix-ext4-limit-the-length-of-per-inode-prealloc-list.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0005-fix-ext4-indicate-via-a-block-bitmap-read-is-prefetc.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0006-fix-removal-of-smp_-read_barrier_depends-v5.9.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0007-fix-writeback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0008-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0009-fix-version-ranges-for-ext4_discard_preallocations-a.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0010-Fix-system-call-filter-table.patch
>
> --
> 2.19.1
>
> 



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142563): 
https://lists.openembedded.org/g/openembedded-core/message/142563
Mute This Topic: https://lists.openembedded.org/mt/76853774/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds

[Bruce Ashfield]

I squashed the other lttng patch to create this, and it looks like the
author is messed up and some kind of strange encoding on one of the
embedded patches.

git send email complained on the way out.

Bruce

On Mon, Sep 14, 2020 at 6:34 PM  wrote:
>
> From: Jens Rehsack 
>
> Backporting the 10 patches since the lttng 2.12.2 release. We'll drop
> them once .3 is released, but for now, we need the fixes to build
> against the latest 5.4, 5.8 and 5.9 kernels.
>
> We also bump the devupstream SRCREV to pickup the same changes.
>
> Signed-off-by: Bruce Ashfield 
> ---
>  ...ndency-issue-when-building-in-tree-w.patch |  54 ++
>  ...ce.h-into-the-mmu-sub-directory-v5.9.patch |  41 +
>  ...Make-kvm_mmu_page-definition-and-acc.patch |  39 +
>  ...he-length-of-per-inode-prealloc-list.patch |  84 ++
>  ...e-via-a-block-bitmap-read-is-prefetc.patch |  63 ++
>  ...al-of-smp_-read_barrier_depends-v5.9.patch | 391 
>  ...teback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch |  59 ++
>  ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 +++
>  ...es-for-ext4_discard_preallocations-a.patch |  52 +
>  .../0010-Fix-system-call-filter-table.patch   | 918 ++
>  .../lttng/lttng-modules_2.12.2.bb |  12 +-
>  11 files changed, 1829 insertions(+), 1 deletion(-)
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0003-fix-KVM-x86-mmu-Make-kvm_mmu_page-definition-and-acc.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0004-fix-ext4-limit-the-length-of-per-inode-prealloc-list.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0005-fix-ext4-indicate-via-a-block-bitmap-read-is-prefetc.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0006-fix-removal-of-smp_-read_barrier_depends-v5.9.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0007-fix-writeback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0008-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0009-fix-version-ranges-for-ext4_discard_preallocations-a.patch
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0010-Fix-system-call-filter-table.patch
>
> diff --git 
> a/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
>  
> b/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
> new file mode 100644
> index 00..ae8bec45de
> --- /dev/null
> +++ 
> b/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
> @@ -0,0 +1,54 @@
> +From ff4d1d7e85be94ef43709cd698f0ec9a12f247d1 Mon Sep 17 00:00:00 2001
> +From: Beniamin Sandu 
> +Date: Thu, 13 Aug 2020 16:24:39 +0300
> +Subject: [PATCH 01/10] Kconfig: fix dependency issue when building in-tree
> + without CONFIG_FTRACE
> +
> +When building in-tree, one could disable CONFIG_FTRACE from kernel
> +config which will leave CONFIG_TRACEPOINTS selected by LTTNG modules,
> +but generate a lot of linker errors like below because it leaves out
> +other stuff, e.g.:
> +
> +trace.c:(.text+0xd86b): undefined reference to `trace_event_buffer_reserve'
> +ld: trace.c:(.text+0xd8de): undefined reference to 
> `trace_event_buffer_commit'
> +ld: trace.c:(.text+0xd926): undefined reference to `event_triggers_call'
> +ld: trace.c:(.text+0xd942): undefined reference to 
> `trace_event_ignore_this_pid'
> +ld: net/mac80211/trace.o: in function 
> `trace_event_raw_event_drv_tdls_cancel_channel_switch':
> +
> +It appears to be caused by the fact that TRACE_EVENT macros in the Linux
> +kernel depend on the Ftrace ring buffer as soon as CONFIG_TRACEPOINTS is
> +enabled.
> +
> +Steps to reproduce:
> +
> +- Get a clone of an upstream stable kernel and use scripts/built-in.sh on it
> +
> +- Configure a standard x86-64 build, enable built-in LTTNG but disable
> +  CONFIG_FTRACE from Kernel Hacking-->Tracers using menuconfig
> +
> +- Build will fail at linking stage
> +
> +Upstream-Status: Backport
> +
> +Signed-off-by: Beniamin Sandu 
> +Signed-off-by: Mathieu Desnoyers 
> +---
> + Kconfig | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/Kconfig b/Kconfig
> +index acdab73..10eccff 100644
> +--- a/Kconfig
>  b/Kconfig
> +@@ -2,7 +2,7 @@
> +
> + config LTTNG
> +   tristate "LTTng support"
> +-  select TRACEPOINTS
> ++  select TRACING
> +   help
> + LTTng is an open source tracing framework for Linux.
> +
> +--
> +2.19.1
> +
> diff --git 
> a/meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
>  

[OE-core] [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds

[Bruce Ashfield]

From: Jens Rehsack 

Backporting the 10 patches since the lttng 2.12.2 release. We'll drop
them once .3 is released, but for now, we need the fixes to build
against the latest 5.4, 5.8 and 5.9 kernels.

We also bump the devupstream SRCREV to pickup the same changes.

Signed-off-by: Bruce Ashfield 
---
 ...ndency-issue-when-building-in-tree-w.patch |  54 ++
 ...ce.h-into-the-mmu-sub-directory-v5.9.patch |  41 +
 ...Make-kvm_mmu_page-definition-and-acc.patch |  39 +
 ...he-length-of-per-inode-prealloc-list.patch |  84 ++
 ...e-via-a-block-bitmap-read-is-prefetc.patch |  63 ++
 ...al-of-smp_-read_barrier_depends-v5.9.patch | 391 
 ...teback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch |  59 ++
 ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 +++
 ...es-for-ext4_discard_preallocations-a.patch |  52 +
 .../0010-Fix-system-call-filter-table.patch   | 918 ++
 .../lttng/lttng-modules_2.12.2.bb |  12 +-
 11 files changed, 1829 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0003-fix-KVM-x86-mmu-Make-kvm_mmu_page-definition-and-acc.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0004-fix-ext4-limit-the-length-of-per-inode-prealloc-list.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0005-fix-ext4-indicate-via-a-block-bitmap-read-is-prefetc.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0006-fix-removal-of-smp_-read_barrier_depends-v5.9.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0007-fix-writeback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0008-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0009-fix-version-ranges-for-ext4_discard_preallocations-a.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0010-Fix-system-call-filter-table.patch

diff --git 
a/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
 
b/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
new file mode 100644
index 00..ae8bec45de
--- /dev/null
+++ 
b/meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
@@ -0,0 +1,54 @@
+From ff4d1d7e85be94ef43709cd698f0ec9a12f247d1 Mon Sep 17 00:00:00 2001
+From: Beniamin Sandu 
+Date: Thu, 13 Aug 2020 16:24:39 +0300
+Subject: [PATCH 01/10] Kconfig: fix dependency issue when building in-tree
+ without CONFIG_FTRACE
+
+When building in-tree, one could disable CONFIG_FTRACE from kernel
+config which will leave CONFIG_TRACEPOINTS selected by LTTNG modules,
+but generate a lot of linker errors like below because it leaves out
+other stuff, e.g.:
+
+trace.c:(.text+0xd86b): undefined reference to `trace_event_buffer_reserve'
+ld: trace.c:(.text+0xd8de): undefined reference to `trace_event_buffer_commit'
+ld: trace.c:(.text+0xd926): undefined reference to `event_triggers_call'
+ld: trace.c:(.text+0xd942): undefined reference to 
`trace_event_ignore_this_pid'
+ld: net/mac80211/trace.o: in function 
`trace_event_raw_event_drv_tdls_cancel_channel_switch':
+
+It appears to be caused by the fact that TRACE_EVENT macros in the Linux
+kernel depend on the Ftrace ring buffer as soon as CONFIG_TRACEPOINTS is
+enabled.
+
+Steps to reproduce:
+
+- Get a clone of an upstream stable kernel and use scripts/built-in.sh on it
+
+- Configure a standard x86-64 build, enable built-in LTTNG but disable
+  CONFIG_FTRACE from Kernel Hacking-->Tracers using menuconfig
+
+- Build will fail at linking stage
+
+Upstream-Status: Backport
+
+Signed-off-by: Beniamin Sandu 
+Signed-off-by: Mathieu Desnoyers 
+---
+ Kconfig | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/Kconfig b/Kconfig
+index acdab73..10eccff 100644
+--- a/Kconfig
 b/Kconfig
+@@ -2,7 +2,7 @@
+ 
+ config LTTNG
+   tristate "LTTng support"
+-  select TRACEPOINTS
++  select TRACING
+   help
+ LTTng is an open source tracing framework for Linux.
+ 
+-- 
+2.19.1
+
diff --git 
a/meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
 
b/meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
new file mode 100644
index 00..fab673b854
--- /dev/null
+++ 
b/meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
@@ -0,0 +1,41 @@
+From e10ab43dd0e425df5bc0ac763447664ed075ba05 Mon Sep 17 00:00:00 2001
+From: Michael Jeanson 
+Date: Mon, 10 Aug 2020 11:22:05 -0400
+Subject: [PATCH 02/10] fix: Move mmut

[OE-core] [PATCH 3/6] linux-yocto/config: configuration warning cleanup

[Bruce Ashfield]

From: Bruce Ashfield 

Integrating the following commit(s) to linux-yocto/.:

7d52eb95f6d ti-am335x: Clean up useless and badly formatted fragments
5fd04e4da78 features/nf_tables: remove duplicate entry

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_5.8.bb  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
index e3a483fbe4..ec8060c945 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_meta ?= "f79c81e7a7d995f0ddb3114000555b25f4649373"
+SRCREV_meta ?= "7d52eb95f6d0899e764f58fec27acf1b477e31c7"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.8;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
index 26f34289fe..2461254fb4 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
@@ -17,7 +17,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine_qemuarm ?= "14a8e34bdcc80797e7b3355241625f13d3396ed8"
 SRCREV_machine ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_meta ?= "f79c81e7a7d995f0ddb3114000555b25f4649373"
+SRCREV_meta ?= "7d52eb95f6d0899e764f58fec27acf1b477e31c7"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.8.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.8.bb
index c232614c21..a0a55ac569 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.8.bb
@@ -21,7 +21,7 @@ SRCREV_machine_qemux86 ?= 
"542471b271e827808692640e58f8771ff6bc67dc"
 SRCREV_machine_qemux86-64 ?= "542471b271e827808692640e58f8771ff6bc67dc"
 SRCREV_machine_qemumips64 ?= "18d9d696a89282b3c7b9d3a0b4bbe9d5500e9eb3"
 SRCREV_machine ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_meta ?= "f79c81e7a7d995f0ddb3114000555b25f4649373"
+SRCREV_meta ?= "7d52eb95f6d0899e764f58fec27acf1b477e31c7"
 
 # remap qemuarm to qemuarma15 for the 5.8 kernel
 # KMACHINE_qemuarm ?= "qemuarma15"
-- 
2.19.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142558): 
https://lists.openembedded.org/g/openembedded-core/message/142558
Mute This Topic: https://lists.openembedded.org/mt/76853778/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 1/6] linux-yocto/5.8: update to v5.8.8

[Bruce Ashfield]

From: Bruce Ashfield 

Updating linux-yocto/5.8 to the latest korg -stable release that comprises
the following commits:

4f447bf95fdc Linux 5.8.8
830b08e696f7 net: usb: Fix uninit-was-stored issue in asix_read_phy_addr()
548c1175051d cfg80211: regulatory: reject invalid hints
9206b03e7fc9 mm/khugepaged.c: fix khugepaged's request size in collapse_file
951e290ad85b mm/hugetlb: fix a race between hugetlb sysctl handlers
e2d4e423205e mm/hugetlb: try preferred node first when alloc gigantic page 
from cma
3fd08f78f47a mm/migrate: fixup setting UFFD_WP flag
658e93f1c318 checkpatch: fix the usage of capture group ( ... )
d3498d5e8775 sdhci: tegra: Add missing TMCLK for data timeout
55eb0f42f465 kconfig: streamline_config.pl: check defined(ENV variable) 
before using it
8c4c56846892 perf record: Correct the help info of option "--no-bpf-event"
bf8fe7b755c2 io_uring: no read/write-retry on -EAGAIN error and O_NONBLOCK 
marked file
a8bf40a7538f mm/rmap: fixup copying of soft dirty and uffd ptes
9b4a9e89f6e8 mm: madvise: fix vma user-after-free
98650804fa53 mm: track page table modifications in __apply_to_page_range()
3eba981cffc9 mm: slub: fix conversion of freelist_corrupted()
4469ea5972ab dm thin metadata: Fix use-after-free in dm_bm_set_read_only
b3c76fdbb119 dm thin metadata: Avoid returning cmd->bm wild pointer on error
d02a33a24825 dm cache metadata: Avoid returning cmd->bm wild pointer on 
error
0a495d145f59 dm crypt: Initialize crypto wait structures
372236a01bc5 dm integrity: fix error reporting in bitmap mode after creation
2c8ee4951f11 dm mpath: fix racey management of PG initialization
cc06bdfc211b dm writecache: handle DAX to partitions on persistent memory 
correctly
67ba86179fc6 drm/amdgpu: Specify get_argument function for ci_smu_funcs
dd8a223d0f58 drm/amd/pm: avoid false alarm due to confusing 
softwareshutdowntemp setting
696f8cfee025 drm/i915: Fix sha_text population code
1693c125c0a9 dmaengine: dw-edma: Fix scatter-gather address calculation
3c761332597d blk-stat: make q->stats->lock irqsafe
70d22582c3eb blk-iocost: ioc_pd_free() shouldn't assume irq disabled
57fd9f8eb603 mips/oprofile: Fix fallthrough placement
dea6f05d372a libata: implement ATA_HORKAGE_MAX_TRIM_128M and apply to 
Sandisks
3264d781e1ad s390: fix GENERIC_LOCKBREAK dependency typo in Kconfig
e37bc36aaff3 io_uring: fix removing the wrong file in 
__io_sqe_files_update()
329c9ffc81cf io_uring: set table->files[i] to NULL when 
io_sqe_file_register failed
a7a42c1e5023 block: ensure bdi->io_pages is always initialized
b7df98a8b7b8 block: allow for_each_bvec to support zero len bvec
2221f41d3fb3 affs: fix basic permission bits to actually work
9af0c46a7612 media: rc: uevent sysfs file races with rc_unregister_device()
bff924ee40ae media: rc: do not access device via sysfs after 
rc_unregister_device()
91994b8489a3 mmc: sdhci-pci: Fix SDHCI_RESET_ALL for CQHCI for Intel 
GLK-based controllers
88df22892d14 mmc: dt-bindings: Add resets/reset-names for Mediatek MMC 
bindings
01263d02f5da mmc: mediatek: add optional module reset property
f8916b54514e arm64: dts: mt7622: add reset node for mmc device
ab90e0d7a985 ALSA: hda/realtek - Improved routing for Thinkpad X1 7th/8th 
Gen
3695decb7771 ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion 
NT950XCJ-X716A
c1e0aff25b1b ALSA; firewire-tascam: exclude Tascam FE-8 from detection
8e83bd51016a ALSA: hda - Fix silent audio output and corrupted input on MSI 
X570-A PRO
48510be50e87 ALSA: firewire-digi00x: exclude Avid Adrenaline from detection
7554ad2ffdad ALSA: hda/hdmi: always check pin power status in i915 pin fixup
db5d1d51bef1 ALSA: pcm: oss: Remove superfluous WARN_ON() for mulaw sanity 
check
dfcfc358e366 ALSA: usb-audio: Add implicit feedback quirk for UR22C
3284ababd0c4 ALSA: usb-audio: Add basic capture support for Pioneer DJ 
DJM-250MK2
2c9ba98fec4d ALSA: ca0106: fix error code handling
9aa4e2c3da17 Revert "ALSA: hda: Add support for Loongson 7A1000 controller"
df7a51020021 x86/mm/32: Bring back vmalloc faulting on x86_32
98f0b4072c94 Bluetooth: Return NOTIFY_DONE for hci_suspend_notifier
434ed4233877 btrfs: tree-checker: fix the error message for transid error
6b09009a2eae btrfs: block-group: fix free-space bitmap threshold
6d12fbd0c4b7 btrfs: set the lockdep class for log tree extent buffers
7ad3d8ad569c btrfs: set the correct lockdep class for new nodes
42a2fbd05773 btrfs: allocate scrub workqueues outside of locks
26cf893236fd btrfs: fix potential deadlock in the search ioctl
5e85cae6cd52 btrfs: drop path before adding new uuid tree entry
be69bb028264 arc: fix memory initialization for systems with two memory 
banks
ec96b4b7514c ARC: perf: don't bail setup if pct irq missing in device-tree
7d5026dcd362 xfs: don't upd

[OE-core] [PATCH 5/6] linux-yocto/5.4: update to v5.4.65

[Bruce Ashfield]

From: Bruce Ashfield 

Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:

6c3d34dea2fc Linux 5.4.65
ddb279d64b72 net: disable netpoll on fresh napis
09c45065257b tipc: fix shutdown() of connectionless socket
b95eb482c288 taprio: Fix using wrong queues in gate mask
20f8c874789a sctp: not disable bh in the whole sctp_get_port_local()
8b61bb0b2d57 net: usb: dm9601: Add USB ID of Keenetic Plus DSL
346fefa82325 netlabel: fix problems with mapping removal
3f73dbf94f8f ipv6: Fix sysctl max for fib_multipath_hash_policy
263e463358d3 ipv4: Silence suspicious RCU usage warning

Signed-off-by: Bruce Ashfield 
---
 .../linux/linux-yocto-rt_5.4.bb   |  6 ++---
 .../linux/linux-yocto-tiny_5.4.bb |  8 +++
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +--
 3 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 97cb7d934f..73876bb99e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "b170a5953260ea7d7bdfcf223fb92d138eb7db67"
-SRCREV_meta ?= "34b6e8caf82c411655d33e0eeff6700a8de1f6fc"
+SRCREV_machine ?= "1d9e25c4f35155580cef313ff2a76de545124a1d"
+SRCREV_meta ?= "0d860e075788a92601dff3eb9b615ee41e465040"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "5.4.64"
+LINUX_VERSION ?= "5.4.65"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index 7d836593c9..853fc93694 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "5.4.64"
+LINUX_VERSION ?= "5.4.65"
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 
 DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine_qemuarm ?= "3bd01ef1ebb9b2a9bbae3c35eb9d640cd1ab9da7"
-SRCREV_machine ?= "86d9bf1c575ada30e515b9337a0ba3fe07986091"
-SRCREV_meta ?= "34b6e8caf82c411655d33e0eeff6700a8de1f6fc"
+SRCREV_machine_qemuarm ?= "bb77791bc00cfa70211dd238d312b4db950c0808"
+SRCREV_machine ?= "406008bf3232dfc9e63b6e7bf745ca883c45041e"
+SRCREV_meta ?= "0d860e075788a92601dff3eb9b615ee41e465040"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 26778a67a3..fe93691961 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86  ?= "v5.4/standard/base"
 KBRANCH_qemux86-64 ?= "v5.4/standard/base"
 KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "33ab5549b39d7bbfc067f13527bfa817250c69a3"
-SRCREV_machine_qemuarm64 ?= "86d9bf1c575ada30e515b9337a0ba3fe07986091"
-SRCREV_machine_qemumips ?= "7954ad760bd317039a9ad44300a8bf1a34107fc8"
-SRCREV_machine_qemuppc ?= "86d9bf1c575ada30e515b9337a0ba3fe07986091"
-SRCREV_machine_qemuriscv64 ?= "86d9bf1c575ada30e515b9337a0ba3fe07986091"
-SRCREV_machine_qemux86 ?= "86d9bf1c575ada30e515b9337a0ba3fe07986091"
-SRCREV_machine_qemux86-64 ?= "86d9bf1c575ada30e515b9337a0ba3fe07986091"
-SRCREV_machine_qemumips64 ?= "91fb319534f5206619aa04556dbf32d49afa1080"
-SRCREV_machine ?= "86d9bf1c575ada30e515b9337a0ba3fe07986091"
-SRCREV_meta ?= "34b6e8caf82c411655d33e0eeff6700a8de1f6fc"
+SRCREV_machine_qemuarm ?= "894e63d3256613faa39931a6ae505cfd196df067"
+SRCREV_machine_qemuarm64 ?= "406008bf3232dfc9e63b6e7bf745ca883c45041e"
+SRCREV_machine_qemumips ?= "aa13fdb2c5f8c4e4e432bfee6df9c8f76ec8ac70"
+SRCREV_machine_qemuppc ?= "406008bf3232dfc9e63b6e7bf745ca883c45041e"
+SRCREV_machine_qemuriscv64 ?= "406008bf3232dfc9e63b6e7bf745ca883c45041e"
+SRCREV_machine_qemux86 ?= "406008bf3232dfc9e63b6e7bf745ca883c45041e"
+SRCREV_machine_qemux86-64 ?= "406008bf3232dfc9e63b6e7bf745ca883c45041e"
+SRCREV_machine_qemumips64 ?= "4fb21d604fc54db63221ea28ab90622c29d74202"
+SRCREV_machine ?= "406008bf3232dfc9e63b6e7bf745ca883c45041e"
+SRCREV_meta ?= "0d860e075788a92601dff3eb9b615ee41e465040"
 
 # remap qemuarm to qemuarma15 for the 5.4 kernel
 # KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;name=machine;bra

[OE-core] [PATCH 0/6] linux-yocto: consolidated pull request

[Bruce Ashfield]

From: Bruce Ashfield 

Richard,

Here's the latest round of -stable updates for the active kernels in
master.

My first runs ran into the lttng-modules issues, and I've included a
10 patch backport of changes from lttng 2.12.x to address the various
build issues I found against 5.4 and 5.8.

There's a different lttng patch on the list, but it didn't address all
of my build failures, so I generated this full backport change.

Cheers,

Bruce

The following changes since commit 070d9b8f5e753e8928d2d7048e0c7bd9adbb3c29:

  linux-yocto/config: netfilter: Enable nat for ipv4 and ipv6 (2020-09-14 
12:13:47 -0400)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  linux-yocto/5.8: update to v5.8.8
  linux-yocto/5.4: update to v5.4.64
  linux-yocto/config: configuration warning cleanup
  linux-yocto/5.8: update to v5.8.9
  linux-yocto/5.4: update to v5.4.65

Jens Rehsack (1):
  lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+
builds

 .../linux/linux-yocto-rt_5.4.bb   |   6 +-
 .../linux/linux-yocto-rt_5.8.bb   |   6 +-
 .../linux/linux-yocto-tiny_5.4.bb |   8 +-
 .../linux/linux-yocto-tiny_5.8.bb |   8 +-
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  |  22 +-
 meta/recipes-kernel/linux/linux-yocto_5.8.bb  |  22 +-
 ...ndency-issue-when-building-in-tree-w.patch |  54 ++
 ...ce.h-into-the-mmu-sub-directory-v5.9.patch |  41 +
 ...Make-kvm_mmu_page-definition-and-acc.patch |  39 +
 ...he-length-of-per-inode-prealloc-list.patch |  84 ++
 ...e-via-a-block-bitmap-read-is-prefetc.patch |  63 ++
 ...al-of-smp_-read_barrier_depends-v5.9.patch | 391 
 ...teback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch |  59 ++
 ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 +++
 ...es-for-ext4_discard_preallocations-a.patch |  52 +
 .../0010-Fix-system-call-filter-table.patch   | 918 ++
 .../lttng/lttng-modules_2.12.2.bb |  12 +-
 17 files changed, 1865 insertions(+), 37 deletions(-)
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0003-fix-KVM-x86-mmu-Make-kvm_mmu_page-definition-and-acc.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0004-fix-ext4-limit-the-length-of-per-inode-prealloc-list.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0005-fix-ext4-indicate-via-a-block-bitmap-read-is-prefetc.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0006-fix-removal-of-smp_-read_barrier_depends-v5.9.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0007-fix-writeback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0008-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0009-fix-version-ranges-for-ext4_discard_preallocations-a.patch
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0010-Fix-system-call-filter-table.patch

-- 
2.19.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142555): 
https://lists.openembedded.org/g/openembedded-core/message/142555
Mute This Topic: https://lists.openembedded.org/mt/76853774/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 2/6] linux-yocto/5.4: update to v5.4.64

[Bruce Ashfield]

From: Bruce Ashfield 

Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:

6ffabce36fc8 Linux 5.4.64
beaf13ed8e97 net: usb: Fix uninit-was-stored issue in asix_read_phy_addr()
58c3e86d42d2 cfg80211: regulatory: reject invalid hints
08eeec445297 mm/khugepaged.c: fix khugepaged's request size in collapse_file
af7786b20c71 mm/hugetlb: fix a race between hugetlb sysctl handlers
f2cd86225c89 checkpatch: fix the usage of capture group ( ... )
59ac5bfa82bc sdhci: tegra: Add missing TMCLK for data timeout
e915b3b63dfd perf record: Correct the help info of option "--no-bpf-event"
894a6f0be372 vfio/pci: Fix SR-IOV VF handling with MMIO blocking
f4fa8d937edf mm: madvise: fix vma user-after-free
87fb7b0c5266 mm: slub: fix conversion of freelist_corrupted()
291144f1114d dm thin metadata: Fix use-after-free in dm_bm_set_read_only
cfe85a4a8552 dm thin metadata: Avoid returning cmd->bm wild pointer on error
392a6afcbf19 dm cache metadata: Avoid returning cmd->bm wild pointer on 
error
9dd74db0bfd1 dm crypt: Initialize crypto wait structures
e6ddb1d45c51 dm integrity: fix error reporting in bitmap mode after creation
b30f628beec9 dm mpath: fix racey management of PG initialization
226fb99eb59d dm writecache: handle DAX to partitions on persistent memory 
correctly
6fb192c06a14 drm/amd/pm: avoid false alarm due to confusing 
softwareshutdowntemp setting
f84804af09c7 dmaengine: dw-edma: Fix scatter-gather address calculation
9f4ab0172e6c blk-iocost: ioc_pd_free() shouldn't assume irq disabled
f7880745e91b libata: implement ATA_HORKAGE_MAX_TRIM_128M and apply to 
Sandisks
5f5f27228195 block: ensure bdi->io_pages is always initialized
84c041c12442 block: allow for_each_bvec to support zero len bvec
b6e4827c04b0 affs: fix basic permission bits to actually work
2d89e44dc932 media: rc: uevent sysfs file races with rc_unregister_device()
5925179bbc64 media: rc: do not access device via sysfs after 
rc_unregister_device()
3d77c12f3040 mmc: sdhci-pci: Fix SDHCI_RESET_ALL for CQHCI for Intel 
GLK-based controllers
ed48704c36a8 mmc: cqhci: Add cqhci_deactivate()
a69047c01eb4 mmc: dt-bindings: Add resets/reset-names for Mediatek MMC 
bindings
5876ee035ba6 mmc: mediatek: add optional module reset property
2816ccd07145 arm64: dts: mt7622: add reset node for mmc device
d074d9d52fe0 ALSA: hda/realtek - Improved routing for Thinkpad X1 7th/8th 
Gen
7de2f56ef51a ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion 
NT950XCJ-X716A
a253fe35666d ALSA; firewire-tascam: exclude Tascam FE-8 from detection
982505615063 ALSA: hda - Fix silent audio output and corrupted input on MSI 
X570-A PRO
cebaed033037 ALSA: firewire-digi00x: exclude Avid Adrenaline from detection
4fa06a43bf9f ALSA: hda/hdmi: always check pin power status in i915 pin fixup
2ebb83a259a8 ALSA: pcm: oss: Remove superfluous WARN_ON() for mulaw sanity 
check
79124b1b912c ALSA: usb-audio: Add implicit feedback quirk for UR22C
a3b94af5117b ALSA: ca0106: fix error code handling
156dd7c73a9b Revert "ALSA: hda: Add support for Loongson 7A1000 controller"
62db427bf8ca Revert "net: dsa: microchip: set the correct number of ports"
4254a4f7988c btrfs: fix potential deadlock in the search ioctl
de53545e8d4c net: core: use listified Rx for GRO_NORMAL in 
napi_gro_receive()
df0c47585cea btrfs: tree-checker: fix the error message for transid error
650275310f3b btrfs: set the lockdep class for log tree extent buffers
7e0ffb0d9d9f btrfs: set the correct lockdep class for new nodes
c37cc199da2b btrfs: allocate scrub workqueues outside of locks
eb29635ba68a btrfs: drop path before adding new uuid tree entry
20b591fd00c0 ARC: perf: don't bail setup if pct irq missing in device-tree
ce690fa1d5d0 xfs: don't update mtime on COW faults
12cd8fccc9ed ext2: don't update mtime on COW faults
cc6c4d81d6ad tracing/kprobes, x86/ptrace: Fix regs argument order for i386
036a857bb57d iommu/vt-d: Handle 36bit addressing for x86-32
8f747b0149c5 vfio-pci: Invalidate mmaps and block MMIO access on disabled 
memory
b0f5096b281a vfio-pci: Fault mmaps to enable vma tracking
270c35d0723a vfio/type1: Support faulting PFNMAP vmas
5629bb21ce20 include/linux/log2.h: add missing () around n in 
roundup_pow_of_two()
bc846b58fe5c net/packet: fix overflow in tpacket_rcv
e3d109c3484e iommu/amd: Restore IRTE.RemapEn bit after programming IRTE
7ce6bc1b549e thermal: qcom-spmi-temp-alarm: Don't suppress negative temp
f5b3bd38ae91 thermal: ti-soc-thermal: Fix bogus thermal shutdowns for 
omap4430
0c21f1bcafc1 iommu/vt-d: Serialize IOMMU GCMD register modifications
920d9ffcd481 x86, fakenuma: Fix invalid starting node ID
1a7e03867a37 tg3: Fix soft lockup when tg3_reset_task() fails.
b0c40f8a7a0e perf jevents: Fix suspicious c

[OE-core] [PATCH 4/6] linux-yocto/5.8: update to v5.8.9

[Bruce Ashfield]

From: Bruce Ashfield 

Updating linux-yocto/5.8 to the latest korg -stable release that comprises
the following commits:

f82f36b2fb1d Linux 5.8.9
cdba995d2f19 mptcp: free acked data before waiting for more memory
655e1af6aecd net: disable netpoll on fresh napis
6f0e276cda3e tipc: fix using smp_processor_id() in preemptible
aae250a26893 tipc: fix shutdown() of connectionless socket
44c3fca3de64 taprio: Fix using wrong queues in gate mask
db16256c95ac sctp: not disable bh in the whole sctp_get_port_local()
05a8237c08f0 net: usb: dm9601: Add USB ID of Keenetic Plus DSL
6540bd18bf2f netlabel: fix problems with mapping removal
089097476c4c ipv6: Fix sysctl max for fib_multipath_hash_policy
d68c3397de48 ipv4: Silence suspicious RCU usage warning
bd15d2192261 RDMA/cma: Execute rdma_cm destruction from a handler properly
d4794085738d RDMA/cma: Remove unneeded locking for req paths
c2064ac30331 RDMA/cma: Using the standard locking pattern when delivering 
the removal event
5a0c4cbd099b RDMA/cma: Simplify DEVICE_REMOVAL for internal_id
87d8175e9c3d io_uring: fix linked deferred ->files cancellation
f5fea75f4ea4 io_uring: fix cancel of deferred reqs with ->files

Signed-off-by: Bruce Ashfield 
---
 .../linux/linux-yocto-rt_5.8.bb   |  6 ++---
 .../linux/linux-yocto-tiny_5.8.bb |  8 +++
 meta/recipes-kernel/linux/linux-yocto_5.8.bb  | 22 +--
 3 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
index ec8060c945..d29c5985cd 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
@@ -11,13 +11,13 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_meta ?= "7d52eb95f6d0899e764f58fec27acf1b477e31c7"
+SRCREV_machine ?= "31fafe701e2adec65d2b2a74a3e592a358915c67"
+SRCREV_meta ?= "a933cb2f91915dceb138775c3878212e228d3eff"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.8;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "5.8.8"
+LINUX_VERSION ?= "5.8.9"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
index 2461254fb4..d32e5d372b 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "5.8.8"
+LINUX_VERSION ?= "5.8.9"
 LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
 
 DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine_qemuarm ?= "14a8e34bdcc80797e7b3355241625f13d3396ed8"
-SRCREV_machine ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_meta ?= "7d52eb95f6d0899e764f58fec27acf1b477e31c7"
+SRCREV_machine_qemuarm ?= "830cb9af40e856615b7a435a4fac57b748ba56d6"
+SRCREV_machine ?= "31fafe701e2adec65d2b2a74a3e592a358915c67"
+SRCREV_meta ?= "a933cb2f91915dceb138775c3878212e228d3eff"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.8.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.8.bb
index a0a55ac569..9ff1d5da80 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.8.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86  ?= "v5.8/standard/base"
 KBRANCH_qemux86-64 ?= "v5.8/standard/base"
 KBRANCH_qemumips64 ?= "v5.8/standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "0e9ceeb178a44d70be22088205d9e6b52f9feb3f"
-SRCREV_machine_qemuarm64 ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_machine_qemumips ?= "68ccca78b4c670e7db82ee7d5aa289abb4910ebe"
-SRCREV_machine_qemuppc ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_machine_qemuriscv64 ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_machine_qemux86 ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_machine_qemux86-64 ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_machine_qemumips64 ?= "18d9d696a89282b3c7b9d3a0b4bbe9d5500e9eb3"
-SRCREV_machine ?= "542471b271e827808692640e58f8771ff6bc67dc"
-SRCREV_meta ?= "7d52eb95f6d0899e764f58fec27acf1b477e31c7"
+SRCREV_machine_qemuarm ?= "d351bf87c9c0e96a1f27f87f16d298bc4470e0b5"
+SRCREV_machine_qemuarm64 ?= "31fafe701e2adec65d2b2a74a3e592a358915c67"
+SRCREV_machine_qemumips ?= "93d29a70890b19fb5482ebcab5f3a49301851daf"
+SRCREV_machine_qemuppc ?= "31fafe701e2adec65d2b2a74a3e592a358915c67"
+SRCREV_mac

Re: [OE-core] [PATCH] core-image-sato: qemumips use 512 mem

[Richard Purdie]

On Mon, 2020-09-14 at 10:27 -0700, Khem Raj wrote:
> 
> On 9/14/20 12:13 AM, Richard Purdie wrote:
> > On Sat, 2020-09-12 at 20:59 -0700, akuster wrote:
> > > From: Armin Kuster 
> > > 
> > > Fixes:
> > > 
> > > WARNING: core-image-sato-sdk-1.0-r0 do_testimage: Couldn't login
> > > into
> > > serial console as root using blank password
> > > WARNING: core-image-sato-sdk-1.0-r0 do_testimage: The output:
> > > root
> > > <<< run_serial(): command timed out after 60 seconds without
> > > output
> > > 
> > > In another run, this error was seen:
> > > 
> > > Failed to reload daemon: Refusing to reload, not enough space
> > > available on /run/systemd. Currently, 14.3M are free, but a
> > > safety
> > > buffer of 16.0M is enforced.
> > > 
> > > With updates to systemd and Qemu we should revert: 499a31cf06
> > > core-
> > > image-sato: don't use 512MB in qemumips
> > > 
> > > Signed-off-by: Armin Kuster  
> > > ---
> > >   meta/recipes-sato/images/core-image-sato.bb | 1 -
> > >   1 file changed, 1 deletion(-)
> > > 
> > > diff --git a/meta/recipes-sato/images/core-image-sato.bb
> > > b/meta/recipes-sato/images/core-image-sato.bb
> > > index 673106eb6d..878e0eaa8d 100644
> > > --- a/meta/recipes-sato/images/core-image-sato.bb
> > > +++ b/meta/recipes-sato/images/core-image-sato.bb
> > > @@ -12,4 +12,3 @@ TOOLCHAIN_HOST_TASK_append = " nativesdk-
> > > intltool
> > > nativesdk-glib-2.0"
> > >   TOOLCHAIN_HOST_TASK_remove_task-populate-sdk-ext = " nativesdk-
> > > intltool nativesdk-glib-2.0"
> > >   
> > >   QB_MEM = '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m
> > > 512", "-m 256", d)}'
> > > -QB_MEM_qemumips = "-m 256"
> > 
> > We have now seen:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/2452
> > 
> > with this applied, not sure if its related. We have seen this kind
> > of
> > network dropout elsewhere but we don't seem to have good debug when
> > it
> > happens.
> > 
> 
> I wonder if ssh daemon is dead in this case. I also see its invoking 
> compilers on target( kernelmodule case), are they usign -jX during
> make 
> ?, 512M might not be enough to run parallel compiles

Shouldn't be using -j for these tests. I think we need better debugging
using the serial console when these failures occur...

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142554): 
https://lists.openembedded.org/g/openembedded-core/message/142554
Mute This Topic: https://lists.openembedded.org/mt/76814331/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 7/8] bind: Add 9.16.x

[Andrey Zhizhikin]

On Mon, Sep 14, 2020 at 9:04 PM Khem Raj  wrote:
>
>
>
> On 9/14/20 10:55 AM, Andrey Zhizhikin wrote:
> > Gentle ping here regarding this issue.
> >
> > Is thre anyone else experiencing this with IPK packages?
>
> Alright thanks for being persist it has paid off :) I have taken a look
> at it and sent a fix to ml

Thanks a lot! :)

Actually, it was such an obvious thing that I managed to overlook - it
didn't cross my eye that update-alternative inheritance was missing in
the first place! :)

The mystery that still remains however: why did it work for RPM
package types? Is there a check that is missing somewhere, or
update-alternatives are inherited implicitly?

I guess if not because of the fact that it did work out for RPM in the
first place - those kinds of obvious failures could be avoided at the
very start.

>
>
> >
> > On Thu, Sep 10, 2020 at 9:12 AM Andrey Zhizhikin  wrote:
> >>
> >> On Thu, Sep 10, 2020 at 1:53 AM Khem Raj  wrote:
> >>>
> >>>
> >>>
> >>> On 9/7/20 2:17 PM, Andrey Zhizhikin wrote:
>  On Mon, Sep 7, 2020 at 5:28 PM akuster808  wrote:
> >
> >
> >
> > On 9/4/20 1:39 AM, Andrey Zhizhikin wrote:
> >> Hello Armin,
> >>
> >> On Tue, Sep 1, 2020 at 5:23 PM akuster  wrote:
> >>> Removed obsolete packageconfig options
> >>>
> >>> License change to MPL-2.0
> >>> https://gitlab.isc.org/isc-projects/bind9/blob/master/LICENSE
> >>>
> >>> Refreshed:
> >>> bind-ensure-searching-for-json-headers-searches-sysr.patch
> >>> 0001-named-lwresd-V-and-start-log-hide-build-options.patch
> >>> bind-ensure-searching-for-json-headers-searches-sysr.patch
> >>>
> >>> Drop obsolete patch: 
> >>> 0001-configure.in-remove-useless-L-use_openssl-lib.patch
> >>>
> >>> Signed-off-by: Armin Kuster 
> >>> ---
> >>>   ...1-avoid-start-failure-with-bind-user.patch |  27 ++
> >>>   ...d-V-and-start-log-hide-build-options.patch |  35 ++
> >>>   ...ching-for-json-headers-searches-sysr.patch |  47 +++
> >>>   .../bind/bind-9.16.5/bind9|   2 +
> >>>   .../bind/bind-9.16.5/conf.patch   | 330 
> >>> ++
> >>>   .../bind/bind-9.16.5/generate-rndc-key.sh |   8 +
> >>>   ...t.d-add-support-for-read-only-rootfs.patch |  65 
> >>>   .../make-etc-initd-bind-stop-work.patch   |  42 +++
> >>>   .../bind/bind-9.16.5/named.service|  22 ++
> >>>   meta/recipes-connectivity/bind/bind_9.16.5.bb | 125 +++
> >>>   10 files changed, 703 insertions(+)
> >>>   create mode 100644 
> >>> meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
> >>>   create mode 100644 
> >>> meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
> >>>   create mode 100644 
> >>> meta/recipes-connectivity/bind/bind-9.16.5/bind-ensure-searching-for-json-headers-searches-sysr.patch
> >>>   create mode 100644 meta/recipes-connectivity/bind/bind-9.16.5/bind9
> >>>   create mode 100644 
> >>> meta/recipes-connectivity/bind/bind-9.16.5/conf.patch
> >>>   create mode 100644 
> >>> meta/recipes-connectivity/bind/bind-9.16.5/generate-rndc-key.sh
> >>>   create mode 100644 
> >>> meta/recipes-connectivity/bind/bind-9.16.5/init.d-add-support-for-read-only-rootfs.patch
> >>>   create mode 100644 
> >>> meta/recipes-connectivity/bind/bind-9.16.5/make-etc-initd-bind-stop-work.patch
> >>>   create mode 100644 
> >>> meta/recipes-connectivity/bind/bind-9.16.5/named.service
> >>>   create mode 100644 meta/recipes-connectivity/bind/bind_9.16.5.bb
> >>>
> >>> diff --git 
> >>> a/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
> >>>  
> >>> b/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
> >>> new file mode 100644
> >>> index 000..8db96ec049c
> >>> --- /dev/null
> >>> +++ 
> >>> b/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
> >>> @@ -0,0 +1,27 @@
> >>> +From 31dde3562f287429eea94b77250d184818b49063 Mon Sep 17 00:00:00 
> >>> 2001
> >>> +From: Chen Qi 
> >>> +Date: Mon, 15 Oct 2018 16:55:09 +0800
> >>> +Subject: [PATCH] avoid start failure with bind user
> >>> +
> >>> +Upstream-Status: Pending
> >>> +
> >>> +Signed-off-by: Chen Qi 
> >>> +---
> >>> + init.d | 1 +
> >>> + 1 file changed, 1 insertion(+)
> >>> +
> >>> +diff --git a/init.d b/init.d
> >>> +index b2eec60..6e03936 100644
> >>> +--- a/init.d
> >>>  b/init.d
> >>> +@@ -57,6 +57,7 @@ case "$1" in
> >>> +   modprobe capability >/dev/null 2>&1 || true
> >>> +   if [ ! -f /etc/bind/rndc.key ]; then
> >>> +   /usr/sbin/rndc-confgen -a -b 512 -r /dev/urandom
> >>> ++  chown root:bind 

Re: [OE-core][PATCH] lttng-modules: backport patch to fix build for linux-5.4.62+

[Martin Jansa]

Is this exact backport from lttng-modules repo?

I came across this issue in
https://github.com/agherzan/meta-raspberrypi/pull/722
and
https://github.com/lttng/lttng-modules/commit/817e02f9e256b8f2cbb9e3125eb061757b83bd4a
+
https://github.com/lttng/lttng-modules/commit/b6af46d166c48c9e59600a60b5a2a7ead10f179a
look a bit different than this one (and are more correct with fixed kernel
ranges as not every > 5.4.62 kernel had this change).

On Mon, Sep 14, 2020 at 10:11 PM Bruce Ashfield 
wrote:

> In my latest round of linux-yocto reference updates, I ran into these
> same issues, but I needed to pull in more of the fixes on the 2.12
> branch than just this to get things building against 5.8.9.
>
> I didn't need to tweak any of the patches for v5.4.64+ here.
>
> I have 10 backported patches and confirmed my 5.8.9 and 5.4.65 both
> build with the changes.
>
> I can submit that patch along with my reference kernel bumps later today.
>
> Bruce
>
>
> On Mon, Sep 14, 2020 at 3:52 AM Jens Rehsack  wrote:
> >
> > From: Jens Rehsack 
> >
> > Backport patch from lttng-modules/stable-2.12
> > 87b2aff fix: writeback: Fix sync livelock due to b_dirty_time
> processing (v5.9)
> >
> > with minor modfication to catch
> > 6623c19042b6 writeback: Fix sync livelock due to b_dirty_time
> processing
> >
> > from linux/stable-5.4 v5.4.62+
> >
> > Signed-off-by: Jens Rehsack 
> > ---
> >  ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 ++
> >  .../lttng/lttng-modules_2.12.2.bb |   1 +
> >  2 files changed, 118 insertions(+)
> >  create mode 100644
> meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
> >
> > diff --git
> a/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
> b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
> > new file mode 100644
> > index 00..96a1c486ef
> > --- /dev/null
> > +++
> b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
> > @@ -0,0 +1,117 @@
> > +From 87b2affc3eb06f3fb2d0923f18af37713eb6814b Mon Sep 17 00:00:00 2001
> > +From: Michael Jeanson 
> > +Date: Mon, 31 Aug 2020 14:16:01 -0400
> > +Subject: [PATCH] fix: writeback: Fix sync livelock due to b_dirty_time
> > + processing (v5.9)
> > +
> > +See upstream commit:
> > +
> > +  commit f9cae926f35e8230330f28c7b743ad088611a8de
> > +  Author: Jan Kara 
> > +  Date:   Fri May 29 16:08:58 2020 +0200
> > +
> > +writeback: Fix sync livelock due to b_dirty_time processing
> > +
> > +When we are processing writeback for sync(2), move_expired_inodes()
> > +didn't set any inode expiry value (older_than_this). This can
> result in
> > +writeback never completing if there's steady stream of inodes added
> to
> > +b_dirty_time list as writeback rechecks dirty lists after each
> writeback
> > +round whether there's more work to be done. Fix the problem by using
> > +sync(2) start time is inode expiry value when processing
> b_dirty_time
> > +list similarly as for ordinarily dirtied inodes. This requires some
> > +refactoring of older_than_this handling which simplifies the code
> > +noticeably as a bonus.
> > +
> > +Change-Id: I8b894b13ccc14d9b8983ee4c2810a927c319560b
> > +Signed-off-by: Michael Jeanson 
> > +Signed-off-by: Mathieu Desnoyers 
> > +---
> > + .../events/lttng-module/writeback.h   | 39 ---
> > + 1 file changed, 26 insertions(+), 13 deletions(-)
> > +
> > +Upstream Status: Backport
> > +
> > +diff --git a/instrumentation/events/lttng-module/writeback.h
> b/instrumentation/events/lttng-module/writeback.h
> > +index ece67ad..e9018dd 100644
> > +--- a/instrumentation/events/lttng-module/writeback.h
> >  b/instrumentation/events/lttng-module/writeback.h
> > +@@ -384,34 +384,48 @@
> LTTNG_TRACEPOINT_EVENT_WBC_INSTANCE(wbc_balance_dirty_wait,
> writeback_wbc_balanc
> > + #endif
> > + LTTNG_TRACEPOINT_EVENT_WBC_INSTANCE(wbc_writepage,
> writeback_wbc_writepage)
> > +
> > +-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,1,0))
> > ++#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,9,0)) ||
> (LINUX_VERSION_CODE >= KERNEL_VERSION(5,4,62))
> > ++LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
> > ++  TP_PROTO(struct bdi_writeback *wb,
> > ++   struct wb_writeback_work *work,
> > ++   unsigned long dirtied_before,
> > ++   int moved),
> > ++  TP_ARGS(wb, work, dirtied_before, moved),
> > ++  TP_FIELDS(
> > ++  ctf_array_text(char, name, dev_name(wb->bdi->dev), 32)
> > ++  ctf_integer(unsigned long, older, dirtied_before)
> > ++  ctf_integer(int, moved, moved)
> > ++  )
> > ++)
> > ++#elif (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
> > + LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
> > +   TP_PROTO(struct bdi_writeback *wb,
> > +-#if (LINUX_VERSION_CODE >= KERN

Re: [OE-core][PATCH] lttng-modules: backport patch to fix build for linux-5.4.62+

[Bruce Ashfield]

In my latest round of linux-yocto reference updates, I ran into these
same issues, but I needed to pull in more of the fixes on the 2.12
branch than just this to get things building against 5.8.9.

I didn't need to tweak any of the patches for v5.4.64+ here.

I have 10 backported patches and confirmed my 5.8.9 and 5.4.65 both
build with the changes.

I can submit that patch along with my reference kernel bumps later today.

Bruce


On Mon, Sep 14, 2020 at 3:52 AM Jens Rehsack  wrote:
>
> From: Jens Rehsack 
>
> Backport patch from lttng-modules/stable-2.12
> 87b2aff fix: writeback: Fix sync livelock due to b_dirty_time processing 
> (v5.9)
>
> with minor modfication to catch
> 6623c19042b6 writeback: Fix sync livelock due to b_dirty_time processing
>
> from linux/stable-5.4 v5.4.62+
>
> Signed-off-by: Jens Rehsack 
> ---
>  ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 ++
>  .../lttng/lttng-modules_2.12.2.bb |   1 +
>  2 files changed, 118 insertions(+)
>  create mode 100644 
> meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>
> diff --git 
> a/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
>  
> b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
> new file mode 100644
> index 00..96a1c486ef
> --- /dev/null
> +++ 
> b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
> @@ -0,0 +1,117 @@
> +From 87b2affc3eb06f3fb2d0923f18af37713eb6814b Mon Sep 17 00:00:00 2001
> +From: Michael Jeanson 
> +Date: Mon, 31 Aug 2020 14:16:01 -0400
> +Subject: [PATCH] fix: writeback: Fix sync livelock due to b_dirty_time
> + processing (v5.9)
> +
> +See upstream commit:
> +
> +  commit f9cae926f35e8230330f28c7b743ad088611a8de
> +  Author: Jan Kara 
> +  Date:   Fri May 29 16:08:58 2020 +0200
> +
> +writeback: Fix sync livelock due to b_dirty_time processing
> +
> +When we are processing writeback for sync(2), move_expired_inodes()
> +didn't set any inode expiry value (older_than_this). This can result in
> +writeback never completing if there's steady stream of inodes added to
> +b_dirty_time list as writeback rechecks dirty lists after each writeback
> +round whether there's more work to be done. Fix the problem by using
> +sync(2) start time is inode expiry value when processing b_dirty_time
> +list similarly as for ordinarily dirtied inodes. This requires some
> +refactoring of older_than_this handling which simplifies the code
> +noticeably as a bonus.
> +
> +Change-Id: I8b894b13ccc14d9b8983ee4c2810a927c319560b
> +Signed-off-by: Michael Jeanson 
> +Signed-off-by: Mathieu Desnoyers 
> +---
> + .../events/lttng-module/writeback.h   | 39 ---
> + 1 file changed, 26 insertions(+), 13 deletions(-)
> +
> +Upstream Status: Backport
> +
> +diff --git a/instrumentation/events/lttng-module/writeback.h 
> b/instrumentation/events/lttng-module/writeback.h
> +index ece67ad..e9018dd 100644
> +--- a/instrumentation/events/lttng-module/writeback.h
>  b/instrumentation/events/lttng-module/writeback.h
> +@@ -384,34 +384,48 @@ 
> LTTNG_TRACEPOINT_EVENT_WBC_INSTANCE(wbc_balance_dirty_wait, 
> writeback_wbc_balanc
> + #endif
> + LTTNG_TRACEPOINT_EVENT_WBC_INSTANCE(wbc_writepage, writeback_wbc_writepage)
> +
> +-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,1,0))
> ++#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,9,0)) || (LINUX_VERSION_CODE >= 
> KERNEL_VERSION(5,4,62))
> ++LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
> ++  TP_PROTO(struct bdi_writeback *wb,
> ++   struct wb_writeback_work *work,
> ++   unsigned long dirtied_before,
> ++   int moved),
> ++  TP_ARGS(wb, work, dirtied_before, moved),
> ++  TP_FIELDS(
> ++  ctf_array_text(char, name, dev_name(wb->bdi->dev), 32)
> ++  ctf_integer(unsigned long, older, dirtied_before)
> ++  ctf_integer(int, moved, moved)
> ++  )
> ++)
> ++#elif (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
> + LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
> +   TP_PROTO(struct bdi_writeback *wb,
> +-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
> +struct wb_writeback_work *work,
> +-#else
> +-   unsigned long *older_than_this,
> +-#endif
> +int moved),
> +-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
> +   TP_ARGS(wb, work, moved),
> +-#else
> ++  TP_FIELDS(
> ++  ctf_array_text(char, name, dev_name(wb->bdi->dev), 32)
> ++  ctf_integer(int, moved, moved)
> ++  )
> ++)
> ++#elif (LINUX_VERSION_CODE >= KERNEL_VERSION(3,1,0))
> ++LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
> ++  TP_PROTO(struct bdi_writeback *wb,
> ++   unsigned long *older_than_this,
> ++   int moved),
> +   TP_ARGS(wb, ol

[OE-core] [PATCH] bind: Inherit update-alternatives

[Khem Raj]

We are setting u-a for nslookup and it won't work unless we inherit this
class

Signed-off-by: Khem Raj 
Cc: Andrey Zhizhikin 
---
 meta/recipes-connectivity/bind/bind_9.16.5.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/bind/bind_9.16.5.bb 
b/meta/recipes-connectivity/bind/bind_9.16.5.bb
index 07efafde70..103192490a 100644
--- a/meta/recipes-connectivity/bind/bind_9.16.5.bb
+++ b/meta/recipes-connectivity/bind/bind_9.16.5.bb
@@ -25,7 +25,7 @@ UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/";
 # stay at 9.16 follow the ESV versions divisible by 4
 UPSTREAM_CHECK_REGEX = "(?P9.(16|20|24|28)(\.\d+)+(-P\d+)*)/"
 
-inherit autotools update-rc.d systemd useradd pkgconfig multilib_header
+inherit autotools update-rc.d systemd useradd pkgconfig multilib_header 
update-alternatives
 
 # PACKAGECONFIGs readline and libedit should NOT be set at same time
 PACKAGECONFIG ?= "readline"
-- 
2.28.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142549): 
https://lists.openembedded.org/g/openembedded-core/message/142549
Mute This Topic: https://lists.openembedded.org/mt/76849738/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 7/8] bind: Add 9.16.x

[Khem Raj]

On 9/14/20 10:55 AM, Andrey Zhizhikin wrote:

Gentle ping here regarding this issue.

Is thre anyone else experiencing this with IPK packages?


Alright thanks for being persist it has paid off :) I have taken a look 
at it and sent a fix to ml





On Thu, Sep 10, 2020 at 9:12 AM Andrey Zhizhikin  wrote:


On Thu, Sep 10, 2020 at 1:53 AM Khem Raj  wrote:




On 9/7/20 2:17 PM, Andrey Zhizhikin wrote:

On Mon, Sep 7, 2020 at 5:28 PM akuster808  wrote:




On 9/4/20 1:39 AM, Andrey Zhizhikin wrote:

Hello Armin,

On Tue, Sep 1, 2020 at 5:23 PM akuster  wrote:

Removed obsolete packageconfig options

License change to MPL-2.0
https://gitlab.isc.org/isc-projects/bind9/blob/master/LICENSE

Refreshed:
bind-ensure-searching-for-json-headers-searches-sysr.patch
0001-named-lwresd-V-and-start-log-hide-build-options.patch
bind-ensure-searching-for-json-headers-searches-sysr.patch

Drop obsolete patch: 0001-configure.in-remove-useless-L-use_openssl-lib.patch

Signed-off-by: Armin Kuster 
---
  ...1-avoid-start-failure-with-bind-user.patch |  27 ++
  ...d-V-and-start-log-hide-build-options.patch |  35 ++
  ...ching-for-json-headers-searches-sysr.patch |  47 +++
  .../bind/bind-9.16.5/bind9|   2 +
  .../bind/bind-9.16.5/conf.patch   | 330 ++
  .../bind/bind-9.16.5/generate-rndc-key.sh |   8 +
  ...t.d-add-support-for-read-only-rootfs.patch |  65 
  .../make-etc-initd-bind-stop-work.patch   |  42 +++
  .../bind/bind-9.16.5/named.service|  22 ++
  meta/recipes-connectivity/bind/bind_9.16.5.bb | 125 +++
  10 files changed, 703 insertions(+)
  create mode 100644 
meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
  create mode 100644 
meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
  create mode 100644 
meta/recipes-connectivity/bind/bind-9.16.5/bind-ensure-searching-for-json-headers-searches-sysr.patch
  create mode 100644 meta/recipes-connectivity/bind/bind-9.16.5/bind9
  create mode 100644 meta/recipes-connectivity/bind/bind-9.16.5/conf.patch
  create mode 100644 
meta/recipes-connectivity/bind/bind-9.16.5/generate-rndc-key.sh
  create mode 100644 
meta/recipes-connectivity/bind/bind-9.16.5/init.d-add-support-for-read-only-rootfs.patch
  create mode 100644 
meta/recipes-connectivity/bind/bind-9.16.5/make-etc-initd-bind-stop-work.patch
  create mode 100644 meta/recipes-connectivity/bind/bind-9.16.5/named.service
  create mode 100644 meta/recipes-connectivity/bind/bind_9.16.5.bb

diff --git 
a/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
 
b/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
new file mode 100644
index 000..8db96ec049c
--- /dev/null
+++ 
b/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
@@ -0,0 +1,27 @@
+From 31dde3562f287429eea94b77250d184818b49063 Mon Sep 17 00:00:00 2001
+From: Chen Qi 
+Date: Mon, 15 Oct 2018 16:55:09 +0800
+Subject: [PATCH] avoid start failure with bind user
+
+Upstream-Status: Pending
+
+Signed-off-by: Chen Qi 
+---
+ init.d | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/init.d b/init.d
+index b2eec60..6e03936 100644
+--- a/init.d
 b/init.d
+@@ -57,6 +57,7 @@ case "$1" in
+   modprobe capability >/dev/null 2>&1 || true
+   if [ ! -f /etc/bind/rndc.key ]; then
+   /usr/sbin/rndc-confgen -a -b 512 -r /dev/urandom
++  chown root:bind /etc/bind/rndc.key >/dev/null 2>&1 || true
+   chmod 0640 /etc/bind/rndc.key
+   fi
+   if [ -f /var/run/named/named.pid ]; then
+--
+2.7.4
+
diff --git 
a/meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
 
b/meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
new file mode 100644
index 000..5bcc16c9b2b
--- /dev/null
+++ 
b/meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
@@ -0,0 +1,35 @@
+From a3af4a405baf5ff582e82aaba392dd9667d94bdc Mon Sep 17 00:00:00 2001
+From: Hongxu Jia 
+Date: Mon, 27 Aug 2018 21:24:20 +0800
+Subject: [PATCH] `named/lwresd -V' and start log hide build options
+
+The build options expose build path directories, so hide them.
+[snip]
+$ named -V
+|built by make with *** (options are hidden)
+[snip]
+
+Upstream-Status: Inappropriate [oe-core specific]
+
+Signed-off-by: Hongxu Jia 
+
+Refreshed for 9.16.0
+Signed-off-by: Armin Kuster 
+
+---
+ bin/named/include/named/globals.h | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+Index: bind-9.16.0/bin/named/include/named/globals.h
+===
+--- bind-9.16.0.orig/bin/named/include/named/globals.h
 bind-9.16.0/bin/named/include/named/globals.h
+@@ -69,7 +69,7 @@ EXTERN const char *named_g_version I
+ EXTERN co

Re: [OE-core] [PATCH 7/8] bind: Add 9.16.x

[Andrey Zhizhikin]

Gentle ping here regarding this issue.

Is thre anyone else experiencing this with IPK packages?

On Thu, Sep 10, 2020 at 9:12 AM Andrey Zhizhikin  wrote:
>
> On Thu, Sep 10, 2020 at 1:53 AM Khem Raj  wrote:
> >
> >
> >
> > On 9/7/20 2:17 PM, Andrey Zhizhikin wrote:
> > > On Mon, Sep 7, 2020 at 5:28 PM akuster808  wrote:
> > >>
> > >>
> > >>
> > >> On 9/4/20 1:39 AM, Andrey Zhizhikin wrote:
> > >>> Hello Armin,
> > >>>
> > >>> On Tue, Sep 1, 2020 at 5:23 PM akuster  wrote:
> >  Removed obsolete packageconfig options
> > 
> >  License change to MPL-2.0
> >  https://gitlab.isc.org/isc-projects/bind9/blob/master/LICENSE
> > 
> >  Refreshed:
> >  bind-ensure-searching-for-json-headers-searches-sysr.patch
> >  0001-named-lwresd-V-and-start-log-hide-build-options.patch
> >  bind-ensure-searching-for-json-headers-searches-sysr.patch
> > 
> >  Drop obsolete patch: 
> >  0001-configure.in-remove-useless-L-use_openssl-lib.patch
> > 
> >  Signed-off-by: Armin Kuster 
> >  ---
> >   ...1-avoid-start-failure-with-bind-user.patch |  27 ++
> >   ...d-V-and-start-log-hide-build-options.patch |  35 ++
> >   ...ching-for-json-headers-searches-sysr.patch |  47 +++
> >   .../bind/bind-9.16.5/bind9|   2 +
> >   .../bind/bind-9.16.5/conf.patch   | 330 ++
> >   .../bind/bind-9.16.5/generate-rndc-key.sh |   8 +
> >   ...t.d-add-support-for-read-only-rootfs.patch |  65 
> >   .../make-etc-initd-bind-stop-work.patch   |  42 +++
> >   .../bind/bind-9.16.5/named.service|  22 ++
> >   meta/recipes-connectivity/bind/bind_9.16.5.bb | 125 +++
> >   10 files changed, 703 insertions(+)
> >   create mode 100644 
> >  meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
> >   create mode 100644 
> >  meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
> >   create mode 100644 
> >  meta/recipes-connectivity/bind/bind-9.16.5/bind-ensure-searching-for-json-headers-searches-sysr.patch
> >   create mode 100644 meta/recipes-connectivity/bind/bind-9.16.5/bind9
> >   create mode 100644 
> >  meta/recipes-connectivity/bind/bind-9.16.5/conf.patch
> >   create mode 100644 
> >  meta/recipes-connectivity/bind/bind-9.16.5/generate-rndc-key.sh
> >   create mode 100644 
> >  meta/recipes-connectivity/bind/bind-9.16.5/init.d-add-support-for-read-only-rootfs.patch
> >   create mode 100644 
> >  meta/recipes-connectivity/bind/bind-9.16.5/make-etc-initd-bind-stop-work.patch
> >   create mode 100644 
> >  meta/recipes-connectivity/bind/bind-9.16.5/named.service
> >   create mode 100644 meta/recipes-connectivity/bind/bind_9.16.5.bb
> > 
> >  diff --git 
> >  a/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
> >   
> >  b/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
> >  new file mode 100644
> >  index 000..8db96ec049c
> >  --- /dev/null
> >  +++ 
> >  b/meta/recipes-connectivity/bind/bind-9.16.5/0001-avoid-start-failure-with-bind-user.patch
> >  @@ -0,0 +1,27 @@
> >  +From 31dde3562f287429eea94b77250d184818b49063 Mon Sep 17 00:00:00 2001
> >  +From: Chen Qi 
> >  +Date: Mon, 15 Oct 2018 16:55:09 +0800
> >  +Subject: [PATCH] avoid start failure with bind user
> >  +
> >  +Upstream-Status: Pending
> >  +
> >  +Signed-off-by: Chen Qi 
> >  +---
> >  + init.d | 1 +
> >  + 1 file changed, 1 insertion(+)
> >  +
> >  +diff --git a/init.d b/init.d
> >  +index b2eec60..6e03936 100644
> >  +--- a/init.d
> >   b/init.d
> >  +@@ -57,6 +57,7 @@ case "$1" in
> >  +   modprobe capability >/dev/null 2>&1 || true
> >  +   if [ ! -f /etc/bind/rndc.key ]; then
> >  +   /usr/sbin/rndc-confgen -a -b 512 -r /dev/urandom
> >  ++  chown root:bind /etc/bind/rndc.key >/dev/null 2>&1 || true
> >  +   chmod 0640 /etc/bind/rndc.key
> >  +   fi
> >  +   if [ -f /var/run/named/named.pid ]; then
> >  +--
> >  +2.7.4
> >  +
> >  diff --git 
> >  a/meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
> >   
> >  b/meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
> >  new file mode 100644
> >  index 000..5bcc16c9b2b
> >  --- /dev/null
> >  +++ 
> >  b/meta/recipes-connectivity/bind/bind-9.16.5/0001-named-lwresd-V-and-start-log-hide-build-options.patch
> >  @@ -0,0 +1,35 @@
> >  +From a3af4a405baf5ff582e82aaba392dd9667d94bdc Mon Sep 17 00:00:00 2001
> >  +From: Hongxu Jia 
> >  +Date: Mon, 27 Aug 2018 21:24:20 +0800
> > >>

Re: [OE-core] [PATCH] core-image-sato: qemumips use 512 mem

[Khem Raj]

On 9/14/20 12:13 AM, Richard Purdie wrote:

On Sat, 2020-09-12 at 20:59 -0700, akuster wrote:

From: Armin Kuster 

Fixes:

WARNING: core-image-sato-sdk-1.0-r0 do_testimage: Couldn't login into
serial console as root using blank password
WARNING: core-image-sato-sdk-1.0-r0 do_testimage: The output:
root
<<< run_serial(): command timed out after 60 seconds without output




In another run, this error was seen:

Failed to reload daemon: Refusing to reload, not enough space
available on /run/systemd. Currently, 14.3M are free, but a safety
buffer of 16.0M is enforced.

With updates to systemd and Qemu we should revert: 499a31cf06 core-
image-sato: don't use 512MB in qemumips

Signed-off-by: Armin Kuster  
---
  meta/recipes-sato/images/core-image-sato.bb | 1 -
  1 file changed, 1 deletion(-)

diff --git a/meta/recipes-sato/images/core-image-sato.bb
b/meta/recipes-sato/images/core-image-sato.bb
index 673106eb6d..878e0eaa8d 100644
--- a/meta/recipes-sato/images/core-image-sato.bb
+++ b/meta/recipes-sato/images/core-image-sato.bb
@@ -12,4 +12,3 @@ TOOLCHAIN_HOST_TASK_append = " nativesdk-intltool
nativesdk-glib-2.0"
  TOOLCHAIN_HOST_TASK_remove_task-populate-sdk-ext = " nativesdk-
intltool nativesdk-glib-2.0"
  
  QB_MEM = '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m

512", "-m 256", d)}'
-QB_MEM_qemumips = "-m 256"



We have now seen:

https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/2452

with this applied, not sure if its related. We have seen this kind of
network dropout elsewhere but we don't seem to have good debug when it
happens.



I wonder if ssh daemon is dead in this case. I also see its invoking 
compilers on target( kernelmodule case), are they usign -jX during make 
?, 512M might not be enough to run parallel compiles



Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142547): 
https://lists.openembedded.org/g/openembedded-core/message/142547
Mute This Topic: https://lists.openembedded.org/mt/76814331/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] bison: remove the parallel build patch

[Andre McCurdy]

On Mon, Sep 14, 2020 at 1:35 AM Yu, Mingli  wrote:
>
> From: Mingli Yu 
>
> Remove the parallel build patch as the issue have already been
> fixed in bison 3.7.2(f7b642cf build: fix incorrect dependencies).

If parallel make issues have been fixed upstream then this workaround
should be removed from the recipe too:

 # Reset any loadavg set via environment, it breaks parallel build
 # | ../bison-3.5.2/lib/uniwidth/width.c:21:10: fatal error:
uniwidth.h: No such file or directory
 # |  #include "uniwidth.h"
 # |   ^~~~
 EXTRA_OEMAKE_append = " -l"

> Signed-off-by: Mingli Yu 
> ---
>  .../0001-bison-fix-the-parallel-build.patch   | 63 ---
>  meta/recipes-devtools/bison/bison_3.7.2.bb|  1 -
>  2 files changed, 64 deletions(-)
>  delete mode 100644 
> meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
>
> diff --git 
> a/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch 
> b/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
> deleted file mode 100644
> index c3be91a109..00
> --- 
> a/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
> +++ /dev/null
> @@ -1,63 +0,0 @@
> -From e0dbcee6e25b3c0cb11a627bbfe3af45ef67ec30 Mon Sep 17 00:00:00 2001
> -From: Mingli Yu 
> -Date: Thu, 14 May 2020 15:23:16 +0800
> -Subject: [PATCH] bison: fix the parallel build
> -
> -Explicitly make the BUILT_SOURCES which
> -are the generated headers such as stdio.h,
> -fcntl.h and etc to be the dependencies of
> -the gl_LIBOBJS such as libbison_a-sprintf.o,
> -libbison_a-printf.o and etc to guarantee the
> -BUILT_SOURCES is generated before begin to
> -compile EXTRA_lib_libbison_a_SOURCES such as
> -fprintf.c in parallel builid, otherwise there
> -may come below error:
> - | muscle-tab.c:(.text+0x77a): undefined reference to `rpl_sprintf'
> -
> -It does the same for src_bison_OBJECTS and
> -lib_libbison_a_OBJECTS to make sure BUILT_SOURCES
> -generated before begin to compile src_bison_SOURCES
> -which contains AnnotationList.c and etc.
> -
> -BTW, the MOSTLYCLEANFILES also contains the
> -generated header needs to be created early
> -in the build process, so add it also in to
> -avoid below error:
> - | ./lib/uniwidth/width.c:21:10: fatal error: uniwidth.h: No such file or 
> directory
> -
> -Upstream-Status: Submitted [bison-patc...@gnu.org maillist]
> -
> -Signed-off-by: Mingli Yu 
> 
> - lib/gnulib.mk | 2 ++
> - src/local.mk  | 1 +
> - 2 files changed, 3 insertions(+)
> -
> -diff --git a/lib/gnulib.mk b/lib/gnulib.mk
> -index c21c656..27fb3dc 100644
>  a/lib/gnulib.mk
> -+++ b/lib/gnulib.mk
> -@@ -120,6 +120,8 @@ lib_libbison_a_SOURCES =
> - lib_libbison_a_LIBADD = $(gl_LIBOBJS)
> - lib_libbison_a_DEPENDENCIES = $(gl_LIBOBJS)
> - EXTRA_lib_libbison_a_SOURCES =
> -+$(lib_libbison_a_OBJECTS): $(BUILT_SOURCES) $(MOSTLYCLEANFILES:%.h)
> -+$(gl_LIBOBJS): $(BUILT_SOURCES) $(MOSTLYCLEANFILES:%.h)
> -
> - lib_libbison_a_CPPFLAGS = $(AM_CPPFLAGS) 
> -DDEFAULT_TEXT_DOMAIN=\"bison-gnulib\"
> -
> -diff --git a/src/local.mk b/src/local.mk
> -index 61dc573..b5b9079 100644
>  a/src/local.mk
> -+++ b/src/local.mk
> -@@ -24,6 +24,7 @@ if RELOCATABLE_VIA_LD
> -   src_bison_LDFLAGS = `$(RELOCATABLE_LDFLAGS) $(bindir)`
> - endif
> -
> -+$(src_bison_OBJECTS): $(BUILT_SOURCES) $(MOSTLYCLEANFILES:%.h)
> - src_bison_CFLAGS = $(AM_CFLAGS) $(WERROR_CFLAGS)
> - src_bison_SOURCES = \
> -   src/AnnotationList.c  \
> ---
> -2.17.1
> -
> diff --git a/meta/recipes-devtools/bison/bison_3.7.2.bb 
> b/meta/recipes-devtools/bison/bison_3.7.2.bb
> index f7bf70fff3..efc426376d 100644
> --- a/meta/recipes-devtools/bison/bison_3.7.2.bb
> +++ b/meta/recipes-devtools/bison/bison_3.7.2.bb
> @@ -11,7 +11,6 @@ DEPENDS = "bison-native flex-native"
>
>  SRC_URI = "${GNU_MIRROR}/bison/bison-${PV}.tar.xz \
> file://add-with-bisonlocaledir.patch \
> -   file://0001-bison-fix-the-parallel-build.patch \
> "
>  SRC_URI[sha256sum] = 
> "7948d193104d979c0fb0294a1854c73c89d72ae41acfc081826142578a78a91b"
>
> --
> 2.17.1
>
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142546): 
https://lists.openembedded.org/g/openembedded-core/message/142546
Mute This Topic: https://lists.openembedded.org/mt/76837897/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v3] squashfs-tools: Allow COMP_DEFAULT to be changed easily at build time

[Andre McCurdy]

On Mon, Sep 14, 2020 at 2:59 AM Peter Morrow
 wrote:
>
> The default compression algorithm is currently gzip, this patch allows the
> default to be changed by setting SQUASHFS_TOOLS_COMP_DEFAULT to a valid
> compression algorithm.
>
> Signed-off-by: Peter Morrow 
> ---
>  meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb 
> b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> index b06951d..42fae28 100644
> --- a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> +++ b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> @@ -25,6 +25,9 @@ PACKAGECONFIG[xattr] = 
> "XATTR_SUPPORT=1,XATTR_SUPPORT=0,attr"
>  PACKAGECONFIG[zstd] = "ZSTD_SUPPORT=1,ZSTD_SUPPORT=0,zstd"
>  PACKAGECONFIG[reproducible] = 
> "REPRODUCIBLE_DEFAULT=1,REPRODUCIBLE_DEFAULT=0,"
>
> +SQUASHFS_TOOLS_COMP_DEFAULT ?= "gzip"
> +EXTRA_OEMAKE += "COMP_DEFAULT=${SQUASHFS_TOOLS_COMP_DEFAULT}"

Since you can easily override COMP_DEFAULT by setting EXTRA_OEMAKE
from a .bbappend, I don't think it's necessary to add this to the main
recipe.

>  do_compile() {
> oe_runmake all
>  }
> --
> 1.8.3.1
>
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142545): 
https://lists.openembedded.org/g/openembedded-core/message/142545
Mute This Topic: https://lists.openembedded.org/mt/76838796/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] qemu: always define unknown_lock_type

[Joe Slater]

Your patch makes the error always occur at run time.  We can preserve the 
intent of producing an error at link time with the attached patch which was NOT 
accepted upstream.  I think they do not like the name QLNULL.  In any event, it 
does work for all optimizations and applies to the latest master branch of qemu.

Joe

-Original Message-
From: openembedded-core@lists.openembedded.org 
 On Behalf Of Khem Raj
Sent: Monday, September 14, 2020 8:23 AM
To: Yu, Mingli 
Cc: Ross Burton ; OE-core 

Subject: Re: [OE-core] [PATCH] qemu: always define unknown_lock_type

On Sun, Sep 13, 2020 at 11:29 PM Yu, Mingli  wrote:
>
>
>
> On 9/14/20 2:02 PM, Khem Raj wrote:
> >
> >
> > On 9/13/20 10:44 PM, Yu, Mingli wrote:
> >>
> >>
> >> On 9/14/20 1:26 PM, Khem Raj wrote:
> >>>
> >>>
> >>> On 9/13/20 6:50 PM, Yu, Mingli wrote:
> 
> 
>  On 9/10/20 6:41 PM, Ross Burton wrote:
> > On Thu, 10 Sep 2020 at 04:03, Yu, Mingli 
> > 
> > wrote:
> >> +Upstream-Status: Submitted [qemu-devel mailing list]
> >
> > https://lists.nongnu.org/archive/cgi-bin/namazu.cgi?query=unknow
> > n_lock_type&submit=Search%21&idxname=qemu-devel&max=20&result=no
> > rmal&sort=score
> >
> >
> > doesn't find this patch, can you link to it please?
> >
> 
>  Hi Ross,
> 
>  The link is
>  https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg03873
>  .html,
>  will include the link in V2.
> >>>
> >>> are you compiling without __OPTIMIZE__ defined ? qemu may not work
> >>
> >> Hi Khem,
> >>
> >> I didn't especially customize something for __OPTIMIZE__,  could 
> >> you help guide where to define it?
> >
> > perhaps you are not using one of -O option ?
>
> -Og passed to the compiler as DEBUG_BUILD = "1" defined in local.conf.

Does qemu work when built with -Og


0001-lockable-use-QLNULL-for-a-null-lockable.patch
Description: 0001-lockable-use-QLNULL-for-a-null-lockable.patch
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142544): 
https://lists.openembedded.org/g/openembedded-core/message/142544
Mute This Topic: https://lists.openembedded.org/mt/76748224/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2] cve-check: use ALLOWLIST

[Khem Raj]

On Mon, Sep 14, 2020 at 3:42 AM Ross Burton  wrote:
>
> On Mon, 14 Sep 2020 at 04:34, Lee Chee Yang  wrote:
> > use allowlist instead of whitelist.
> > Replace CVE_CHECK_PN_WHITELIST with CVE_CHECK_PN_ALLOWLIST.
>
> This is a deprecated variable already, I wouldn't bother changing it.
>
> > Replace CVE_CHECK_WHITELIST with CVE_CHECK_ALLOWLIST.
>
> ALLOWLIST really is a horrible word as this isn't a list of CVEs being
> allowed, it's a list of CVEs being not considered.  CVE_CHECK_IGNORE?
> CVE_CHECK_EXCLUDE?

Yeah it's more like an ignored list than block list.

>
> I do also think that we should do these variable renames in one go,
> instead of piecemeal either side of a release.
>
> Ross
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142543): 
https://lists.openembedded.org/g/openembedded-core/message/142543
Mute This Topic: https://lists.openembedded.org/mt/76835201/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 1/3] cve-update-db-native: be less magical about checking whether the cve-check class is enabled

[Chris Laplante via lists.openembedded.org]

Signed-off-by: Chris Laplante 
---
 meta/recipes-core/meta/cve-update-db-native.bb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/recipes-core/meta/cve-update-db-native.bb 
b/meta/recipes-core/meta/cve-update-db-native.bb
index e4e2451bfd..c2f713312f 100644
--- a/meta/recipes-core/meta/cve-update-db-native.bb
+++ b/meta/recipes-core/meta/cve-update-db-native.bb
@@ -13,8 +13,7 @@ deltask do_install
 deltask do_populate_sysroot
 
 python () {
-cve_check_db_file = d.getVar("CVE_CHECK_DB_FILE")
-if not cve_check_db_file:
+if not bb.data.inherits_class("cve-check", d):
 raise bb.parse.SkipRecipe("Skip recipe when cve-check class is not 
loaded.")
 
 if os.path.exists("%s-journal" % cve_check_db_file ):
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142540): 
https://lists.openembedded.org/g/openembedded-core/message/142540
Mute This Topic: https://lists.openembedded.org/mt/76844932/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 3/3] cve-update-db-native: remove unused variable

[Chris Laplante via lists.openembedded.org]

Signed-off-by: Chris Laplante 
---
 meta/recipes-core/meta/cve-update-db-native.bb | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta/recipes-core/meta/cve-update-db-native.bb 
b/meta/recipes-core/meta/cve-update-db-native.bb
index 242fbc2f30..cf2b251e21 100644
--- a/meta/recipes-core/meta/cve-update-db-native.bb
+++ b/meta/recipes-core/meta/cve-update-db-native.bb
@@ -33,7 +33,6 @@ python do_fetch() {
 
 db_file = d.getVar("CVE_CHECK_DB_FILE")
 db_dir = os.path.dirname(db_file)
-json_tmpfile = os.path.join(db_dir, 'nvd.json.gz')
 
 if os.path.exists("{0}-journal".format(db_file)):
 # If a journal is present the last update might have been interrupted. 
In that case,
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142542): 
https://lists.openembedded.org/g/openembedded-core/message/142542
Mute This Topic: https://lists.openembedded.org/mt/76844934/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 2/3] cve-update-db-native: move -journal checking into do_fetch

[Chris Laplante via lists.openembedded.org]

It was always questionable to do this in an anonymous function, but now
with multiconfig it is a critical mistake and leads to more strange
"Exception: sqlite3.OperationalError: disk I/O error" errors.

Signed-off-by: Chris Laplante 
---
 meta/recipes-core/meta/cve-update-db-native.bb | 14 --
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/meta/recipes-core/meta/cve-update-db-native.bb 
b/meta/recipes-core/meta/cve-update-db-native.bb
index c2f713312f..242fbc2f30 100644
--- a/meta/recipes-core/meta/cve-update-db-native.bb
+++ b/meta/recipes-core/meta/cve-update-db-native.bb
@@ -15,12 +15,6 @@ deltask do_populate_sysroot
 python () {
 if not bb.data.inherits_class("cve-check", d):
 raise bb.parse.SkipRecipe("Skip recipe when cve-check class is not 
loaded.")
-
-if os.path.exists("%s-journal" % cve_check_db_file ):
-os.remove("%s-journal" % cve_check_db_file)
-
-if os.path.exists(cve_check_db_file):
-os.remove(cve_check_db_file)
 }
 
 python do_fetch() {
@@ -41,6 +35,14 @@ python do_fetch() {
 db_dir = os.path.dirname(db_file)
 json_tmpfile = os.path.join(db_dir, 'nvd.json.gz')
 
+if os.path.exists("{0}-journal".format(db_file)):
+# If a journal is present the last update might have been interrupted. 
In that case,
+# just wipe any leftovers and force the DB to be recreated.
+os.remove("{0}-journal".format(db_file))
+
+if os.path.exists(db_file):
+os.remove(db_file)
+
 # Don't refresh the database more than once an hour
 try:
 import time
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142541): 
https://lists.openembedded.org/g/openembedded-core/message/142541
Mute This Topic: https://lists.openembedded.org/mt/76844933/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [meta-oe][PATCH 0/5] ARMv8 Tune reorg

[Martin Jansa]

> This reduces the number of files from 12 to 2 for ARMv8a, and that is
excluding the 13 I am adding in this series that would otherwise be unique
files.

I don't have a strong opinion on this anymore, but is the number of the
include files the issue here?

I think the issue is the number of possible combinations and using the same
TUNE_PKGARCH for different tunes (unlike 32bit arm tune files which use
different). Bundling all these combinations in fewer include files doesn't
IMHO improve it.

With 32bit arm include files it was useful to be able to compare various
include files to check that they follow the same "structure" (or to add new
cortexa* one by copying existing and regex-replace).

Also AVAILTUNES will now contain all possible tunes from given family
(which makes it almost useless for aarch64 tunes). So instead of BSP
including .inc file corresponding with the core used in the MACHINE and
getting some "sane" default DEFAULTTUNE (plus some other possible options
listed in AVAILTUNES) we now force every BSP to set more
specific DEFAULTTUNE and then let user figure out what other DEFAULTTUNEs
might be compatible with it, e.g. when someone is doing multi MACHINE
builds and wants to share TUNE_PKGARCH between them (to save build time,
package feed size etc).

Cheers,

On Mon, Sep 14, 2020 at 5:14 PM Jon Mason  wrote:

> There is a large number of Arm Tune files located in
> meta/conf/machine/include/, and to support the current and upcoming Arm
> cores, more are needed.  Adding more files is simply going to make it
> harder to find the relevant ones for an OE/YP developer/user.  Also,
> there are problems with stale and erroneous configs (see my previous
> series), which will only be exacerbated by having more files.
>
> I am proposing a reorganization of the existing tune files by including
> them in the generic family include file.  For example, the
> tune-cortexa55.inc would be moved into arch-armv8-2a.inc, and
> tune-cortexa57.inc would be moved into arch-armv8a.inc.  This reduces
> the number of files from 12 to 2 for ARMv8a, and that is excluding the
> 13 I am adding in this series that would otherwise be unique files.
>
> To use, simply add
> ...
> DEFAULTTUNE ?= "neoversen1"
> require conf/machine/include/arm/arch-armv8-2a.inc
> ...
>
> Which is arguably what should be done anyway (instead of taking the
> default of the tune include file).
> See the qemuarm64 patch in the series for a working example.
>
> Of course, by removing the existing tune files, current users are going
> to break.  A simple script can be written to use sed (or similar) to
> replace the relevant parts for those users that would be affected (at
> least for those that are in the layer index and update regularly).
>
> Thanks,
> Jon
>
> ---
>
> Originally sent as a RFC in
> https://lists.openembedded.org/g/openembedded-core/message/142324
>
> Given the generally positive feedback, sending as a patch series.
> Keeping the "hard fail" of the file removal (per Richards comment in
> https://lists.openembedded.org/g/openembedded-core/message/142356).
> Only difference of note is the removal of the "arm64: set BASE_LIB to
> lib64", as there needs to be more investigation (see
> https://lists.openembedded.org/g/openembedded-core/message/142414).
>
>
> Jon Mason (5):
>   arch-armv8-2a.inc: Add Cortex-A55 tunings
>   arch-armv8a.inc: Add existing tunings
>   qemuarm64: change tuning
>   arch-armv8a.inc: Add tunes for supported ARMv8a cores
>   arch-armv8-2a.inc: Add tunes for supported ARMv8.2a cores
>
>  .../machine/include/arm/arch-armv8-2a.inc | 175 ++-
>  meta/conf/machine/include/arm/arch-armv8a.inc | 206 +-
>  meta/conf/machine/include/tune-cortexa32.inc  |  18 --
>  meta/conf/machine/include/tune-cortexa35.inc  |  17 --
>  meta/conf/machine/include/tune-cortexa53.inc  |  18 --
>  meta/conf/machine/include/tune-cortexa55.inc  |  13 --
>  .../include/tune-cortexa57-cortexa53.inc  |  15 --
>  meta/conf/machine/include/tune-cortexa57.inc  |  17 --
>  .../include/tune-cortexa72-cortexa53.inc  |  20 --
>  meta/conf/machine/include/tune-cortexa72.inc  |  13 --
>  .../include/tune-cortexa73-cortexa53.inc  |  20 --
>  meta/conf/machine/include/tune-thunderx.inc   |  19 --
>  meta/conf/machine/qemuarm64.conf  |   3 +-
>  13 files changed, 371 insertions(+), 183 deletions(-)
>  delete mode 100644 meta/conf/machine/include/tune-cortexa32.inc
>  delete mode 100644 meta/conf/machine/include/tune-cortexa35.inc
>  delete mode 100644 meta/conf/machine/include/tune-cortexa53.inc
>  delete mode 100644 meta/conf/machine/include/tune-cortexa55.inc
>  delete mode 100644 meta/conf/machine/include/tune-cortexa57-cortexa53.inc
>  delete mode 100644 meta/conf/machine/include/tune-cortexa57.inc
>  delete mode 100644 meta/conf/machine/include/tune-cortexa72-cortexa53.inc
>  delete mode 100644 meta/conf/machine/include/tune-cortexa72.inc
>  delete mode 100644 meta/conf/machine/include/tune-cortexa73

Re: [OE-core] [PATCH] qemu: always define unknown_lock_type

[Khem Raj]

On Sun, Sep 13, 2020 at 11:29 PM Yu, Mingli  wrote:
>
>
>
> On 9/14/20 2:02 PM, Khem Raj wrote:
> >
> >
> > On 9/13/20 10:44 PM, Yu, Mingli wrote:
> >>
> >>
> >> On 9/14/20 1:26 PM, Khem Raj wrote:
> >>>
> >>>
> >>> On 9/13/20 6:50 PM, Yu, Mingli wrote:
> 
> 
>  On 9/10/20 6:41 PM, Ross Burton wrote:
> > On Thu, 10 Sep 2020 at 04:03, Yu, Mingli 
> > wrote:
> >> +Upstream-Status: Submitted [qemu-devel mailing list]
> >
> > https://lists.nongnu.org/archive/cgi-bin/namazu.cgi?query=unknown_lock_type&submit=Search%21&idxname=qemu-devel&max=20&result=normal&sort=score
> >
> >
> > doesn't find this patch, can you link to it please?
> >
> 
>  Hi Ross,
> 
>  The link is
>  https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg03873.html,
>  will include the link in V2.
> >>>
> >>> are you compiling without __OPTIMIZE__ defined ? qemu may not work
> >>
> >> Hi Khem,
> >>
> >> I didn't especially customize something for __OPTIMIZE__,  could you
> >> help guide where to define it?
> >
> > perhaps you are not using one of -O option ?
>
> -Og passed to the compiler as DEBUG_BUILD = "1" defined in local.conf.

Does qemu work when built with -Og
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142538): 
https://lists.openembedded.org/g/openembedded-core/message/142538
Mute This Topic: https://lists.openembedded.org/mt/76748224/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [meta-oe][PATCH 4/5] arch-armv8a.inc: Add tunes for supported ARMv8a cores

[Jon Mason]

Add tunes for all the ARMv8a cores currently supported in GCC.  This
is: Cortex-A34, Cortex-A73, and Cortex-A73-Cortex-A35.

Signed-off-by: Jon Mason 
---
 meta/conf/machine/include/arm/arch-armv8a.inc | 49 +++
 1 file changed, 49 insertions(+)

diff --git a/meta/conf/machine/include/arm/arch-armv8a.inc 
b/meta/conf/machine/include/arm/arch-armv8a.inc
index eaf601216a3d..3febbcb6a6f6 100644
--- a/meta/conf/machine/include/arm/arch-armv8a.inc
+++ b/meta/conf/machine/include/arm/arch-armv8a.inc
@@ -15,6 +15,23 @@ PACKAGE_EXTRA_ARCHS_tune-cortexa32-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-
 BASE_LIB_tune-cortexa32= "lib"
 BASE_LIB_tune-cortexa32-crypto = "lib"
 
+#
+# Tune Settings for Cortex-A34
+#
+TUNEVALID[cortexa34] = "Enable Cortex-A34 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa34', ' 
-mcpu=cortex-a34', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES+= "cortexa34 cortexa34-crypto"
+ARMPKGARCH_tune-cortexa34  = "cortexa34"
+ARMPKGARCH_tune-cortexa34-crypto   = "cortexa34"
+TUNE_FEATURES_tune-cortexa34   = "aarch64 cortexa34 crc"
+TUNE_FEATURES_tune-cortexa34-crypto= "${TUNE_FEATURES_tune-cortexa34} 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa34 = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc} cortexa34"
+PACKAGE_EXTRA_ARCHS_tune-cortexa34-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-crypto} cortexa34 cortexa34-crypto"
+BASE_LIB_tune-cortexa34= "lib64"
+BASE_LIB_tune-cortexa34-crypto = "lib64"
+
 #
 # Tune Settings for Cortex-A35
 #
@@ -80,6 +97,20 @@ PACKAGE_EXTRA_ARCHS_tune-cortexa72 = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-
 BASE_LIB_tune-cortexa72= "lib64"
 BASE_LIB_tune-cortexa72-crypto = "lib64"
 
+#
+# Tune Settings for Cortex-A73
+#
+TUNEVALID[cortexa73] = "Enable Cortex-A73 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa73', ' 
-mcpu=cortex-a73', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES+= "cortexa73"
+ARMPKGARCH_tune-cortexa73  = "cortexa73"
+TUNE_FEATURES_tune-cortexa73   = "aarch64 cortexa73 crc crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa73 = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-crypto} cortexa73"
+BASE_LIB_tune-cortexa73= "lib64"
+BASE_LIB_tune-cortexa73-crypto = "lib64"
+
 #
 # Tune Settings for ThunderX
 #
@@ -128,6 +159,24 @@ PACKAGE_EXTRA_ARCHS_tune-cortexa72-cortexa53-crypto = 
"${PACKAGE_EXTRA_ARCHS_tun
 BASE_LIB_tune-cortexa72-cortexa53  = "lib64"
 BASE_LIB_tune-cortexa72-cortexa53-crypto   = "lib64"
 
+#
+# Tune Settings for big.LITTLE Cortex-A73 - Cortex-A35
+#
+TUNEVALID[cortexa73-cortexa35] = "Enable big.LITTLE Cortex-A73.Cortex-A35 
specific processor optimizations"
+MACHINEOVERRIDES =. "${@bb.utils.contains("TUNE_FEATURES", 
"cortexa73-cortexa35", "cortexa73-cortexa35:", "" ,d)}"
+TUNE_CCARGS .= "${@bb.utils.contains("TUNE_FEATURES", "cortexa73-cortexa35", " 
-mcpu=cortex-a73.cortex-a35", "", d)}"
+
+# cortexa73.cortexa35 implies crc support
+AVAILTUNES+= "cortexa73-cortexa35 
cortexa73-cortexa35-crypto"
+ARMPKGARCH_tune-cortexa73-cortexa35= "cortexa73-cortexa35"
+ARMPKGARCH_tune-cortexa73-cortexa35-crypto = "cortexa73-cortexa35-crypto"
+TUNE_FEATURES_tune-cortexa73-cortexa35 = "aarch64 crc cortexa73-cortexa35"
+TUNE_FEATURES_tune-cortexa73-cortexa35-crypto = 
"${TUNE_FEATURES_tune-cortexa73-cortexa35} crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa73-cortexa35  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc} cortexa73-cortexa35"
+PACKAGE_EXTRA_ARCHS_tune-cortexa73-cortexa35-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-crypto} cortexa73-cortexa35 
cortexa73-cortexa35-crypto"
+BASE_LIB_tune-cortexa73-cortexa35  = "lib64"
+BASE_LIB_tune-cortexa73-cortexa35-crypto   = "lib64"
+
 #
 # Tune Settings for big.LITTLE Cortex-A73 - Cortex-A53
 #
-- 
2.20.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142536): 
https://lists.openembedded.org/g/openembedded-core/message/142536
Mute This Topic: https://lists.openembedded.org/mt/76844478/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [meta-oe][PATCH 5/5] arch-armv8-2a.inc: Add tunes for supported ARMv8.2a cores

[Jon Mason]

Add tunes for all the ARMv8.2a cores currently supported in GCC.  This
is: Cortex-A65, Cortex-A65AE, Cortex-A75, Cortex-A76, Cortex-A76AE,
Cortex-A77, Neoverse-E1, Neoverse-N1, Cortex-A75-Cortex-A55, and
Cortex-A76-Cortex-A55.

Signed-off-by: Jon Mason 
---
 .../machine/include/arm/arch-armv8-2a.inc | 139 ++
 1 file changed, 139 insertions(+)

diff --git a/meta/conf/machine/include/arm/arch-armv8-2a.inc 
b/meta/conf/machine/include/arm/arch-armv8-2a.inc
index 3fc9658400a3..f620eafa013b 100644
--- a/meta/conf/machine/include/arm/arch-armv8-2a.inc
+++ b/meta/conf/machine/include/arm/arch-armv8-2a.inc
@@ -11,6 +11,145 @@ TUNE_FEATURES_tune-cortexa55= 
"aarch64 cortexa55 crypto"
 PACKAGE_EXTRA_ARCHS_tune-cortexa55  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa55"
 BASE_LIB_tune-cortexa55 = "lib64"
 
+#
+# Tune Settings for Cortex-A65
+#
+TUNEVALID[cortexa65] = "Enable Cortex-A65 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa65', ' 
-mcpu=cortex-a65', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES += "cortexa65"
+ARMPKGARCH_tune-cortexa65   = "cortexa65"
+TUNE_FEATURES_tune-cortexa65= "aarch64 cortexa65 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa65  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa65"
+BASE_LIB_tune-cortexa65 = "lib64"
+
+#
+# Tune Settings for Cortex-A65AE
+#
+TUNEVALID[cortexa65ae] = "Enable Cortex-A65AE specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa65ae', ' 
-mcpu=cortex-a65ae', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES += "cortexa65ae"
+ARMPKGARCH_tune-cortexa65ae = "cortexa65ae"
+TUNE_FEATURES_tune-cortexa65ae  = "aarch64 cortexa65ae 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa65ae= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa65ae"
+BASE_LIB_tune-cortexa65ae   = "lib64"
+
+#
+# Tune Settings for Cortex-A75
+#
+TUNEVALID[cortexa75] = "Enable Cortex-A75 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa75', ' 
-mcpu=cortex-a75', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES += "cortexa75"
+ARMPKGARCH_tune-cortexa75   = "cortexa75"
+TUNE_FEATURES_tune-cortexa75= "aarch64 cortexa75 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa75  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa75"
+BASE_LIB_tune-cortexa75 = "lib64"
+
+#
+# Tune Settings for Cortex-A76
+#
+TUNEVALID[cortexa76] = "Enable Cortex-A76 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa76', ' 
-mcpu=cortex-a76', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES += "cortexa76"
+ARMPKGARCH_tune-cortexa76   = "cortexa76"
+TUNE_FEATURES_tune-cortexa76= "aarch64 cortexa76 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa76  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa76"
+BASE_LIB_tune-cortexa76 = "lib64"
+
+#
+# Tune Settings for Cortex-A76AE
+#
+TUNEVALID[cortexa76ae] = "Enable Cortex-A76AE specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa76ae', ' 
-mcpu=cortex-a76ae', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES += "cortexa76ae"
+ARMPKGARCH_tune-cortexa76ae = "cortexa76ae"
+TUNE_FEATURES_tune-cortexa76ae  = "aarch64 cortexa76ae 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa76ae= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa76ae"
+BASE_LIB_tune-cortexa76ae   = "lib64"
+
+#
+# Tune Settings for Cortex-A77
+#
+TUNEVALID[cortexa77] = "Enable Cortex-A77 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa77', ' 
-mcpu=cortex-a77', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES += "cortexa77"
+ARMPKGARCH_tune-cortexa77   = "cortexa77"
+TUNE_FEATURES_tune-cortexa77= "aarch64 cortexa77 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa77  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa77"
+BASE_LIB_tune-cortexa77 = "lib64"
+
+#
+# Tune Settings for Neoverse-E1
+#
+TUNEVALID[neoversee1] = "Enable Neoverse-E1 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'neoversee1', ' 
-mcpu=neoverse-e1', '', d)}"

[OE-core] [meta-oe][PATCH 3/5] qemuarm64: change tuning

[Jon Mason]

The previous patch caused the tuning file referenced here to be removed.
Use the new one with the new DEFAULTTUNE.

Signed-off-by: Jon Mason 
---
 meta/conf/machine/qemuarm64.conf | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/conf/machine/qemuarm64.conf b/meta/conf/machine/qemuarm64.conf
index fdd464d708be..9367f6ccb8d0 100644
--- a/meta/conf/machine/qemuarm64.conf
+++ b/meta/conf/machine/qemuarm64.conf
@@ -2,7 +2,8 @@
 #@NAME: QEMU ARMv8 machine
 #@DESCRIPTION: Machine configuration for running an ARMv8 system on QEMU
 
-require conf/machine/include/tune-cortexa57.inc
+DEFAULTTUNE ?= "cortexa57"
+require conf/machine/include/arm/arch-armv8a.inc
 require conf/machine/include/qemu.inc
 
 KERNEL_IMAGETYPE = "Image"
-- 
2.20.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142535): 
https://lists.openembedded.org/g/openembedded-core/message/142535
Mute This Topic: https://lists.openembedded.org/mt/76844477/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [meta-oe][PATCH 2/5] arch-armv8a.inc: Add existing tunings

[Jon Mason]

Migrate the existing tune settings to arch-armv8a.inc.  This will allow
for a single file to include all of the tunings of a family of
processors.  This will reduce the proliferation of unique files per
processor currently occurring in conf/machine/include/

Signed-off-by: Jon Mason 
---
 meta/conf/machine/include/arm/arch-armv8a.inc | 157 +-
 meta/conf/machine/include/tune-cortexa32.inc  |  18 --
 meta/conf/machine/include/tune-cortexa35.inc  |  17 --
 meta/conf/machine/include/tune-cortexa53.inc  |  18 --
 .../include/tune-cortexa57-cortexa53.inc  |  15 --
 meta/conf/machine/include/tune-cortexa57.inc  |  17 --
 .../include/tune-cortexa72-cortexa53.inc  |  20 ---
 meta/conf/machine/include/tune-cortexa72.inc  |  13 --
 .../include/tune-cortexa73-cortexa53.inc  |  20 ---
 meta/conf/machine/include/tune-thunderx.inc   |  19 ---
 10 files changed, 155 insertions(+), 159 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-cortexa32.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa35.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa53.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa57-cortexa53.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa57.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa72-cortexa53.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa72.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa73-cortexa53.inc
 delete mode 100644 meta/conf/machine/include/tune-thunderx.inc

diff --git a/meta/conf/machine/include/arm/arch-armv8a.inc 
b/meta/conf/machine/include/arm/arch-armv8a.inc
index f810a1e8fc98..eaf601216a3d 100644
--- a/meta/conf/machine/include/arm/arch-armv8a.inc
+++ b/meta/conf/machine/include/arm/arch-armv8a.inc
@@ -1,4 +1,155 @@
-DEFAULTTUNE ?= "armv8a-crc"
+#
+# Tune Settings for Cortex-A32 (32bit only)
+#
+TUNEVALID[cortexa32] = "Enable Cortex-A32 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa32', ' 
-mcpu=cortex-a32', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES+= "cortexa32 cortexa32-crypto"
+ARMPKGARCH_tune-cortexa32  = "cortexa32"
+ARMPKGARCH_tune-cortexa32-crypto   = "cortexa32"
+TUNE_FEATURES_tune-cortexa32   = "armv8a cortexa32 crc"
+TUNE_FEATURES_tune-cortexa32-crypto= "${TUNE_FEATURES_tune-cortexa32} 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa32 = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc} cortexa32"
+PACKAGE_EXTRA_ARCHS_tune-cortexa32-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-crypto} cortexa32 cortexa32-crypto"
+BASE_LIB_tune-cortexa32= "lib"
+BASE_LIB_tune-cortexa32-crypto = "lib"
+
+#
+# Tune Settings for Cortex-A35
+#
+TUNEVALID[cortexa35] = "Enable Cortex-A35 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa35', ' 
-mcpu=cortex-a35', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES+= "cortexa35 cortexa35-crypto"
+ARMPKGARCH_tune-cortexa35  = "cortexa35"
+ARMPKGARCH_tune-cortexa35-crypto   = "cortexa35"
+TUNE_FEATURES_tune-cortexa35   = "aarch64 cortexa35 crc"
+TUNE_FEATURES_tune-cortexa35-crypto= "${TUNE_FEATURES_tune-cortexa35} 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa35 = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc} cortexa35"
+PACKAGE_EXTRA_ARCHS_tune-cortexa35-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-crypto} cortexa35 cortexa35-crypto"
+BASE_LIB_tune-cortexa35= "lib64"
+BASE_LIB_tune-cortexa35-crypto = "lib64"
+
+#
+# Tune Settings for Cortex-A53
+#
+TUNEVALID[cortexa53] = "Enable Cortex-A53 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa53', ' 
-mcpu=cortex-a53', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES+= "cortexa53 cortexa53-crypto"
+ARMPKGARCH_tune-cortexa53  = "cortexa53"
+ARMPKGARCH_tune-cortexa53-crypto   = "cortexa53-crypto"
+TUNE_FEATURES_tune-cortexa53   = "aarch64 cortexa53 crc"
+TUNE_FEATURES_tune-cortexa53-crypto= "${TUNE_FEATURES_tune-cortexa53} 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa53 = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc} cortexa53"
+PACKAGE_EXTRA_ARCHS_tune-cortexa53-crypto  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-crypto} cortexa53 cortexa53-crypto"
+BASE_LIB_tune-cortexa53= "lib64"
+BASE_LIB_tune-cortexa53-crypto = "lib64"
+
+#
+# Tune Settings for Cortex-A57
+#
+TUNEVALID[cortexa57] = "Enable Cortex-A57 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa57', ' 
-mcpu=cortex-a57', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES+= "cortexa57 cortexa57-crypto"
+ARMPKGARCH_tune-cortexa57  = "cort

[OE-core] [meta-oe][PATCH 1/5] arch-armv8-2a.inc: Add Cortex-A55 tunings

[Jon Mason]

Migrate the settings in tune-cortexa55.inc to arch-armv8-2a.inc.  This
will allow for a single file to include all of the tunings of a family
of processors.  This will reduce the proliferation of unique files per
processor currently occurring in conf/machine/include/

Signed-off-by: Jon Mason 
---
 .../machine/include/arm/arch-armv8-2a.inc | 36 +--
 meta/conf/machine/include/tune-cortexa55.inc  | 13 ---
 2 files changed, 26 insertions(+), 23 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-cortexa55.inc

diff --git a/meta/conf/machine/include/arm/arch-armv8-2a.inc 
b/meta/conf/machine/include/arm/arch-armv8-2a.inc
index 1c095256d185..3fc9658400a3 100644
--- a/meta/conf/machine/include/arm/arch-armv8-2a.inc
+++ b/meta/conf/machine/include/arm/arch-armv8-2a.inc
@@ -1,4 +1,20 @@
-DEFAULTTUNE ?= "armv8-2a"
+#
+# Tune Settings for Cortex-A55
+#
+TUNEVALID[cortexa55] = "Enable Cortex-A55 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa55', ' 
-mcpu=cortex-a55', '', d)}"
+
+# Little Endian base configs
+AVAILTUNES += "cortexa55"
+ARMPKGARCH_tune-cortexa55   = "cortexa55"
+TUNE_FEATURES_tune-cortexa55= "aarch64 cortexa55 
crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa55  = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa55"
+BASE_LIB_tune-cortexa55 = "lib64"
+
+#
+# Defaults for ARMv8-a
+#
+DEFAULTTUNE?= "armv8-2a"
 
 TUNEVALID[armv8-2a] = "Enable instructions for ARMv8-a"
 TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv8-2a', ' 
-march=armv8.2-a', '', d)}"
@@ -8,12 +24,12 @@ MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 
'armv8-2a', 'armv8-2a
 require conf/machine/include/arm/arch-armv8a.inc
 
 # Little Endian base configs
-AVAILTUNES += "armv8-2a armv8-2a-crypto"
-ARMPKGARCH_tune-armv8-2a?= "armv8-2a"
-ARMPKGARCH_tune-armv8-2a-crypto ?= "armv8-2a"
-TUNE_FEATURES_tune-armv8-2a  = "aarch64 armv8-2a"
-TUNE_FEATURES_tune-armv8-2a-crypto   = "${TUNE_FEATURES_tune-armv8-2a} 
crypto"
-PACKAGE_EXTRA_ARCHS_tune-armv8-2a= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a} armv8-2a"
-PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a} armv8-2a-crypto"
-BASE_LIB_tune-armv8-2a   = "lib64"
-BASE_LIB_tune-armv8-2a-crypto= "lib64"
+AVAILTUNES += "armv8-2a 
armv8-2a-crypto"
+ARMPKGARCH_tune-armv8-2a   ?= "armv8-2a"
+ARMPKGARCH_tune-armv8-2a-crypto?= "armv8-2a"
+TUNE_FEATURES_tune-armv8-2a = "aarch64 armv8-2a"
+TUNE_FEATURES_tune-armv8-2a-crypto  = 
"${TUNE_FEATURES_tune-armv8-2a} crypto"
+PACKAGE_EXTRA_ARCHS_tune-armv8-2a   = 
"${PACKAGE_EXTRA_ARCHS_tune-armv8a} armv8-2a"
+PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a} armv8-2a-crypto"
+BASE_LIB_tune-armv8-2a  = "lib64"
+BASE_LIB_tune-armv8-2a-crypto   = "lib64"
diff --git a/meta/conf/machine/include/tune-cortexa55.inc 
b/meta/conf/machine/include/tune-cortexa55.inc
deleted file mode 100644
index 66a5d0c437ee..
--- a/meta/conf/machine/include/tune-cortexa55.inc
+++ /dev/null
@@ -1,13 +0,0 @@
-DEFAULTTUNE ?= "cortexa55"
-
-TUNEVALID[cortexa55] = "Enable Cortex-A55 specific processor optimizations"
-TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexa55', ' 
-mcpu=cortex-a55', '', d)}"
-
-require conf/machine/include/arm/arch-armv8-2a.inc
-
-# Little Endian base configs
-AVAILTUNES += "cortexa55"
-ARMPKGARCH_tune-cortexa55 = "cortexa55"
-TUNE_FEATURES_tune-cortexa55  = "aarch64 cortexa55 crypto"
-PACKAGE_EXTRA_ARCHS_tune-cortexa55= 
"${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa55"
-BASE_LIB_tune-cortexa55   = "lib64"
-- 
2.20.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142533): 
https://lists.openembedded.org/g/openembedded-core/message/142533
Mute This Topic: https://lists.openembedded.org/mt/76844474/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [meta-oe][PATCH 0/5] ARMv8 Tune reorg

[Jon Mason]

There is a large number of Arm Tune files located in
meta/conf/machine/include/, and to support the current and upcoming Arm
cores, more are needed.  Adding more files is simply going to make it
harder to find the relevant ones for an OE/YP developer/user.  Also,
there are problems with stale and erroneous configs (see my previous
series), which will only be exacerbated by having more files.

I am proposing a reorganization of the existing tune files by including
them in the generic family include file.  For example, the
tune-cortexa55.inc would be moved into arch-armv8-2a.inc, and
tune-cortexa57.inc would be moved into arch-armv8a.inc.  This reduces
the number of files from 12 to 2 for ARMv8a, and that is excluding the
13 I am adding in this series that would otherwise be unique files.

To use, simply add
...
DEFAULTTUNE ?= "neoversen1"
require conf/machine/include/arm/arch-armv8-2a.inc
...

Which is arguably what should be done anyway (instead of taking the
default of the tune include file).
See the qemuarm64 patch in the series for a working example.

Of course, by removing the existing tune files, current users are going
to break.  A simple script can be written to use sed (or similar) to
replace the relevant parts for those users that would be affected (at
least for those that are in the layer index and update regularly).

Thanks,
Jon

---

Originally sent as a RFC in
https://lists.openembedded.org/g/openembedded-core/message/142324

Given the generally positive feedback, sending as a patch series.
Keeping the "hard fail" of the file removal (per Richards comment in
https://lists.openembedded.org/g/openembedded-core/message/142356).
Only difference of note is the removal of the "arm64: set BASE_LIB to
lib64", as there needs to be more investigation (see
https://lists.openembedded.org/g/openembedded-core/message/142414).


Jon Mason (5):
  arch-armv8-2a.inc: Add Cortex-A55 tunings
  arch-armv8a.inc: Add existing tunings
  qemuarm64: change tuning
  arch-armv8a.inc: Add tunes for supported ARMv8a cores
  arch-armv8-2a.inc: Add tunes for supported ARMv8.2a cores

 .../machine/include/arm/arch-armv8-2a.inc | 175 ++-
 meta/conf/machine/include/arm/arch-armv8a.inc | 206 +-
 meta/conf/machine/include/tune-cortexa32.inc  |  18 --
 meta/conf/machine/include/tune-cortexa35.inc  |  17 --
 meta/conf/machine/include/tune-cortexa53.inc  |  18 --
 meta/conf/machine/include/tune-cortexa55.inc  |  13 --
 .../include/tune-cortexa57-cortexa53.inc  |  15 --
 meta/conf/machine/include/tune-cortexa57.inc  |  17 --
 .../include/tune-cortexa72-cortexa53.inc  |  20 --
 meta/conf/machine/include/tune-cortexa72.inc  |  13 --
 .../include/tune-cortexa73-cortexa53.inc  |  20 --
 meta/conf/machine/include/tune-thunderx.inc   |  19 --
 meta/conf/machine/qemuarm64.conf  |   3 +-
 13 files changed, 371 insertions(+), 183 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-cortexa32.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa35.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa53.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa55.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa57-cortexa53.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa57.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa72-cortexa53.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa72.inc
 delete mode 100644 meta/conf/machine/include/tune-cortexa73-cortexa53.inc
 delete mode 100644 meta/conf/machine/include/tune-thunderx.inc

-- 
2.20.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142532): 
https://lists.openembedded.org/g/openembedded-core/message/142532
Mute This Topic: https://lists.openembedded.org/mt/76844469/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core][dunfell 12/24] systemd-serialgetty: Fix sed expression quoting

[Steve Sakoman]

In reviewing new master branch commits this morning I see that this
patch introduces a bug and a fix patch has been merged.

I will drop this patch from the final pull request and will submit it
next week along with the fix (systemd-serialgetty: Replace sed quoting
using ' with " to allow var expansion)

Steve

On Mon, Sep 14, 2020 at 4:12 AM Steve Sakoman via
lists.openembedded.org 
wrote:
>
> From: Rahul Kumar 
>
> Fix sed: -e expression #1, char 13: unterminated `s' command
>
> Error Message:
> | NOTE: Installed into sysroot: []
> | NOTE: Skipping as already exists in sysroot: ['pseudo-native', 'glibc', 
> 'patch-native', 'quilt-native', 'gcc-cross-arm', 'gcc-runtime', 
> 'linux-libc-headers', 'libgcc', 'flex-native', 'xz-native', 'libtool-native', 
> 'automake-native', 'binutils-cross-arm', 'zlib-native', 'mpfr-native', 
> 'texinfo-dummy-native', 'autoconf-native', 'libmpc-native', 
> 'gnu-config-native', 'gmp-native', 'attr-native', 'm4-native', 
> 'gettext-minimal-native']
> | DEBUG: Python function extend_recipe_sysroot finished
> | DEBUG: Executing shell function do_install
> | sed: -e expression #1, char 13: unterminated `s' command
> | WARNING: exit code 1 from a shell command.
> | ERROR: Execution of 
> '/opt/Projects/poky/build/tmp/work/qemux86_64-poky-linux/systemd-serialgetty/1.0-r5/temp/run.do_install.11228'
>  failed with exit code 1:
> | sed: -e expression #1, char 13: unterminated `s' command
> | WARNING: exit code 1 from a shell command.
> |
>
> To Fix this Issue using the strong (single quote) character in sed command.
> It is recommend to use quotes. If we have meta-characters in the command, 
> quotes are necessary.
>
> Signed-off-by: Rahul Kumar 
> Signed-off-by: Richard Purdie 
> (cherry picked from commit e2fea05e150dcfec4b7dfbd8edddb53897026bf9)
> Signed-off-by: Steve Sakoman 
> ---
>  meta/recipes-core/systemd/systemd-serialgetty.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/systemd/systemd-serialgetty.bb 
> b/meta/recipes-core/systemd/systemd-serialgetty.bb
> index 044c6c5b67..059fccc2b6 100644
> --- a/meta/recipes-core/systemd/systemd-serialgetty.bb
> +++ b/meta/recipes-core/systemd/systemd-serialgetty.bb
> @@ -21,7 +21,7 @@ do_install() {
> install -d ${D}${systemd_unitdir}/system/
> install -d 
> ${D}${sysconfdir}/systemd/system/getty.target.wants/
> install -m 0644 ${WORKDIR}/serial-getty@.service 
> ${D}${systemd_unitdir}/system/
> -   sed -i -e s/\@BAUDRATE\@/$default_baudrate/g 
> ${D}${systemd_unitdir}/system/serial-getty@.service
> +   sed -i -e 's/\@BAUDRATE\@/$default_baudrate/g' 
> ${D}${systemd_unitdir}/system/serial-getty@.service
>
> tmp="${SERIAL_CONSOLES}"
> for entry in $tmp ; do
> --
> 2.17.1
>
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142531): 
https://lists.openembedded.org/g/openembedded-core/message/142531
Mute This Topic: https://lists.openembedded.org/mt/76843324/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 24/24] cve-check: avoid FileNotFoundError if no do_cve_check task has run

[Steve Sakoman]

From: Chris Laplante 

For example, if you just run 'bitbake cve-update-db-native' in a clean
build system, |cve_tmp_file| won't exist yet.

Signed-off-by: Chris Laplante 
Signed-off-by: Richard Purdie 
(cherry picked from commit dd4473f3d8e1c1a587b6de660775e4b46ddc5fad)
Signed-off-by: Steve Sakoman 
---
 meta/classes/cve-check.bbclass | 13 +++--
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 35b7d0f298..17f64a8a9c 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -63,14 +63,15 @@ python cve_save_summary_handler () {
 timestamp = datetime.datetime.now().strftime('%Y%m%d%H%M%S')
 cve_summary_file = os.path.join(cvelogpath, "%s-%s.txt" % 
(cve_summary_name, timestamp))
 
-shutil.copyfile(cve_tmp_file, cve_summary_file)
+if os.path.exists(cve_tmp_file):
+shutil.copyfile(cve_tmp_file, cve_summary_file)
 
-if cve_summary_file and os.path.exists(cve_summary_file):
-cvefile_link = os.path.join(cvelogpath, cve_summary_name)
+if cve_summary_file and os.path.exists(cve_summary_file):
+cvefile_link = os.path.join(cvelogpath, cve_summary_name)
 
-if os.path.exists(os.path.realpath(cvefile_link)):
-os.remove(cvefile_link)
-os.symlink(os.path.basename(cve_summary_file), cvefile_link)
+if os.path.exists(os.path.realpath(cvefile_link)):
+os.remove(cvefile_link)
+os.symlink(os.path.basename(cve_summary_file), cvefile_link)
 }
 
 addhandler cve_save_summary_handler
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142530): 
https://lists.openembedded.org/g/openembedded-core/message/142530
Mute This Topic: https://lists.openembedded.org/mt/76843068/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 18/24] cmake: whitelist CVE-2016-10642

[Steve Sakoman]

From: Ross Burton 

This CVE is specific to the npm package that can install cmake, so isn't
relevant to our cmake recipe.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
(cherry picked from commit 8e74ed809ec4c1f61264ecf5be4bc319e5e07766)
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/cmake/cmake.inc | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-devtools/cmake/cmake.inc 
b/meta/recipes-devtools/cmake/cmake.inc
index 09949b566c..a2c7d513b3 100644
--- a/meta/recipes-devtools/cmake/cmake.inc
+++ b/meta/recipes-devtools/cmake/cmake.inc
@@ -26,3 +26,7 @@ SRC_URI[md5sum] = "d86ccaf3d2462b6b5947919abe5b9f15"
 SRC_URI[sha256sum] = 
"5f760b50b8ecc9c0c37135fae5fbf00a2fef617059aa9d61c1bb91653e5a8bfc"
 
 UPSTREAM_CHECK_REGEX = "cmake-(?P\d+(\.\d+)+)\.tar"
+
+# This is specific to the npm package that installs cmake, so isn't
+# relevant to OpenEmbedded
+CVE_CHECK_WHITELIST += "CVE-2016-10642"
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142524): 
https://lists.openembedded.org/g/openembedded-core/message/142524
Mute This Topic: https://lists.openembedded.org/mt/76843056/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 21/24] cve-update-db-native: add progress handler

[Steve Sakoman]

From: Chris Laplante 

Signed-off-by: Chris Laplante 
Signed-off-by: Richard Purdie 
(cherry picked from commit 79ae2e82b8ec11578177f428060b568d6c7d44ca)
Signed-off-by: Steve Sakoman 
---
 .../recipes-core/meta/cve-update-db-native.bb | 90 ++-
 1 file changed, 47 insertions(+), 43 deletions(-)

diff --git a/meta/recipes-core/meta/cve-update-db-native.bb 
b/meta/recipes-core/meta/cve-update-db-native.bb
index 32d6dbdffc..2221825bf8 100644
--- a/meta/recipes-core/meta/cve-update-db-native.bb
+++ b/meta/recipes-core/meta/cve-update-db-native.bb
@@ -29,6 +29,7 @@ python do_populate_cve_db() {
 Update NVD database with json data feed
 """
 import bb.utils
+import bb.progress
 import sqlite3, urllib, urllib.parse, shutil, gzip
 from datetime import date
 
@@ -60,54 +61,57 @@ python do_populate_cve_db() {
 
 initialize_db(c)
 
-for year in range(YEAR_START, date.today().year + 1):
-year_url = BASE_URL + str(year)
-meta_url = year_url + ".meta"
-json_url = year_url + ".json.gz"
+with bb.progress.ProgressHandler(d) as ph:
+total_years = date.today().year + 1 - YEAR_START
+for i, year in enumerate(range(YEAR_START, date.today().year + 1)):
+ph.update((float(i + 1) / total_years) * 100)
+year_url = BASE_URL + str(year)
+meta_url = year_url + ".meta"
+json_url = year_url + ".json.gz"
 
-# Retrieve meta last modified date
-try:
-response = urllib.request.urlopen(meta_url)
-except urllib.error.URLError as e:
-cve_f.write('Warning: CVE db update error, Unable to fetch CVE 
data.\n\n')
-bb.warn("Failed to fetch CVE data (%s)" % e.reason)
-return
-
-if response:
-for l in response.read().decode("utf-8").splitlines():
-key, value = l.split(":", 1)
-if key == "lastModifiedDate":
-last_modified = value
-break
-else:
-bb.warn("Cannot parse CVE metadata, update failed")
-return
-
-# Compare with current db last modified date
-c.execute("select DATE from META where YEAR = ?", (year,))
-meta = c.fetchone()
-if not meta or meta[0] != last_modified:
-# Clear products table entries corresponding to current year
-c.execute("delete from PRODUCTS where ID like ?", ('CVE-%d%%' % 
year,))
-
-# Update db with current year json file
+# Retrieve meta last modified date
 try:
-response = urllib.request.urlopen(json_url)
-if response:
-update_db(c, 
gzip.decompress(response.read()).decode('utf-8'))
-c.execute("insert or replace into META values (?, ?)", [year, 
last_modified])
+response = urllib.request.urlopen(meta_url)
 except urllib.error.URLError as e:
-cve_f.write('Warning: CVE db update error, CVE data is 
outdated.\n\n')
-bb.warn("Cannot parse CVE data (%s), update failed" % e.reason)
+cve_f.write('Warning: CVE db update error, Unable to fetch CVE 
data.\n\n')
+bb.warn("Failed to fetch CVE data (%s)" % e.reason)
 return
 
-# Update success, set the date to cve_check file.
-if year == date.today().year:
-cve_f.write('CVE database update : %s\n\n' % date.today())
-
-cve_f.close()
-conn.commit()
-conn.close()
+if response:
+for l in response.read().decode("utf-8").splitlines():
+key, value = l.split(":", 1)
+if key == "lastModifiedDate":
+last_modified = value
+break
+else:
+bb.warn("Cannot parse CVE metadata, update failed")
+return
+
+# Compare with current db last modified date
+c.execute("select DATE from META where YEAR = ?", (year,))
+meta = c.fetchone()
+if not meta or meta[0] != last_modified:
+# Clear products table entries corresponding to current year
+c.execute("delete from PRODUCTS where ID like ?", ('CVE-%d%%' 
% year,))
+
+# Update db with current year json file
+try:
+response = urllib.request.urlopen(json_url)
+if response:
+update_db(c, 
gzip.decompress(response.read()).decode('utf-8'))
+c.execute("insert or replace into META values (?, ?)", 
[year, last_modified])
+except urllib.error.URLError as e:
+cve_f.write('Warning: CVE db update error, CVE data is 
outdated.\n\n')
+bb.warn("Cannot parse CVE data (%s), update failed" % 
e.reason)
+retu

[OE-core][dunfell 23/24] cve-update-db-native: use context manager for cve_f

[Steve Sakoman]

From: Chris Laplante 

Signed-off-by: Richard Purdie 
(cherry picked from commit ff422652e1b5db62205fafc75ce56bb5951d478d)
Signed-off-by: Steve Sakoman 
---
 meta/recipes-core/meta/cve-update-db-native.bb | 5 +
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/meta/recipes-core/meta/cve-update-db-native.bb 
b/meta/recipes-core/meta/cve-update-db-native.bb
index d22b66f6c7..328f6ab364 100644
--- a/meta/recipes-core/meta/cve-update-db-native.bb
+++ b/meta/recipes-core/meta/cve-update-db-native.bb
@@ -50,8 +50,6 @@ python do_populate_cve_db() {
 except OSError:
 pass
 
-cve_f = open(os.path.join(d.getVar("TMPDIR"), 'cve_check'), 'a')
-
 bb.utils.mkdirhier(db_dir)
 
 # Connect to database
@@ -60,7 +58,7 @@ python do_populate_cve_db() {
 
 initialize_db(c)
 
-with bb.progress.ProgressHandler(d) as ph:
+with bb.progress.ProgressHandler(d) as ph, 
open(os.path.join(d.getVar("TMPDIR"), 'cve_check'), 'a') as cve_f:
 total_years = date.today().year + 1 - YEAR_START
 for i, year in enumerate(range(YEAR_START, date.today().year + 1)):
 ph.update((float(i + 1) / total_years) * 100)
@@ -108,7 +106,6 @@ python do_populate_cve_db() {
 if year == date.today().year:
 cve_f.write('CVE database update : %s\n\n' % date.today())
 
-cve_f.close()
 conn.commit()
 conn.close()
 }
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142529): 
https://lists.openembedded.org/g/openembedded-core/message/142529
Mute This Topic: https://lists.openembedded.org/mt/76843067/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 22/24] cve-check/cve-update-db-native: use lockfile to fix usage under multiconfig

[Steve Sakoman]

From: Chris Laplante 

Previously CVE_CHECK_DB_FILE / CVE_CHECK_DB_DIR was the same across
multiconfigs which led to a race condition wherein multiple
cve-update-db-native:do_populate_cve_db tasks could attempt to write to
the same sqlite database. This led to the following task failure:

Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:do_populate_cve_db(d)
 0003:
File: 
'/mnt/data/agent/work/74f119cccb44f133/yocto/sources/poky/meta/recipes-core/meta/cve-update-db-native.bb',
 lineno: 103, function: do_populate_cve_db
 0099:if year == date.today().year:
 0100:cve_f.write('CVE database update : %s\n\n' % 
date.today())
 0101:
 0102:cve_f.close()
 *** 0103:conn.commit()
 0104:conn.close()
 0105:}
 0106:
 0107:def initialize_db(c):
Exception: sqlite3.OperationalError: disk I/O error

Use a lockfile to ensure multiple tasks don't step over each other.

Signed-off-by: Chris Laplante 
Signed-off-by: Richard Purdie 
(cherry picked from commit 24e9380643a2ae3fcae193519cb64aedaf682153)
Signed-off-by: Steve Sakoman 
---
 meta/classes/cve-check.bbclass | 1 +
 meta/recipes-core/meta/cve-update-db-native.bb | 5 +++--
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 0889e7544a..35b7d0f298 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -27,6 +27,7 @@ CVE_VERSION ??= "${PV}"
 
 CVE_CHECK_DB_DIR ?= "${DL_DIR}/CVE_CHECK"
 CVE_CHECK_DB_FILE ?= "${CVE_CHECK_DB_DIR}/nvdcve_1.1.db"
+CVE_CHECK_DB_FILE_LOCK ?= "${CVE_CHECK_DB_FILE}.lock"
 
 CVE_CHECK_LOG ?= "${T}/cve.log"
 CVE_CHECK_TMP_FILE ?= "${TMPDIR}/cve_check"
diff --git a/meta/recipes-core/meta/cve-update-db-native.bb 
b/meta/recipes-core/meta/cve-update-db-native.bb
index 2221825bf8..d22b66f6c7 100644
--- a/meta/recipes-core/meta/cve-update-db-native.bb
+++ b/meta/recipes-core/meta/cve-update-db-native.bb
@@ -52,8 +52,7 @@ python do_populate_cve_db() {
 
 cve_f = open(os.path.join(d.getVar("TMPDIR"), 'cve_check'), 'a')
 
-if not os.path.isdir(db_dir):
-os.mkdir(db_dir)
+bb.utils.mkdirhier(db_dir)
 
 # Connect to database
 conn = sqlite3.connect(db_file)
@@ -114,6 +113,8 @@ python do_populate_cve_db() {
 conn.close()
 }
 
+do_populate_cve_db[lockfiles] += "${CVE_CHECK_DB_FILE_LOCK}"
+
 def initialize_db(c):
 c.execute("CREATE TABLE IF NOT EXISTS META (YEAR INTEGER UNIQUE, DATE 
TEXT)")
 
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142528): 
https://lists.openembedded.org/g/openembedded-core/message/142528
Mute This Topic: https://lists.openembedded.org/mt/76843064/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 11/24] oe-publish-sdk: fix layers init via ssh

[Steve Sakoman]

From: Adrian Freihofer 

Escaping does not work in my use case. It must be escaped for
python, ssh and shell as well as for different versions of echo.
Let's try it a little less elegant, but hopefully more reliable.

Signed-off-by: Adrian Freihofer 
Signed-off-by: Richard Purdie 
(cherry picked from commit 5cc1ae332eb6b05d83802c8d64ab2767c7079412)
Signed-off-by: Steve Sakoman 
---
 scripts/oe-publish-sdk | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/oe-publish-sdk b/scripts/oe-publish-sdk
index 4b70f436b1..19a5d69864 100755
--- a/scripts/oe-publish-sdk
+++ b/scripts/oe-publish-sdk
@@ -106,7 +106,7 @@ def publish(args):
 if not is_remote:
 cmd = 'set -e; mkdir -p %s/layers; cd %s/layers; if [ ! -e .git ]; 
then git init .; cp .git/hooks/post-update.sample .git/hooks/post-commit; echo 
"*.pyc\n*.pyo\npyshtables.py" > .gitignore; fi; git add -A .; git config 
user.email "o...@oe.oe" && git config user.name "OE" && git commit -q -m "init 
repo" || true' % (destination, destination)
 else:
-cmd = "ssh %s 'set -e; mkdir -p %s/layers; cd %s/layers; if [ ! -e 
.git ]; then git init .; cp .git/hooks/post-update.sample 
.git/hooks/post-commit; echo '*.pyc\n*.pyo\npyshtables.py' > .gitignore; fi; 
git add -A .; git config user.email 'o...@oe.oe' && git config user.name 'OE' 
&& git commit -q -m \"init repo\" || true'" % (host, destdir, destdir)
+cmd = "ssh %s 'set -e; mkdir -p %s/layers; cd %s/layers; if [ ! -e 
.git ]; then git init .; cp .git/hooks/post-update.sample 
.git/hooks/post-commit; echo '*.pyc' > .gitignore; echo '*.pyo' >> .gitignore; 
echo 'pyshtables.py' >> .gitignore; fi; git add -A .; git config user.email 
'o...@oe.oe' && git config user.name 'OE' && git commit -q -m \"init repo\" || 
true'" % (host, destdir, destdir)
 ret = subprocess.call(cmd, shell=True)
 if ret == 0:
 logger.info('SDK published successfully')
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142517): 
https://lists.openembedded.org/g/openembedded-core/message/142517
Mute This Topic: https://lists.openembedded.org/mt/76843042/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 09/24] runqemu: Add a hook to allow it to renice

[Steve Sakoman]

From: Richard Purdie 

We have an issue where qemu is being starved of resources on our autobuilders.
We can't raise its priority without special capacilties, therefore add a hook
which if present can allow this to happen using an executable
"~/runqemu-renice".

Signed-off-by: Richard Purdie 
(cherry picked from commit 141a3c9ce93bc3d526303021ecf0460c6e9fea8a)
Signed-off-by: Steve Sakoman 
---
 scripts/runqemu | 5 +
 1 file changed, 5 insertions(+)

diff --git a/scripts/runqemu b/scripts/runqemu
index b24ac1c804..cc87ea871a 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -1507,6 +1507,11 @@ def main():
 try:
 config = BaseConfig()
 
+renice = os.path.expanduser("~/bin/runqemu-renice")
+if os.path.exists(renice):
+logger.info('Using %s to renice' % renice)
+subprocess.check_call([renice, str(os.getpid())])
+
 def sigterm_handler(signum, frame):
 logger.info("SIGTERM received")
 os.kill(config.qemupid, signal.SIGTERM)
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142515): 
https://lists.openembedded.org/g/openembedded-core/message/142515
Mute This Topic: https://lists.openembedded.org/mt/76843037/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 20/24] cve-check.bbclass: always save cve report

[Steve Sakoman]

From: akuster 

The cve-check file should be saved always, it has good info.

Put a copy in the log dir as cve-summary with symlinks to latest run.

[Yocto #13974]

Signed-off-by: Armin Kuster 
Signed-off-by: Richard Purdie 
(cherry picked from commit 859849c7b594d844819ad8c3f7d8325388d94b93)
Signed-off-by: Steve Sakoman 
---
 meta/classes/cve-check.bbclass | 32 
 1 file changed, 32 insertions(+)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 514897e8b8..0889e7544a 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -30,6 +30,9 @@ CVE_CHECK_DB_FILE ?= "${CVE_CHECK_DB_DIR}/nvdcve_1.1.db"
 
 CVE_CHECK_LOG ?= "${T}/cve.log"
 CVE_CHECK_TMP_FILE ?= "${TMPDIR}/cve_check"
+CVE_CHECK_SUMMARY_DIR ?= "${LOG_DIR}/cve"
+CVE_CHECK_SUMMARY_FILE_NAME ?= "cve-summary"
+CVE_CHECK_SUMMARY_FILE ?= 
"${CVE_CHECK_SUMMARY_DIR}/${CVE_CHECK_SUMMARY_FILE_NAME}"
 
 CVE_CHECK_DIR ??= "${DEPLOY_DIR}/cve"
 CVE_CHECK_MANIFEST ?= 
"${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.cve"
@@ -46,6 +49,32 @@ CVE_CHECK_PN_WHITELIST ?= ""
 # 
 CVE_CHECK_WHITELIST ?= ""
 
+python cve_save_summary_handler () {
+import shutil
+import datetime
+
+cve_tmp_file = d.getVar("CVE_CHECK_TMP_FILE")
+
+cve_summary_name = d.getVar("CVE_CHECK_SUMMARY_FILE_NAME")
+cvelogpath = d.getVar("CVE_CHECK_SUMMARY_DIR")
+bb.utils.mkdirhier(cvelogpath)
+
+timestamp = datetime.datetime.now().strftime('%Y%m%d%H%M%S')
+cve_summary_file = os.path.join(cvelogpath, "%s-%s.txt" % 
(cve_summary_name, timestamp))
+
+shutil.copyfile(cve_tmp_file, cve_summary_file)
+
+if cve_summary_file and os.path.exists(cve_summary_file):
+cvefile_link = os.path.join(cvelogpath, cve_summary_name)
+
+if os.path.exists(os.path.realpath(cvefile_link)):
+os.remove(cvefile_link)
+os.symlink(os.path.basename(cve_summary_file), cvefile_link)
+}
+
+addhandler cve_save_summary_handler
+cve_save_summary_handler[eventmask] = "bb.event.BuildCompleted"
+
 python do_cve_check () {
 """
 Check recipe for patched and unpatched CVEs
@@ -331,5 +360,8 @@ def cve_write_data(d, patched, unpatched, whitelisted, 
cve_data):
 f.write(write_string)
 
 if d.getVar("CVE_CHECK_CREATE_MANIFEST") == "1":
+cvelogpath = d.getVar("CVE_CHECK_SUMMARY_DIR")
+bb.utils.mkdirhier(cvelogpath)
+
 with open(d.getVar("CVE_CHECK_TMP_FILE"), "a") as f:
 f.write("%s" % write_string)
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142526): 
https://lists.openembedded.org/g/openembedded-core/message/142526
Mute This Topic: https://lists.openembedded.org/mt/76843059/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 05/24] rpcbind: Use update-alternatives for rpcinfo

[Steve Sakoman]

From: Khem Raj 

rpcinfo is also provided vy netkit in meta-networking

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie 
(cherry picked from commit 28183dfd7446de9113773ab89edd0afb4ab82f7e)
Signed-off-by: Steve Sakoman 
---
 meta/recipes-extended/rpcbind/rpcbind_1.2.5.bb | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/rpcbind/rpcbind_1.2.5.bb 
b/meta/recipes-extended/rpcbind/rpcbind_1.2.5.bb
index aff00e56e6..ec8f9e48b2 100644
--- a/meta/recipes-extended/rpcbind/rpcbind_1.2.5.bb
+++ b/meta/recipes-extended/rpcbind/rpcbind_1.2.5.bb
@@ -19,7 +19,7 @@ SRC_URI = 
"${SOURCEFORGE_MIRROR}/rpcbind/rpcbind-${PV}.tar.bz2 \
 SRC_URI[md5sum] = "ed46f09b9c0fa2d49015f6431bc5ea7b"
 SRC_URI[sha256sum] = 
"2ce360683963b35c19c43f0ee2c7f18aa5b81ef41c3fdbd15ffcb00b8bffda7a"
 
-inherit autotools update-rc.d systemd pkgconfig
+inherit autotools update-rc.d systemd pkgconfig update-alternatives
 
 PACKAGECONFIG ??= "tcp-wrappers"
 PACKAGECONFIG[tcp-wrappers] = "--enable-libwrap,--disable-libwrap,tcp-wrappers"
@@ -50,3 +50,6 @@ do_install_append () {
${WORKDIR}/init.d > ${D}${sysconfdir}/init.d/rpcbind
chmod 0755 ${D}${sysconfdir}/init.d/rpcbind
 }
+
+ALTERNATIVE_${PN} = "rpcinfo"
+ALTERNATIVE_LINK_NAME[rpcinfo] = "${bindir}/rpcinfo"
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142511): 
https://lists.openembedded.org/g/openembedded-core/message/142511
Mute This Topic: https://lists.openembedded.org/mt/76843028/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 16/24] ell: update to 0.33

[Steve Sakoman]

From: Oleksandr Kravchuk 

Changelog
- Fix issue with uintset and number of bytes copied.
- Fix issue with overflow in DHCP lease T2 computation.
- Fix issue with side channel leak in l_ecc_scalar_new.
- Fix issue with missing MSG_MORE in l_cipher_set_iv.
- Add support for DHCP v6 client implementation.

Signed-off-by: Oleksandr Kravchuk 
Signed-off-by: Richard Purdie 
(cherry picked from commit 3ad8ca257d40f5041b3ec167e4117c687da448a9)
Signed-off-by: Steve Sakoman 
---
 meta/recipes-core/ell/{ell_0.32.bb => ell_0.33.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-core/ell/{ell_0.32.bb => ell_0.33.bb} (89%)

diff --git a/meta/recipes-core/ell/ell_0.32.bb 
b/meta/recipes-core/ell/ell_0.33.bb
similarity index 89%
rename from meta/recipes-core/ell/ell_0.32.bb
rename to meta/recipes-core/ell/ell_0.33.bb
index 07dc4d4cbb..2fa05104fb 100644
--- a/meta/recipes-core/ell/ell_0.32.bb
+++ b/meta/recipes-core/ell/ell_0.33.bb
@@ -14,7 +14,7 @@ DEPENDS = "dbus"
 inherit autotools pkgconfig
 
 SRC_URI = 
"https://mirrors.edge.kernel.org/pub/linux/libs/${BPN}/${BPN}-${PV}.tar.xz";
-SRC_URI[sha256sum] = 
"42fdb9e24ff561a101389d51445cab1ff7d55f5385dc22a05b0493088cf99e30"
+SRC_URI[sha256sum] = 
"d9e40e641164150394b74b719b9726fc734f24b2cde679cf5f3be6915c34eded"
 
 do_configure_prepend () {
 mkdir -p ${S}/build-aux
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142522): 
https://lists.openembedded.org/g/openembedded-core/message/142522
Mute This Topic: https://lists.openembedded.org/mt/76843053/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 12/24] systemd-serialgetty: Fix sed expression quoting

[Steve Sakoman]

From: Rahul Kumar 

Fix sed: -e expression #1, char 13: unterminated `s' command

Error Message:
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['pseudo-native', 'glibc', 
'patch-native', 'quilt-native', 'gcc-cross-arm', 'gcc-runtime', 
'linux-libc-headers', 'libgcc', 'flex-native', 'xz-native', 'libtool-native', 
'automake-native', 'binutils-cross-arm', 'zlib-native', 'mpfr-native', 
'texinfo-dummy-native', 'autoconf-native', 'libmpc-native', 
'gnu-config-native', 'gmp-native', 'attr-native', 'm4-native', 
'gettext-minimal-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| sed: -e expression #1, char 13: unterminated `s' command
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of 
'/opt/Projects/poky/build/tmp/work/qemux86_64-poky-linux/systemd-serialgetty/1.0-r5/temp/run.do_install.11228'
 failed with exit code 1:
| sed: -e expression #1, char 13: unterminated `s' command
| WARNING: exit code 1 from a shell command.
|

To Fix this Issue using the strong (single quote) character in sed command.
It is recommend to use quotes. If we have meta-characters in the command, 
quotes are necessary.

Signed-off-by: Rahul Kumar 
Signed-off-by: Richard Purdie 
(cherry picked from commit e2fea05e150dcfec4b7dfbd8edddb53897026bf9)
Signed-off-by: Steve Sakoman 
---
 meta/recipes-core/systemd/systemd-serialgetty.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/systemd/systemd-serialgetty.bb 
b/meta/recipes-core/systemd/systemd-serialgetty.bb
index 044c6c5b67..059fccc2b6 100644
--- a/meta/recipes-core/systemd/systemd-serialgetty.bb
+++ b/meta/recipes-core/systemd/systemd-serialgetty.bb
@@ -21,7 +21,7 @@ do_install() {
install -d ${D}${systemd_unitdir}/system/
install -d ${D}${sysconfdir}/systemd/system/getty.target.wants/
install -m 0644 ${WORKDIR}/serial-getty@.service 
${D}${systemd_unitdir}/system/
-   sed -i -e s/\@BAUDRATE\@/$default_baudrate/g 
${D}${systemd_unitdir}/system/serial-getty@.service
+   sed -i -e 's/\@BAUDRATE\@/$default_baudrate/g' 
${D}${systemd_unitdir}/system/serial-getty@.service
 
tmp="${SERIAL_CONSOLES}"
for entry in $tmp ; do
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142518): 
https://lists.openembedded.org/g/openembedded-core/message/142518
Mute This Topic: https://lists.openembedded.org/mt/76843043/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 07/24] insane: only load real files as ELF

[Steve Sakoman]

From: Ross Burton 

The file path checks are passed an ELF object if the file is an ELF. It
doesn't make a lot of sense to load symlinks to ELFs as if they're in
the same package then the real file will be checked too.

This should speed up do_package_qa slightly as libraries won't be
scanned repeatedly.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
(cherry picked from commit c63af30d3b6350361daff94a59d4f14d7c5395e1)
Signed-off-by: Steve Sakoman 
---
 meta/classes/insane.bbclass | 13 +++--
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index c595080bdf..46d386a38b 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -708,12 +708,13 @@ def package_qa_walk(warnfuncs, errorfuncs, package, d):
 warnings = {}
 errors = {}
 for path in pkgfiles[package]:
-elf = oe.qa.ELFFile(path)
-try:
-elf.open()
-except (IOError, oe.qa.NotELFFileError):
-# IOError can happen if the packaging control files disappear,
-elf = None
+elf = None
+if os.path.isfile(path):
+elf = oe.qa.ELFFile(path)
+try:
+elf.open()
+except oe.qa.NotELFFileError:
+elf = None
 for func in warnfuncs:
 func(path, package, d, elf, warnings)
 for func in errorfuncs:
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142513): 
https://lists.openembedded.org/g/openembedded-core/message/142513
Mute This Topic: https://lists.openembedded.org/mt/76843034/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 06/24] gdk-pixbuf: add tests PACKAGECONFIG

[Steve Sakoman]

From: Ross Burton 

Convert the installed-tests toggle from simply respecting PTEST_ENABLED
to a PACKAGECONFIG, so that it can be turned on/off in the usual manner.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
(cherry picked from commit 08e61ffae6056055b56f93678bcbb9fd71f3303e)
Signed-off-by: Steve Sakoman 
---
 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.40.0.bb | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.40.0.bb 
b/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.40.0.bb
index d0df5015a5..0405fa78b5 100644
--- a/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.40.0.bb
+++ b/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.40.0.bb
@@ -40,20 +40,20 @@ inherit meson pkgconfig gettext pixbufcache ptest-gnome 
upstream-version-is-even
 
 GIR_MESON_OPTION = 'gir'
 
-EXTRA_OEMESON_append = " ${@bb.utils.contains('PTEST_ENABLED', '1', 
'-Dinstalled_tests=true', '-Dinstalled_tests=false', d)}"
-
 LIBV = "2.10.0"
 
 GDK_PIXBUF_LOADERS ?= "png jpeg"
 
-PACKAGECONFIG = "${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)} 
${GDK_PIXBUF_LOADERS}"
+PACKAGECONFIG = "${GDK_PIXBUF_LOADERS} \
+ ${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)} \
+ ${@bb.utils.contains('PTEST_ENABLED', '1', 'tests', '', d)}"
 PACKAGECONFIG_class-native = "${GDK_PIXBUF_LOADERS}"
 
 PACKAGECONFIG[png] = "-Dpng=true,-Dpng=false,libpng"
 PACKAGECONFIG[jpeg] = "-Djpeg=true,-Djpeg=false,jpeg"
 PACKAGECONFIG[tiff] = "-Dtiff=true,-Dtiff=false,tiff"
 PACKAGECONFIG[jpeg2000] = "-Djasper=true,-Djasper=false,jasper"
-
+PACKAGECONFIG[tests] = "-Dinstalled_tests=true,-Dinstalled_tests=false"
 PACKAGECONFIG[x11] = "-Dx11=true,-Dx11=false,virtual/libx11"
 
 PACKAGES =+ "${PN}-xlib"
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142512): 
https://lists.openembedded.org/g/openembedded-core/message/142512
Mute This Topic: https://lists.openembedded.org/mt/76843030/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 17/24] curl: add vendors to CVE_PRODUCT to exclude false positives

[Steve Sakoman]

From: Ross Burton 

To avoid false positives (such as CVE-2010-0734, rubygems:curl), expand
the CVE_PRODUCT list to include all the vendors that have been used.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
(cherry picked from commit bb265122cccea9466405fdd924ad10ce8cda0dec)
Signed-off-by: Steve Sakoman 
---
 meta/recipes-support/curl/curl_7.69.1.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-support/curl/curl_7.69.1.bb 
b/meta/recipes-support/curl/curl_7.69.1.bb
index 8b5170f021..dfcd533c80 100644
--- a/meta/recipes-support/curl/curl_7.69.1.bb
+++ b/meta/recipes-support/curl/curl_7.69.1.bb
@@ -14,7 +14,9 @@ SRC_URI = "http://curl.haxx.se/download/curl-${PV}.tar.bz2 \
 SRC_URI[md5sum] = "ec5fc263f898a3dfef08e805f1ecca42"
 SRC_URI[sha256sum] = 
"2ff5e5bd507adf6aa88ff4bbafd4c7af464867ffb688be93b9930717a56c4de8"
 
-CVE_PRODUCT = "curl libcurl"
+# Curl has used many names over the years...
+CVE_PRODUCT = "haxx:curl haxx:libcurl curl:curl curl:libcurl libcurl:libcurl 
daniel_stenberg:curl"
+
 inherit autotools pkgconfig binconfig multilib_header
 
 PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'ipv6', d)} gnutls 
libidn proxy threaded-resolver verbose zlib"
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142523): 
https://lists.openembedded.org/g/openembedded-core/message/142523
Mute This Topic: https://lists.openembedded.org/mt/76843054/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 15/24] gnutls: CVE-2020-24659

[Steve Sakoman]

From: Zhixiong Chi 

Backport the CVE patch from the usptream:
https://gitlab.com/gnutls/gnutls.git
commit 29ee67c205855e848a0a26e6d0e4f65b6b943e0a

Signed-off-by: Zhixiong Chi 
Signed-off-by: Richard Purdie 
(cherry picked from commit 84b1bc500e318657cb7a8a189b59cc63bc91dca3)
Signed-off-by: Steve Sakoman 
---
 .../gnutls/gnutls/CVE-2020-24659.patch| 117 ++
 meta/recipes-support/gnutls/gnutls_3.6.14.bb  |   1 +
 2 files changed, 118 insertions(+)
 create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2020-24659.patch

diff --git a/meta/recipes-support/gnutls/gnutls/CVE-2020-24659.patch 
b/meta/recipes-support/gnutls/gnutls/CVE-2020-24659.patch
new file mode 100644
index 00..1702325e66
--- /dev/null
+++ b/meta/recipes-support/gnutls/gnutls/CVE-2020-24659.patch
@@ -0,0 +1,117 @@
+From 29ee67c205855e848a0a26e6d0e4f65b6b943e0a Mon Sep 17 00:00:00 2001
+From: Daiki Ueno 
+Date: Sat, 22 Aug 2020 17:19:39 +0200
+Subject: [PATCH] handshake: reject no_renegotiation alert if handshake is
+ incomplete
+
+If the initial handshake is incomplete and the server sends a
+no_renegotiation alert, the client should treat it as a fatal error
+even if its level is warning.  Otherwise the same handshake
+state (e.g., DHE parameters) are reused in the next gnutls_handshake
+call, if it is called in the loop idiom:
+
+  do {
+  ret = gnutls_handshake(session);
+  } while (ret < 0 && gnutls_error_is_fatal(ret) == 0);
+
+Signed-off-by: Daiki Ueno 
+CVE: CVE-2020-24659
+Upstream-Status: Backport [https://gitlab.com/gnutls/gnutls.git]
+Signed-off-by: Zhixiong Chi 
+---
+ lib/gnutls_int.h  |   1 +
+ lib/handshake.c   |  48 +-
+ 2 files changed, 36 insertions(+), 13 deletions(-)
+
+diff --git a/lib/gnutls_int.h b/lib/gnutls_int.h
+index bb6c19713..31cec5c0c 100644
+--- a/lib/gnutls_int.h
 b/lib/gnutls_int.h
+@@ -1370,6 +1370,7 @@ typedef struct {
+ #define HSK_RECORD_SIZE_LIMIT_RECEIVED (1<<26) /* server: record_size_limit 
extension was seen but not accepted yet */
+ #define HSK_OCSP_REQUESTED (1<<27) /* server: client requested OCSP stapling 
*/
+ #define HSK_CLIENT_OCSP_REQUESTED (1<<28) /* client: server requested OCSP 
stapling */
++#define HSK_SERVER_HELLO_RECEIVED (1<<29) /* client: Server Hello message has 
been received */
+ 
+   /* The hsk_flags are for use within the ongoing handshake;
+* they are reset to zero prior to handshake start by gnutls_handshake. 
*/
+diff --git a/lib/handshake.c b/lib/handshake.c
+index b40f84b3d..ce2d160e2 100644
+--- a/lib/handshake.c
 b/lib/handshake.c
+@@ -2051,6 +2051,8 @@ read_server_hello(gnutls_session_t session,
+   if (ret < 0)
+   return gnutls_assert_val(ret);
+ 
++  session->internals.hsk_flags |= HSK_SERVER_HELLO_RECEIVED;
++
+   return 0;
+ }
+ 
+@@ -2575,16 +2577,42 @@ int gnutls_rehandshake(gnutls_session_t session)
+   return 0;
+ }
+ 
++/* This function checks whether the error code should be treated fatal
++ * or not, and also does the necessary state transition.  In
++ * particular, in the case of a rehandshake abort it resets the
++ * handshake's internal state.
++ */
+ inline static int
+ _gnutls_abort_handshake(gnutls_session_t session, int ret)
+ {
+-  if (((ret == GNUTLS_E_WARNING_ALERT_RECEIVED) &&
+-   (gnutls_alert_get(session) == GNUTLS_A_NO_RENEGOTIATION))
+-  || ret == GNUTLS_E_GOT_APPLICATION_DATA)
+-  return 0;
++  switch (ret) {
++  case GNUTLS_E_WARNING_ALERT_RECEIVED:
++  if (gnutls_alert_get(session) == GNUTLS_A_NO_RENEGOTIATION) {
++  /* The server always toleretes a "no_renegotiation" 
alert. */
++  if (session->security_parameters.entity == 
GNUTLS_SERVER) {
++  STATE = STATE0;
++  return ret;
++  }
++
++  /* The client should tolerete a "no_renegotiation" 
alert only if:
++   * - the initial handshake has completed, or
++   * - a Server Hello is not yet received
++   */
++  if (session->internals.initial_negotiation_completed ||
++  !(session->internals.hsk_flags & 
HSK_SERVER_HELLO_RECEIVED)) {
++  STATE = STATE0;
++  return ret;
++  }
+ 
+-  /* this doesn't matter */
+-  return GNUTLS_E_INTERNAL_ERROR;
++  return gnutls_assert_val(GNUTLS_E_UNEXPECTED_PACKET);
++  }
++  return ret;
++  case GNUTLS_E_GOT_APPLICATION_DATA:
++  STATE = STATE0;
++  return ret;
++  default:
++  return ret;
++  }
+ }
+ 
+ 
+@@ -2747,13 +2774,7 @@ int gnutls_handshake(gnutls_session_t session)
+   }
+ 
+   if (ret < 0) {
+-  /* In the case

[OE-core][dunfell 19/24] libxml2: Fix CVE-2020-24977

[Steve Sakoman]

From: Ovidiu Panait 

GNOME project libxml2 v2.9.10 and earlier have a global Buffer Overflow
vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. The issue has
been fixed in commit 8e7c20a1 (20910-GITv2.9.10-103-g8e7c20a1).

Reference:
https://gitlab.gnome.org/GNOME/libxml2/-/issues/178

Upstream patch:
https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2

Signed-off-by: Ovidiu Panait 
Signed-off-by: Richard Purdie 
(cherry picked from commit 92dc02b8f03f3586de0a2ec1463b189a3918e303)
Signed-off-by: Steve Sakoman 
---
 .../libxml/libxml2/CVE-2020-24977.patch   | 41 +++
 meta/recipes-core/libxml/libxml2_2.9.10.bb|  1 +
 2 files changed, 42 insertions(+)
 create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2020-24977.patch

diff --git a/meta/recipes-core/libxml/libxml2/CVE-2020-24977.patch 
b/meta/recipes-core/libxml/libxml2/CVE-2020-24977.patch
new file mode 100644
index 00..8224346660
--- /dev/null
+++ b/meta/recipes-core/libxml/libxml2/CVE-2020-24977.patch
@@ -0,0 +1,41 @@
+From 50f06b3efb638efb0abd95dc62dca05ae67882c2 Mon Sep 17 00:00:00 2001
+From: Nick Wellnhofer 
+Date: Fri, 7 Aug 2020 21:54:27 +0200
+Subject: [PATCH] Fix out-of-bounds read with 'xmllint --htmlout'
+
+Make sure that truncated UTF-8 sequences don't cause an out-of-bounds
+array access.
+
+Thanks to @SuhwanSong and the Agency for Defense Development (ADD) for
+the report.
+
+Fixes #178.
+
+CVE: CVE-2020-24977
+Upstream-Status: Backport 
[https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2]
+
+Signed-off-by: Ovidiu Panait 
+---
+ xmllint.c | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/xmllint.c b/xmllint.c
+index f6a8e463..c647486f 100644
+--- a/xmllint.c
 b/xmllint.c
+@@ -528,6 +528,12 @@ static void
+ xmlHTMLEncodeSend(void) {
+ char *result;
+ 
++/*
++ * xmlEncodeEntitiesReentrant assumes valid UTF-8, but the buffer might
++ * end with a truncated UTF-8 sequence. This is a hack to at least avoid
++ * an out-of-bounds read.
++ */
++memset(&buffer[sizeof(buffer)-4], 0, 4);
+ result = (char *) xmlEncodeEntitiesReentrant(NULL, BAD_CAST buffer);
+ if (result) {
+   xmlGenericError(xmlGenericErrorContext, "%s", result);
+-- 
+2.17.1
+
diff --git a/meta/recipes-core/libxml/libxml2_2.9.10.bb 
b/meta/recipes-core/libxml/libxml2_2.9.10.bb
index 097aceb2c0..4ebfb9e556 100644
--- a/meta/recipes-core/libxml/libxml2_2.9.10.bb
+++ b/meta/recipes-core/libxml/libxml2_2.9.10.bb
@@ -22,6 +22,7 @@ SRC_URI = 
"http://www.xmlsoft.org/sources/libxml2-${PV}.tar.gz;name=libtar \
file://fix-execution-of-ptests.patch \
file://CVE-2020-7595.patch \
file://CVE-2019-20388.patch \
+   file://CVE-2020-24977.patch \
"
 
 SRC_URI[libtar.md5sum] = "10942a1dc23137a8aa07f0639cbfece5"
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142525): 
https://lists.openembedded.org/g/openembedded-core/message/142525
Mute This Topic: https://lists.openembedded.org/mt/76843058/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 08/24] autoconf: consolidate DEPENDS

[Steve Sakoman]

From: Ross Burton 

Depending on nativesdk- varients in a nativesdk build isn't correct, so
just collapse the DEPENDS down and let bitbake do the right thing (which
is leaving them as -native).

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
(cherry picked from commit 4864167ad4ed4c57e49f2aa5e7c58383bddb052b)
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/autoconf/autoconf.inc | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-devtools/autoconf/autoconf.inc 
b/meta/recipes-devtools/autoconf/autoconf.inc
index 2c87bf8296..36a48d9116 100644
--- a/meta/recipes-devtools/autoconf/autoconf.inc
+++ b/meta/recipes-devtools/autoconf/autoconf.inc
@@ -5,9 +5,8 @@ file that lists the operating system features that the package 
can use, in the f
 LICENSE = "GPLv3"
 HOMEPAGE = "http://www.gnu.org/software/autoconf/";
 SECTION = "devel"
-DEPENDS += "m4-native"
-DEPENDS_class-native = "m4-native gnu-config-native"
-DEPENDS_class-nativesdk = "nativesdk-m4 nativesdk-gnu-config"
+DEPENDS = "m4-native gnu-config-native"
+
 RDEPENDS_${PN} = "m4 gnu-config \
  perl \
  perl-module-bytes \
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142514): 
https://lists.openembedded.org/g/openembedded-core/message/142514
Mute This Topic: https://lists.openembedded.org/mt/76843036/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 13/24] selftest/signing: Ensure build path relocation is safe

[Steve Sakoman]

From: Richard Purdie 

Similarly to 04ee0e8b95cd8ed890374e0007f976684206b630, ensure only full
build paths are replaced in the environment to avoid breaking buildtools.

Signed-off-by: Richard Purdie 
(cherry picked from commit fcd0a9683af1a9155eabbd9056e3b46d4a931b2e)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/selftest/cases/signing.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/cases/signing.py 
b/meta/lib/oeqa/selftest/cases/signing.py
index 202d54994b..a28c7eb19a 100644
--- a/meta/lib/oeqa/selftest/cases/signing.py
+++ b/meta/lib/oeqa/selftest/cases/signing.py
@@ -44,7 +44,9 @@ class Signing(OESelftestTestCase):
 origenv = os.environ.copy()
 
 for e in os.environ:
-if builddir in os.environ[e]:
+if builddir + "/" in os.environ[e]:
+os.environ[e] = os.environ[e].replace(builddir + "/", 
newbuilddir + "/")
+if os.environ[e].endswith(builddir):
 os.environ[e] = os.environ[e].replace(builddir, newbuilddir)
 
 os.chdir(newbuilddir)
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142519): 
https://lists.openembedded.org/g/openembedded-core/message/142519
Mute This Topic: https://lists.openembedded.org/mt/76843044/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 14/24] oeqa/concurrencytest: Improve builddir path manipulations

[Steve Sakoman]

From: Richard Purdie 

Its possible some patterns may cause problems with the current path
manipulations, make a small tweak to try and avoid potential pathname
overlap issues.

Signed-off-by: Richard Purdie 
(cherry picked from commit 889005dc17d3e3b8eadee907ee2c05b8ff613285)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/selftest/context.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/context.py 
b/meta/lib/oeqa/selftest/context.py
index 9baad58321..33557b1240 100644
--- a/meta/lib/oeqa/selftest/context.py
+++ b/meta/lib/oeqa/selftest/context.py
@@ -82,7 +82,9 @@ class OESelftestTestContext(OETestContext):
 oe.path.copytree(selftestdir, newselftestdir)
 
 for e in os.environ:
-if builddir + "/" in os.environ[e] or 
os.environ[e].endswith(builddir):
+if builddir + "/" in os.environ[e]:
+os.environ[e] = os.environ[e].replace(builddir + "/", 
newbuilddir + "/")
+if os.environ[e].endswith(builddir):
 os.environ[e] = os.environ[e].replace(builddir, newbuilddir)
 
 subprocess.check_output("git init; git add *; git commit -a -m 
'initial'", cwd=newselftestdir, shell=True)
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142520): 
https://lists.openembedded.org/g/openembedded-core/message/142520
Mute This Topic: https://lists.openembedded.org/mt/76843045/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 10/24] image.bbclass: fix REPRODUCIBLE_TIMESTAMP_ROOTFS reference

[Steve Sakoman]

From: Matt Madison 

Commit 97b439469a45a089431ca9c31893288c855045f4 added a fallback
mechanism for getting the rootfs timestamp. However, it uses curly
braces around the variable name, which causes bitbake resolve the
variable reference, rather than the shell, so the git timestamp
never gets used. Fix the reference to restore the intent of
making it a fallback for when there is no git timestamp to
retrieve.

Signed-off-by: Matt Madison 
Signed-off-by: Richard Purdie 
(cherry picked from commit fbcf2c1c255b0c61a795c032cf7b67f5db41baa8)
Signed-off-by: Steve Sakoman 
---
 meta/classes/image.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 6620a9e9c3..459d872b4a 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -654,7 +654,7 @@ reproducible_final_image_task () {
 if [ "${BUILD_REPRODUCIBLE_BINARIES}" = "1" ]; then
 if [ "$REPRODUCIBLE_TIMESTAMP_ROOTFS" = "" ]; then
 REPRODUCIBLE_TIMESTAMP_ROOTFS=`git -C "${COREBASE}" log -1 
--pretty=%ct 2>/dev/null` || true
-if [ "${REPRODUCIBLE_TIMESTAMP_ROOTFS}" = "" ]; then
+if [ "$REPRODUCIBLE_TIMESTAMP_ROOTFS" = "" ]; then
 REPRODUCIBLE_TIMESTAMP_ROOTFS=`stat -c%Y 
${@bb.utils.which(d.getVar("BBPATH"), "conf/bitbake.conf")}`
 fi
 fi
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142516): 
https://lists.openembedded.org/g/openembedded-core/message/142516
Mute This Topic: https://lists.openembedded.org/mt/76843039/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 01/24] uninative: Upgrade to 2.9

[Steve Sakoman]

From: Khem Raj 

This supports glibc upto 2.32 which is now rolling into distributions

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie 
(cherry picked from commit 5cda8c7d642cfb72242c95f450e3391bd6537709)
Signed-off-by: Armin Kuster 
Signed-off-by: Steve Sakoman 
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index 889695eae3..69b6edee5f 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,9 +6,9 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.31"
+UNINATIVE_MAXGLIBCVERSION = "2.32"
 
-UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.8/";
-UNINATIVE_CHECKSUM[aarch64] ?= 
"989187344bf9539b464fb7ed9c223e51f4bdb4c7a677d2c314e6fed393176efe"
-UNINATIVE_CHECKSUM[i686] ?= 
"cc3e45bc8594488b407363e3fa9af5a099279dab2703c64342098719bd674990"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"a09922172c3a439105e0ae6b943daad2d83505b17da0aba97961ff433b8c21ab"
+UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.9/";
+UNINATIVE_CHECKSUM[aarch64] ?= 
"9f25a667aee225b1dd65c4aea73e01983e825b1cb9b56937932a1ee328b45f81"
+UNINATIVE_CHECKSUM[i686] ?= 
"cae5d73245d95b07cf133b780ba3f6c8d0adca3ffc4e7e7fab61d5e24d36"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"d07916b95c419c81541a19c8ef0ed8cbd78ae18437ff28a4c8a60ef40518e423"
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142507): 
https://lists.openembedded.org/g/openembedded-core/message/142507
Mute This Topic: https://lists.openembedded.org/mt/76843016/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 00/24] Patch review

[Steve Sakoman]

Please review this next set of patches for dunfell and have comments back
by end of day Wednesday.

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1381

The following changes since commit 210ebed1e9c2285d6e457bf03d1f1a1f3ddc7fda:

  package: get_package_mapping: avoid dependency mapping if renamed package 
provides original name (2020-09-04 04:31:45 -1000)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut

Adrian Freihofer (1):
  oe-publish-sdk: fix layers init via ssh

Chris Laplante (4):
  cve-update-db-native: add progress handler
  cve-check/cve-update-db-native: use lockfile to fix usage under
multiconfig
  cve-update-db-native: use context manager for cve_f
  cve-check: avoid FileNotFoundError if no do_cve_check task has run

Khem Raj (2):
  uninative: Upgrade to 2.9
  rpcbind: Use update-alternatives for rpcinfo

Lee Chee Yang (3):
  xserver-xorg: fix CVE-2020-14347
  qemu: fix CVE-2020-14364 CVE-2020-14415
  libx11 : fix CVE-2020-14344

Matt Madison (1):
  image.bbclass: fix REPRODUCIBLE_TIMESTAMP_ROOTFS reference

Oleksandr Kravchuk (1):
  ell: update to 0.33

Ovidiu Panait (1):
  libxml2: Fix CVE-2020-24977

Rahul Kumar (1):
  systemd-serialgetty: Fix sed expression quoting

Richard Purdie (3):
  runqemu: Add a hook to allow it to renice
  selftest/signing: Ensure build path relocation is safe
  oeqa/concurrencytest: Improve builddir path manipulations

Ross Burton (5):
  gdk-pixbuf: add tests PACKAGECONFIG
  insane: only load real files as ELF
  autoconf: consolidate DEPENDS
  curl: add vendors to CVE_PRODUCT to exclude false positives
  cmake: whitelist CVE-2016-10642

Zhixiong Chi (1):
  gnutls: CVE-2020-24659

akuster (1):
  cve-check.bbclass: always save cve report

 meta/classes/cve-check.bbclass|  34 ++
 meta/classes/image.bbclass|   2 +-
 meta/classes/insane.bbclass   |  13 +-
 meta/conf/distro/include/yocto-uninative.inc  |  10 +-
 meta/lib/oeqa/selftest/cases/signing.py   |   4 +-
 meta/lib/oeqa/selftest/context.py |   4 +-
 .../ell/{ell_0.32.bb => ell_0.33.bb}  |   2 +-
 .../libxml/libxml2/CVE-2020-24977.patch   |  41 +++
 meta/recipes-core/libxml/libxml2_2.9.10.bb|   1 +
 .../recipes-core/meta/cve-update-db-native.bb |  96 +++---
 .../systemd/systemd-serialgetty.bb|   2 +-
 meta/recipes-devtools/autoconf/autoconf.inc   |   5 +-
 meta/recipes-devtools/cmake/cmake.inc |   4 +
 meta/recipes-devtools/qemu/qemu.inc   |   2 +
 .../qemu/qemu/CVE-2020-14364.patch|  93 +
 .../qemu/qemu/CVE-2020-14415.patch|  37 ++
 .../recipes-extended/rpcbind/rpcbind_1.2.5.bb |   5 +-
 .../gdk-pixbuf/gdk-pixbuf_2.40.0.bb   |   8 +-
 .../xorg-lib/libx11/CVE-2020-14344.patch  | 321 ++
 .../recipes-graphics/xorg-lib/libx11_1.6.9.bb |   4 +-
 .../xserver-xorg/CVE-2020-14347.patch |  38 +++
 .../xorg-xserver/xserver-xorg_1.20.8.bb   |   1 +
 meta/recipes-support/curl/curl_7.69.1.bb  |   4 +-
 .../gnutls/gnutls/CVE-2020-24659.patch| 117 +++
 meta/recipes-support/gnutls/gnutls_3.6.14.bb  |   1 +
 scripts/oe-publish-sdk|   2 +-
 scripts/runqemu   |   5 +
 27 files changed, 782 insertions(+), 74 deletions(-)
 rename meta/recipes-core/ell/{ell_0.32.bb => ell_0.33.bb} (89%)
 create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2020-24977.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-14364.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-14415.patch
 create mode 100644 meta/recipes-graphics/xorg-lib/libx11/CVE-2020-14344.patch
 create mode 100644 
meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2020-14347.patch
 create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2020-24659.patch

-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142506): 
https://lists.openembedded.org/g/openembedded-core/message/142506
Mute This Topic: https://lists.openembedded.org/mt/76843009/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 04/24] libx11 : fix CVE-2020-14344

[Steve Sakoman]

From: Lee Chee Yang 

fix CVE-2020-14344 with squashed patch.
squashed patch include below patch,
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/1703b9f3435079d3c6021e1ee2ec34fd4978103d
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/1a566c9e00e5f35c1f9e7f3d741a02e5170852b2
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/2fcfcc49f3b1be854bb9085993a01d17c62acf60
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488

also include fix to issue introduced in above patch
(388b303c62aa35a245f1704211a023440ad2c488)
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/93fce3f4e79cbc737d6468a4f68ba3de1b83953b

Signed-off-by: Lee Chee Yang 
Signed-off-by: Steve Sakoman 
---
 .../xorg-lib/libx11/CVE-2020-14344.patch  | 321 ++
 .../recipes-graphics/xorg-lib/libx11_1.6.9.bb |   4 +-
 2 files changed, 324 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-graphics/xorg-lib/libx11/CVE-2020-14344.patch

diff --git a/meta/recipes-graphics/xorg-lib/libx11/CVE-2020-14344.patch 
b/meta/recipes-graphics/xorg-lib/libx11/CVE-2020-14344.patch
new file mode 100644
index 00..9d07202b06
--- /dev/null
+++ b/meta/recipes-graphics/xorg-lib/libx11/CVE-2020-14344.patch
@@ -0,0 +1,321 @@
+From f64388ed036b6668686ad5448bc7d4f73b35e1c7 Mon Sep 17 00:00:00 2001
+From: Matthieu Herrb 
+Date: Fri, 24 Jul 2020 21:09:10 +0200
+Subject: [PATCH] Fix CVE-2020-14344
+
+This is a squashed of below commit:
+
+commit 1 :-
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/1703b9f3435079d3c6021e1ee2ec34fd4978103d
+Change the data_len parameter of _XimAttributeToValue() to CARD16
+
+It's coming from a length in the protocol (unsigned) and passed
+to functions that expect unsigned int parameters (_XCopyToArg()
+and memcpy()).
+
+Signed-off-by: Matthieu Herrb 
+Reviewed-by: Todd Carson 
+
+commit 2 :-
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/1a566c9e00e5f35c1f9e7f3d741a02e5170852b2
+Zero out buffers in functions
+
+It looks like uninitialized stack or heap memory can leak
+out via padding bytes.
+
+Signed-off-by: Matthieu Herrb 
+Reviewed-by: Matthieu Herrb 
+
+commit 3 :-
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/2fcfcc49f3b1be854bb9085993a01d17c62acf60
+Fix more unchecked lengths
+
+Signed-off-by: Matthieu Herrb 
+Reviewed-by: Matthieu Herrb 
+
+commit 4 :-
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488
+fix integer overflows in _XimAttributeToValue()
+
+Signed-off-by: Matthieu Herrb 
+Reviewed-by: Matthieu Herrb 
+
+commit 5 :-
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/93fce3f4e79cbc737d6468a4f68ba3de1b83953b
+Fix size calculation in `_XimAttributeToValue`.
+
+The check here guards the read below.
+For `XimType_XIMStyles`, these are `num` of `CARD32` and for 
`XimType_XIMHotKeyTriggers`
+these are `num` of `XIMTRIGGERKEY` ref[1] which is defined as 3 x `CARD32`.
+(There are data after the `XIMTRIGGERKEY` according to the spec but they are 
not read by this
+function and doesn't need to be checked.)
+
+The old code here used the native datatype size instead of the wire protocol 
size causing
+the check to always fail.
+
+Also fix the size calculation for the header (size). It is 2 x CARD16 for both 
types
+despite the unused `CARD16` for `XimType_XIMStyles`.
+
+[1] 
https://www.x.org/releases/X11R7.6/doc/libX11/specs/XIM/xim.html#Input_Method_Styles
+
+This fixes a regression caused by 388b303c62aa35a245f1704211a023440ad2c488 in 
1.6.10.
+
+Fix #116
+
+Upstream-Status: Backport
+[ 
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/1703b9f3435079d3c6021e1ee2ec34fd4978103d
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/1a566c9e00e5f35c1f9e7f3d741a02e5170852b2
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/2fcfcc49f3b1be854bb9085993a01d17c62acf60
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488
+https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/93fce3f4e79cbc737d6468a4f68ba3de1b83953b
 ]
+CVE: CVE-2020-14344
+Signed-off-by: Chee Yang Lee 
+---
+ modules/im/ximcp/imDefIc.c  |  6 --
+ modules/im/ximcp/imDefIm.c  | 25 +
+ modules/im/ximcp/imRmAttr.c | 31 +++
+ 3 files changed, 44 insertions(+), 18 deletions(-)
+
+diff --git a/modules/im/ximcp/imDefIc.c b/modules/im/ximcp/imDefIc.c
+index 7564dbad..d552aa9e 100644
+--- a/modules/im/ximcp/imDefIc.c
 b/modules/im/ximcp/imDefIc.c
+@@ -350,7 +350,7 @@ _XimProtoGetICValues(
++ sizeof(INT16)
++ XIM_PAD(2 + buf_size);
+ 
+-if (!(buf = Xmalloc(buf_size)))
++if (!(buf = Xcalloc(buf_size, 1)))
+   return arg->name;
+ buf_s = (CARD16 *)&buf[XIM_HEADER_SIZE];
+ 
+@@ -708,6 +708,7 @@ _XimProtoSetICValues(
+ #endif /* XIM_CONNECTABLE */
+ 
+ _XimGetCurrentICValues(ic, &ic_values);
++memset(tmp_buf, 0, sizeof(tmp_buf32));
+ buf

[OE-core][dunfell 02/24] xserver-xorg: fix CVE-2020-14347

[Steve Sakoman]

From: Lee Chee Yang 

Signed-off-by: Lee Chee Yang 
Signed-off-by: Steve Sakoman 
---
 .../xserver-xorg/CVE-2020-14347.patch | 38 +++
 .../xorg-xserver/xserver-xorg_1.20.8.bb   |  1 +
 2 files changed, 39 insertions(+)
 create mode 100644 
meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2020-14347.patch

diff --git 
a/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2020-14347.patch 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2020-14347.patch
new file mode 100644
index 00..cf3f5f9417
--- /dev/null
+++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2020-14347.patch
@@ -0,0 +1,38 @@
+From aac28e162e5108510065ad4c323affd6deffd816 Mon Sep 17 00:00:00 2001
+From: Matthieu Herrb 
+Date: Sat, 25 Jul 2020 19:33:50 +0200
+Subject: [PATCH] fix for ZDI-11426
+
+Avoid leaking un-initalized memory to clients by zeroing the
+whole pixmap on initial allocation.
+
+This vulnerability was discovered by:
+Jan-Niklas Sohn working with Trend Micro Zero Day Initiative
+
+Signed-off-by: Matthieu Herrb 
+Reviewed-by: Alan Coopersmith 
+
+
+Upstream-Status: Backport 
[https://gitlab.freedesktop.org/xorg/xserver/-/commit/aac28e162e5108510065ad4c323affd6deffd816]
+CVE: CVE-2020-14347
+Signed-off-by: Chee Yang Lee 
+---
+ dix/pixmap.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/dix/pixmap.c b/dix/pixmap.c
+index 1186d7dbbf..5a0146bbb6 100644
+--- a/dix/pixmap.c
 b/dix/pixmap.c
+@@ -116,7 +116,7 @@ AllocatePixmap(ScreenPtr pScreen, int pixDataSize)
+ if (pScreen->totalPixmapSize > ((size_t) - 1) - pixDataSize)
+ return NullPixmap;
+ 
+-pPixmap = malloc(pScreen->totalPixmapSize + pixDataSize);
++pPixmap = calloc(1, pScreen->totalPixmapSize + pixDataSize);
+ if (!pPixmap)
+ return NullPixmap;
+ 
+-- 
+GitLab
+
diff --git a/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.20.8.bb 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.20.8.bb
index 3f7fbe85b8..5101134538 100644
--- a/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.20.8.bb
+++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.20.8.bb
@@ -5,6 +5,7 @@ SRC_URI += 
"file://0001-xf86pciBus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.pat
file://0001-test-xtest-Initialize-array-with-braces.patch \
file://sdksyms-no-build-path.patch \
file://0001-drmmode_display.c-add-missing-mi.h-include.patch \
+   file://CVE-2020-14347.patch \
"
 SRC_URI[md5sum] = "a770aec600116444a953ff632f51f839"
 SRC_URI[sha256sum] = 
"d17b646bee4ba0fb7850c1cc55b18e3e8513ed5c02bdf38da7e107f84e2d0146"
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142508): 
https://lists.openembedded.org/g/openembedded-core/message/142508
Mute This Topic: https://lists.openembedded.org/mt/76843018/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 03/24] qemu: fix CVE-2020-14364 CVE-2020-14415

[Steve Sakoman]

From: Lee Chee Yang 

Signed-off-by: Lee Chee Yang 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/qemu/qemu.inc   |  2 +
 .../qemu/qemu/CVE-2020-14364.patch| 93 +++
 .../qemu/qemu/CVE-2020-14415.patch| 37 
 3 files changed, 132 insertions(+)
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-14364.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-14415.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 49dbb1c13d..e0ea5ad477 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -45,6 +45,8 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
   file://CVE-2020-13800.patch \
   file://CVE-2020-13362.patch \
   file://CVE-2020-15863.patch \
+  file://CVE-2020-14364.patch \
+  file://CVE-2020-14415.patch \
   "
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
 
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2020-14364.patch 
b/meta/recipes-devtools/qemu/qemu/CVE-2020-14364.patch
new file mode 100644
index 00..8333025a32
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2020-14364.patch
@@ -0,0 +1,93 @@
+From b946434f2659a182afc17e155be6791ebfb302eb Mon Sep 17 00:00:00 2001
+From: Gerd Hoffmann 
+Date: Tue, 25 Aug 2020 07:36:36 +0200
+Subject: [PATCH] usb: fix setup_len init (CVE-2020-14364)
+
+Store calculated setup_len in a local variable, verify it, and only
+write it to the struct (USBDevice->setup_len) in case it passed the
+sanity checks.
+
+This prevents other code (do_token_{in,out} functions specifically)
+from working with invalid USBDevice->setup_len values and overrunning
+the USBDevice->setup_buf[] buffer.
+
+Fixes: CVE-2020-14364
+Signed-off-by: Gerd Hoffmann 
+Tested-by: Gonglei 
+Reviewed-by: Li Qiang 
+Message-id: 20200825053636.29648-1-kra...@redhat.com
+
+Upstream-Status: Backport
+[https://git.qemu.org/?p=qemu.git;a=patch;h=b946434f2659a182afc17e155be6791ebfb302eb]
+CVE: CVE-2020-14364
+Signed-off-by: Chee Yang Lee 
+---
+ hw/usb/core.c | 16 ++--
+ 1 file changed, 10 insertions(+), 6 deletions(-)
+
+diff --git a/hw/usb/core.c b/hw/usb/core.c
+index 5abd128..5234dcc 100644
+--- a/hw/usb/core.c
 b/hw/usb/core.c
+@@ -129,6 +129,7 @@ void usb_wakeup(USBEndpoint *ep, unsigned int stream)
+ static void do_token_setup(USBDevice *s, USBPacket *p)
+ {
+ int request, value, index;
++unsigned int setup_len;
+ 
+ if (p->iov.size != 8) {
+ p->status = USB_RET_STALL;
+@@ -138,14 +139,15 @@ static void do_token_setup(USBDevice *s, USBPacket *p)
+ usb_packet_copy(p, s->setup_buf, p->iov.size);
+ s->setup_index = 0;
+ p->actual_length = 0;
+-s->setup_len   = (s->setup_buf[7] << 8) | s->setup_buf[6];
+-if (s->setup_len > sizeof(s->data_buf)) {
++setup_len = (s->setup_buf[7] << 8) | s->setup_buf[6];
++if (setup_len > sizeof(s->data_buf)) {
+ fprintf(stderr,
+ "usb_generic_handle_packet: ctrl buffer too small (%d > 
%zu)\n",
+-s->setup_len, sizeof(s->data_buf));
++setup_len, sizeof(s->data_buf));
+ p->status = USB_RET_STALL;
+ return;
+ }
++s->setup_len = setup_len;
+ 
+ request = (s->setup_buf[0] << 8) | s->setup_buf[1];
+ value   = (s->setup_buf[3] << 8) | s->setup_buf[2];
+@@ -259,26 +261,28 @@ static void do_token_out(USBDevice *s, USBPacket *p)
+ static void do_parameter(USBDevice *s, USBPacket *p)
+ {
+ int i, request, value, index;
++unsigned int setup_len;
+ 
+ for (i = 0; i < 8; i++) {
+ s->setup_buf[i] = p->parameter >> (i*8);
+ }
+ 
+ s->setup_state = SETUP_STATE_PARAM;
+-s->setup_len   = (s->setup_buf[7] << 8) | s->setup_buf[6];
+ s->setup_index = 0;
+ 
+ request = (s->setup_buf[0] << 8) | s->setup_buf[1];
+ value   = (s->setup_buf[3] << 8) | s->setup_buf[2];
+ index   = (s->setup_buf[5] << 8) | s->setup_buf[4];
+ 
+-if (s->setup_len > sizeof(s->data_buf)) {
++setup_len = (s->setup_buf[7] << 8) | s->setup_buf[6];
++if (setup_len > sizeof(s->data_buf)) {
+ fprintf(stderr,
+ "usb_generic_handle_packet: ctrl buffer too small (%d > 
%zu)\n",
+-s->setup_len, sizeof(s->data_buf));
++setup_len, sizeof(s->data_buf));
+ p->status = USB_RET_STALL;
+ return;
+ }
++s->setup_len = setup_len;
+ 
+ if (p->pid == USB_TOKEN_OUT) {
+ usb_packet_copy(p, s->data_buf, s->setup_len);
+-- 
+1.8.3.1
+
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2020-14415.patch 
b/meta/recipes-devtools/qemu/qemu/CVE-2020-14415.patch
new file mode 100644
index 00..dca2f90a49
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2020-14415.patch
@@ -0,0 +1,37 @@
+From 7a4ede0047a8613b0e3b72c9d351038f013dd357 Mon Sep 17 00:00:00 2001
+From: Gerd Hoffmann 
+Date: Mon, 20 Jan

Re: [OE-core] [PATCH v2] cve-check: use ALLOWLIST

[Richard Purdie]

On Mon, 2020-09-14 at 11:42 +0100, Ross Burton wrote:
> On Mon, 14 Sep 2020 at 04:34, Lee Chee Yang 
> wrote:
> > use allowlist instead of whitelist.
> > Replace CVE_CHECK_PN_WHITELIST with CVE_CHECK_PN_ALLOWLIST.
> 
> This is a deprecated variable already, I wouldn't bother changing it.

If its deprecated, lets remove it.

> > Replace CVE_CHECK_WHITELIST with CVE_CHECK_ALLOWLIST.
> 
> ALLOWLIST really is a horrible word as this isn't a list of CVEs
> being
> allowed, it's a list of CVEs being not considered.  CVE_CHECK_IGNORE?
> CVE_CHECK_EXCLUDE?

My preference is for CVE_CHECK_IGNORE which is basically what it causes
the tool to do.

> I do also think that we should do these variable renames in one go,
> instead of piecemeal either side of a release.

I am worried about the timing of this, and the documentation
implications. We still haven't built M3 as we decided to do the sphinx
transition but we're not getting anywhere need the volume of patches to
make it happen :(

That means I don't have time to start handling piecemeal patches to
variable names, handling the fallout as things break.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142505): 
https://lists.openembedded.org/g/openembedded-core/message/142505
Mute This Topic: https://lists.openembedded.org/mt/76835201/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2] cve-check: use ALLOWLIST

[Ross Burton]

On Mon, 14 Sep 2020 at 04:34, Lee Chee Yang  wrote:
> use allowlist instead of whitelist.
> Replace CVE_CHECK_PN_WHITELIST with CVE_CHECK_PN_ALLOWLIST.

This is a deprecated variable already, I wouldn't bother changing it.

> Replace CVE_CHECK_WHITELIST with CVE_CHECK_ALLOWLIST.

ALLOWLIST really is a horrible word as this isn't a list of CVEs being
allowed, it's a list of CVEs being not considered.  CVE_CHECK_IGNORE?
CVE_CHECK_EXCLUDE?

I do also think that we should do these variable renames in one go,
instead of piecemeal either side of a release.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142504): 
https://lists.openembedded.org/g/openembedded-core/message/142504
Mute This Topic: https://lists.openembedded.org/mt/76835201/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v4] wic/bootimg-efi: IMAGE_EFI_BOOT_FILES variable added to separate bootimg-efi and bootimg-partition

[Jamaluddin, Khairul Rohaizzat]

From: Khairul Rohaizzat Jamaluddin 

Due to recent changes in bootimg-efi to include IMAGE_BOOT_FILES,
when both bootimg-partition and bootimg-efi occur in a single .wks
and IMAGE_BOOT_FILES are defined, files listed in IMAGE_BOOT_FILES
will be duplicated in both partition.
Since IMAGE_BOOT_FILES are crucial for bootimg-partition, but
optional for bootimg-efi, hence allowing bootimg-efi to have the option
to ignore it.

The new variable, IMAGE_EFI_BOOT_FILES, was added to help handle this
issue. Its basic usage is the same as IMAGE_BOOT_FILES.
Usage example:
${IMGDEPLOYDIR}/${IMAGE_BASENAME}-${MACHINE}.ext4;rootfs.img \

This commit is also squashed with the updated testcase to cover for
this change.

[YOCTO #14011]

Signed-off-by: Khairul Rohaizzat Jamaluddin 


---

v4: Added fix
sysroot = get_bb_var('RECIPE_SYSROOT_NATIVE', 'wic-tools')
result = runCmd("wic ls %s:1/ -n %s" % (images[0], sysroot))
---
 meta/classes/image_types_wic.bbclass  |  2 +-
 meta/lib/oeqa/selftest/cases/wic.py   | 13 -
 scripts/lib/wic/plugins/source/bootimg-efi.py |  8 
 3 files changed, 17 insertions(+), 6 deletions(-)

diff --git a/meta/classes/image_types_wic.bbclass 
b/meta/classes/image_types_wic.bbclass
index 2a1feed..4f888ef 100644
--- a/meta/classes/image_types_wic.bbclass
+++ b/meta/classes/image_types_wic.bbclass
@@ -1,7 +1,7 @@
 # The WICVARS variable is used to define list of bitbake variables used in wic 
code
 # variables from this list is written to .env file
 WICVARS ?= "\
-   BBLAYERS IMGDEPLOYDIR DEPLOY_DIR_IMAGE FAKEROOTCMD IMAGE_BASENAME 
IMAGE_BOOT_FILES \
+   BBLAYERS IMGDEPLOYDIR DEPLOY_DIR_IMAGE FAKEROOTCMD IMAGE_BASENAME 
IMAGE_EFI_BOOT_FILES IMAGE_BOOT_FILES \
IMAGE_LINK_NAME IMAGE_ROOTFS INITRAMFS_FSTYPES INITRD INITRD_LIVE 
ISODIR RECIPE_SYSROOT_NATIVE \
ROOTFS_SIZE STAGING_DATADIR STAGING_DIR STAGING_LIBDIR TARGET_SYS \
KERNEL_IMAGETYPE MACHINE INITRAMFS_IMAGE INITRAMFS_IMAGE_BUNDLE 
INITRAMFS_LINK_NAME APPEND \
diff --git a/meta/lib/oeqa/selftest/cases/wic.py 
b/meta/lib/oeqa/selftest/cases/wic.py
index e6b23c6..714637e 100644
--- a/meta/lib/oeqa/selftest/cases/wic.py
+++ b/meta/lib/oeqa/selftest/cases/wic.py
@@ -235,6 +235,17 @@ class Wic(WicTestCase):
 runCmd(cmd)
 self.assertEqual(1, len(glob(self.resultdir + 
"systemd-bootdisk-*direct")))
 
+def test_efi_bootpart(self):
+"""Test creation of efi-bootpart image"""
+cmd = "wic create mkefidisk -e core-image-minimal -o %s" % 
self.resultdir
+kimgtype = get_bb_var('KERNEL_IMAGETYPE', 'core-image-minimal')
+self.append_config('IMAGE_EFI_BOOT_FILES = "%s;kernel"\n' % kimgtype)
+runCmd(cmd)
+sysroot = get_bb_var('RECIPE_SYSROOT_NATIVE', 'wic-tools')
+images = glob(self.resultdir + "mkefidisk-*.direct")
+result = runCmd("wic ls %s:1/ -n %s" % (images[0], sysroot))   
+self.assertIn("kernel",result.output)
+
 def test_sdimage_bootpart(self):
 """Test creation of sdimage-bootpart image"""
 cmd = "wic create sdimage-bootpart -e core-image-minimal -o %s" % 
self.resultdir
@@ -689,7 +700,7 @@ class Wic2(WicTestCase):
 wicvars = wicvars.difference(('DEPLOY_DIR_IMAGE', 'IMAGE_BOOT_FILES',
   'INITRD', 'INITRD_LIVE', 
'ISODIR','INITRAMFS_IMAGE',
   'INITRAMFS_IMAGE_BUNDLE', 
'INITRAMFS_LINK_NAME',
-  'APPEND'))
+  'APPEND', 'IMAGE_EFI_BOOT_FILES'))
 with open(path) as envfile:
 content = dict(line.split("=", 1) for line in envfile)
 # test if variables used by wic present in the .env file
diff --git a/scripts/lib/wic/plugins/source/bootimg-efi.py 
b/scripts/lib/wic/plugins/source/bootimg-efi.py
index 14c1723..cdc7254 100644
--- a/scripts/lib/wic/plugins/source/bootimg-efi.py
+++ b/scripts/lib/wic/plugins/source/bootimg-efi.py
@@ -212,8 +212,8 @@ class BootimgEFIPlugin(SourcePlugin):
 except KeyError:
 raise WicError("bootimg-efi requires a loader, none specified")
 
-if get_bitbake_var("IMAGE_BOOT_FILES") is None:
-logger.debug('No boot files defined in IMAGE_BOOT_FILES')
+if get_bitbake_var("IMAGE_EFI_BOOT_FILES") is None:
+logger.debug('No boot files defined in IMAGE_EFI_BOOT_FILES')
 else:
 boot_files = None
 for (fmt, id) in (("_uuid-%s", part.uuid), ("_label-%s", 
part.label), (None, None)):
@@ -222,7 +222,7 @@ class BootimgEFIPlugin(SourcePlugin):
 else:
 var = ""
 
-boot_files = get_bitbake_var("IMAGE_BOOT_FILES" + var)
+boot_files = get_bitbake_var("IMAGE_EFI_BOOT_FILES" + var)
 if boot_files:
 break
 
@@ -292,7 +292,7 @@ class BootimgEFIPlugin(SourcePlugin):
 (s

[OE-core] [PATCH v4] wic/bootimg-efi: IMAGE_EFI_BOOT_FILES variable added to separate bootimg-efi and bootimg-partition

[Jamaluddin, Khairul Rohaizzat]

From: Khairul Rohaizzat Jamaluddin 

Due to recent changes in bootimg-efi to include IMAGE_BOOT_FILES,
when both bootimg-partition and bootimg-efi occur in a single .wks
and IMAGE_BOOT_FILES are defined, files listed in IMAGE_BOOT_FILES
will be duplicated in both partition.
Since IMAGE_BOOT_FILES are crucial for bootimg-partition, but
optional for bootimg-efi, hence allowing bootimg-efi to have the option
to ignore it.

The new variable, IMAGE_EFI_BOOT_FILES, was added to help handle this
issue. Its basic usage is the same as IMAGE_BOOT_FILES.
Usage example:
${IMGDEPLOYDIR}/${IMAGE_BASENAME}-${MACHINE}.ext4;rootfs.img \

This commit is also squashed with the updated testcase to cover for
this change.

[YOCTO #14011]

Signed-off-by: Khairul Rohaizzat Jamaluddin 


---

v4: Added fix
sysroot = get_bb_var('RECIPE_SYSROOT_NATIVE', 'wic-tools')
result = runCmd("wic ls %s:1/ -n %s" % (images[0], sysroot))
---
 meta/classes/image_types_wic.bbclass  |  2 +-
 meta/lib/oeqa/selftest/cases/wic.py   | 13 -
 scripts/lib/wic/plugins/source/bootimg-efi.py |  8 
 3 files changed, 17 insertions(+), 6 deletions(-)

diff --git a/meta/classes/image_types_wic.bbclass 
b/meta/classes/image_types_wic.bbclass
index 2a1feed..4f888ef 100644
--- a/meta/classes/image_types_wic.bbclass
+++ b/meta/classes/image_types_wic.bbclass
@@ -1,7 +1,7 @@
 # The WICVARS variable is used to define list of bitbake variables used in wic 
code
 # variables from this list is written to .env file
 WICVARS ?= "\
-   BBLAYERS IMGDEPLOYDIR DEPLOY_DIR_IMAGE FAKEROOTCMD IMAGE_BASENAME 
IMAGE_BOOT_FILES \
+   BBLAYERS IMGDEPLOYDIR DEPLOY_DIR_IMAGE FAKEROOTCMD IMAGE_BASENAME 
IMAGE_EFI_BOOT_FILES IMAGE_BOOT_FILES \
IMAGE_LINK_NAME IMAGE_ROOTFS INITRAMFS_FSTYPES INITRD INITRD_LIVE 
ISODIR RECIPE_SYSROOT_NATIVE \
ROOTFS_SIZE STAGING_DATADIR STAGING_DIR STAGING_LIBDIR TARGET_SYS \
KERNEL_IMAGETYPE MACHINE INITRAMFS_IMAGE INITRAMFS_IMAGE_BUNDLE 
INITRAMFS_LINK_NAME APPEND \
diff --git a/meta/lib/oeqa/selftest/cases/wic.py 
b/meta/lib/oeqa/selftest/cases/wic.py
index e6b23c6..714637e 100644
--- a/meta/lib/oeqa/selftest/cases/wic.py
+++ b/meta/lib/oeqa/selftest/cases/wic.py
@@ -235,6 +235,17 @@ class Wic(WicTestCase):
 runCmd(cmd)
 self.assertEqual(1, len(glob(self.resultdir + 
"systemd-bootdisk-*direct")))
 
+def test_efi_bootpart(self):
+"""Test creation of efi-bootpart image"""
+cmd = "wic create mkefidisk -e core-image-minimal -o %s" % 
self.resultdir
+kimgtype = get_bb_var('KERNEL_IMAGETYPE', 'core-image-minimal')
+self.append_config('IMAGE_EFI_BOOT_FILES = "%s;kernel"\n' % kimgtype)
+runCmd(cmd)
+sysroot = get_bb_var('RECIPE_SYSROOT_NATIVE', 'wic-tools')
+images = glob(self.resultdir + "mkefidisk-*.direct")
+result = runCmd("wic ls %s:1/ -n %s" % (images[0], sysroot))   
+self.assertIn("kernel",result.output)
+
 def test_sdimage_bootpart(self):
 """Test creation of sdimage-bootpart image"""
 cmd = "wic create sdimage-bootpart -e core-image-minimal -o %s" % 
self.resultdir
@@ -689,7 +700,7 @@ class Wic2(WicTestCase):
 wicvars = wicvars.difference(('DEPLOY_DIR_IMAGE', 'IMAGE_BOOT_FILES',
   'INITRD', 'INITRD_LIVE', 
'ISODIR','INITRAMFS_IMAGE',
   'INITRAMFS_IMAGE_BUNDLE', 
'INITRAMFS_LINK_NAME',
-  'APPEND'))
+  'APPEND', 'IMAGE_EFI_BOOT_FILES'))
 with open(path) as envfile:
 content = dict(line.split("=", 1) for line in envfile)
 # test if variables used by wic present in the .env file
diff --git a/scripts/lib/wic/plugins/source/bootimg-efi.py 
b/scripts/lib/wic/plugins/source/bootimg-efi.py
index 14c1723..cdc7254 100644
--- a/scripts/lib/wic/plugins/source/bootimg-efi.py
+++ b/scripts/lib/wic/plugins/source/bootimg-efi.py
@@ -212,8 +212,8 @@ class BootimgEFIPlugin(SourcePlugin):
 except KeyError:
 raise WicError("bootimg-efi requires a loader, none specified")
 
-if get_bitbake_var("IMAGE_BOOT_FILES") is None:
-logger.debug('No boot files defined in IMAGE_BOOT_FILES')
+if get_bitbake_var("IMAGE_EFI_BOOT_FILES") is None:
+logger.debug('No boot files defined in IMAGE_EFI_BOOT_FILES')
 else:
 boot_files = None
 for (fmt, id) in (("_uuid-%s", part.uuid), ("_label-%s", 
part.label), (None, None)):
@@ -222,7 +222,7 @@ class BootimgEFIPlugin(SourcePlugin):
 else:
 var = ""
 
-boot_files = get_bitbake_var("IMAGE_BOOT_FILES" + var)
+boot_files = get_bitbake_var("IMAGE_EFI_BOOT_FILES" + var)
 if boot_files:
 break
 
@@ -292,7 +292,7 @@ class BootimgEFIPlugin(SourcePlugin):
 (s

[OE-core] [PATCH v3] squashfs-tools: Allow COMP_DEFAULT to be changed easily at build time

[Peter Morrow]

The default compression algorithm is currently gzip, this patch allows the
default to be changed by setting SQUASHFS_TOOLS_COMP_DEFAULT to a valid
compression algorithm.

Signed-off-by: Peter Morrow 
---
 meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb 
b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
index b06951d..42fae28 100644
--- a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
+++ b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
@@ -25,6 +25,9 @@ PACKAGECONFIG[xattr] = "XATTR_SUPPORT=1,XATTR_SUPPORT=0,attr"
 PACKAGECONFIG[zstd] = "ZSTD_SUPPORT=1,ZSTD_SUPPORT=0,zstd"
 PACKAGECONFIG[reproducible] = "REPRODUCIBLE_DEFAULT=1,REPRODUCIBLE_DEFAULT=0,"
 
+SQUASHFS_TOOLS_COMP_DEFAULT ?= "gzip"
+EXTRA_OEMAKE += "COMP_DEFAULT=${SQUASHFS_TOOLS_COMP_DEFAULT}"
+
 do_compile() {
oe_runmake all
 }
-- 
1.8.3.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142501): 
https://lists.openembedded.org/g/openembedded-core/message/142501
Mute This Topic: https://lists.openembedded.org/mt/76838796/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2] squashfs-tools: Allow COMP_DEFAULT to be changed easily at build time

[Peter Morrow]

On Fri, Sep 11, 2020 at 10:04:00PM -0700, Khem Raj wrote:
> 
> 
> On 9/11/20 10:33 AM, Andre McCurdy wrote:
> > On Fri, Sep 11, 2020 at 10:21 AM Peter Morrow
> >  wrote:
> >>
> >> The default compression algorithm is gzip, this patch allows the default
> >> to be changed via a bbappend file by setting SQUASHFS_TOOLS_COMP_DEFAULT
> >> to a valid compression algorithm.
> >>
> >> Signed-off-by: Peter Morrow 
> >> ---
> >>  ...ols-Allow-COMP_DEFAULT-to-be-overridden-v.patch | 34 
> >> ++
> >>  .../squashfs-tools/squashfs-tools_git.bb   |  4 +++
> >>  2 files changed, 38 insertions(+)
> >>  create mode 100644 
> >> meta/recipes-devtools/squashfs-tools/files/0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch
> >>
> >> diff --git 
> >> a/meta/recipes-devtools/squashfs-tools/files/0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch
> >>  
> >> b/meta/recipes-devtools/squashfs-tools/files/0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch
> >> new file mode 100644
> >> index 000..5f12c42
> >> --- /dev/null
> >> +++ 
> >> b/meta/recipes-devtools/squashfs-tools/files/0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch
> >> @@ -0,0 +1,34 @@
> >> +From d2d9b517696f5950597f5b60ae8fdade5b7c14a9 Mon Sep 17 00:00:00 2001
> >> +From: Peter Morrow 
> >> +Date: Fri, 4 Sep 2020 15:43:15 +0100
> >> +Subject: [PATCH] squashfs-tools: Allow COMP_DEFAULT to be overridden via 
> >> make
> >> + cmdline
> >> +
> >> +Currently the only way to modify the default compression algorithm is to
> >> +modify the Makefile. It is useful to be able to set the default 
> >> compression
> >> +algorithm via the make command line since otherwise a build time search
> >> +replace operation needs to be performed on the Makefile.
> > 
> > That's not how Makefiles normally work. Options set via the command
> > line over-ride variables set with = in the Makefile.
> > 
> > Does setting your chosen value for COMP_DEFAULT on the make command
> > line really not work?
> 
> that works if make is invoked with -e option, We do not use make -e with
> bare makefile based recipes.
> 
> > 
> >> +Upstream-Status: Submitted 
> >> [https://github.com/plougher/squashfs-tools/pull/93 ]
> >> +
> >> +Signed-off-by: Peter Morrow 
> >> +---
> >> + squashfs-tools/Makefile | 2 +-
> >> + 1 file changed, 1 insertion(+), 1 deletion(-)
> >> +
> >> +diff --git a/squashfs-tools/Makefile b/squashfs-tools/Makefile
> >> +index aee4b96..7425605 100644
> >> +--- a/squashfs-tools/Makefile
> >>  b/squashfs-tools/Makefile
> >> +@@ -85,7 +85,7 @@ GZIP_SUPPORT = 1
> >> + # in Mksquashfs.  Obviously the compression algorithm must have been
> >> + # selected to be built
> >> + #
> >> +-COMP_DEFAULT = gzip
> >> ++COMP_DEFAULT ?= gzip
> >> +
> >> +
> >> + ###
> >> +--
> >> +2.20.1
> >> +
> >> diff --git a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb 
> >> b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> >> index b06951d..df025d4 100644
> >> --- a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> >> +++ b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> >> @@ -9,6 +9,7 @@ PV = "4.4"
> >>  SRCREV = "52eb4c279cd283ed9802dd1ceb686560b22ffb67"
> >>  SRC_URI = "git://github.com/plougher/squashfs-tools.git;protocol=https \
> >> 
> >> file://0001-squashfs-tools-fix-build-failure-against-gcc-10.patch;striplevel=2
> >>  \
> >> +   
> >> file://0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch;striplevel=2
> >>  \
> >>  "
> >>
> >>  S = "${WORKDIR}/git/squashfs-tools"
> >> @@ -25,6 +26,9 @@ PACKAGECONFIG[xattr] = 
> >> "XATTR_SUPPORT=1,XATTR_SUPPORT=0,attr"
> >>  PACKAGECONFIG[zstd] = "ZSTD_SUPPORT=1,ZSTD_SUPPORT=0,zstd"
> >>  PACKAGECONFIG[reproducible] = 
> >> "REPRODUCIBLE_DEFAULT=1,REPRODUCIBLE_DEFAULT=0,"
> >>
> >> +SQUASHFS_TOOLS_COMP_DEFAULT ?= "gzip"
> >> +EXTRA_OEMAKE += "COMP_DEFAULT=${SQUASHFS_TOOLS_COMP_DEFAULT}"
> > 
> > Note that this will force the recipe's default value even if upstream
> > squashfs-tools changes. Not a problem now as the two are the same, but
> > something which will need to be checked each time squashfs-tools is
> > updated.

Yep, good point. I covered this in V1, though have not covered it in V3.
I'm happy to add something to cover this in a V4 if you'd like?

Thanks,
Peter.

> > 
> >>  do_compile() {
> >> oe_runmake all
> >>  }
> >> --
> >> 1.8.3.1
> >>
> >>
> >>
> >> 

> pub  1024D/919D3314 2009-08-28 Khem Raj 
> sub  4096g/7CF5958F 2009-08-28

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142500): 
https://lists.openembedded.org/g/openembedded-core/message/142500
Mute This Topic: https://lists.openembedded.org/mt/76784587/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2] squashfs-tools: Allow COMP_DEFAULT to be changed easily at build time

[Peter Morrow]

On Sat, Sep 12, 2020 at 12:37:28AM -0700, Khem Raj wrote:
> On Fri, Sep 11, 2020 at 11:36 PM Andre McCurdy  wrote:
> >
> > On Fri, Sep 11, 2020 at 10:04 PM Khem Raj  wrote:
> > >
> > >
> > >
> > > On 9/11/20 10:33 AM, Andre McCurdy wrote:
> > > > On Fri, Sep 11, 2020 at 10:21 AM Peter Morrow
> > > >  wrote:
> > > >>
> > > >> The default compression algorithm is gzip, this patch allows the 
> > > >> default
> > > >> to be changed via a bbappend file by setting 
> > > >> SQUASHFS_TOOLS_COMP_DEFAULT
> > > >> to a valid compression algorithm.
> > > >>
> > > >> Signed-off-by: Peter Morrow 
> > > >> ---
> > > >>  ...ols-Allow-COMP_DEFAULT-to-be-overridden-v.patch | 34 
> > > >> ++
> > > >>  .../squashfs-tools/squashfs-tools_git.bb   |  4 +++
> > > >>  2 files changed, 38 insertions(+)
> > > >>  create mode 100644 
> > > >> meta/recipes-devtools/squashfs-tools/files/0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch
> > > >>
> > > >> diff --git 
> > > >> a/meta/recipes-devtools/squashfs-tools/files/0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch
> > > >>  
> > > >> b/meta/recipes-devtools/squashfs-tools/files/0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch
> > > >> new file mode 100644
> > > >> index 000..5f12c42
> > > >> --- /dev/null
> > > >> +++ 
> > > >> b/meta/recipes-devtools/squashfs-tools/files/0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch
> > > >> @@ -0,0 +1,34 @@
> > > >> +From d2d9b517696f5950597f5b60ae8fdade5b7c14a9 Mon Sep 17 00:00:00 2001
> > > >> +From: Peter Morrow 
> > > >> +Date: Fri, 4 Sep 2020 15:43:15 +0100
> > > >> +Subject: [PATCH] squashfs-tools: Allow COMP_DEFAULT to be overridden 
> > > >> via make
> > > >> + cmdline
> > > >> +
> > > >> +Currently the only way to modify the default compression algorithm is 
> > > >> to
> > > >> +modify the Makefile. It is useful to be able to set the default 
> > > >> compression
> > > >> +algorithm via the make command line since otherwise a build time 
> > > >> search
> > > >> +replace operation needs to be performed on the Makefile.
> > > >
> > > > That's not how Makefiles normally work. Options set via the command
> > > > line over-ride variables set with = in the Makefile.
> > > >
> > > > Does setting your chosen value for COMP_DEFAULT on the make command
> > > > line really not work?
> > >
> > > that works if make is invoked with -e option, We do not use make -e with
> > > bare makefile based recipes.
> >
> > The -e option is related to environment variables. It's not relevant
> > for this discussion - which is about setting options via the make
> > command line.
> >
> 
> I somehow oversaw the fact its being passed as make variable on
> cmdline  and not becoming
> an export. so you are right, I think we don't need the patch perhaps
> setting it via EXTRA_OEMAKE
> should suffice

Yes, not sure what I was thinking. I've tested again without the
squashfs-tools patch and setting via EXTRA_OEMAKE works as expected.

Thanks,
Peter.

> 
> > > >> +Upstream-Status: Submitted 
> > > >> [https://github.com/plougher/squashfs-tools/pull/93 ]
> > > >> +
> > > >> +Signed-off-by: Peter Morrow 
> > > >> +---
> > > >> + squashfs-tools/Makefile | 2 +-
> > > >> + 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >> +
> > > >> +diff --git a/squashfs-tools/Makefile b/squashfs-tools/Makefile
> > > >> +index aee4b96..7425605 100644
> > > >> +--- a/squashfs-tools/Makefile
> > > >>  b/squashfs-tools/Makefile
> > > >> +@@ -85,7 +85,7 @@ GZIP_SUPPORT = 1
> > > >> + # in Mksquashfs.  Obviously the compression algorithm must have been
> > > >> + # selected to be built
> > > >> + #
> > > >> +-COMP_DEFAULT = gzip
> > > >> ++COMP_DEFAULT ?= gzip
> > > >> +
> > > >> +
> > > >> + ###
> > > >> +--
> > > >> +2.20.1
> > > >> +
> > > >> diff --git 
> > > >> a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb 
> > > >> b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> > > >> index b06951d..df025d4 100644
> > > >> --- a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> > > >> +++ b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
> > > >> @@ -9,6 +9,7 @@ PV = "4.4"
> > > >>  SRCREV = "52eb4c279cd283ed9802dd1ceb686560b22ffb67"
> > > >>  SRC_URI = 
> > > >> "git://github.com/plougher/squashfs-tools.git;protocol=https \
> > > >> 
> > > >> file://0001-squashfs-tools-fix-build-failure-against-gcc-10.patch;striplevel=2
> > > >>  \
> > > >> +   
> > > >> file://0001-squashfs-tools-Allow-COMP_DEFAULT-to-be-overridden-v.patch;striplevel=2
> > > >>  \
> > > >>  "
> > > >>
> > > >>  S = "${WORKDIR}/git/squashfs-tools"
> > > >> @@ -25,6 +26,9 @@ PACKAGECONFIG[xattr] = 
> > > >> "XATTR_SUPPORT=1,XATTR_SUPPORT=0,attr"
> > > >>  PACKAGECONFIG[zstd] = "ZSTD_SUPPORT=1,ZSTD_SUPPORT=0,zstd"
> > > >>  PACKAGECONFIG[reproducible] = 
> > > >> "REPRODUCIBLE_DEFAULT=1,REPRODUCIBLE_DEFAULT=0,"
> > > >>
> > > 

[OE-core] [PATCH] bison: remove the parallel build patch

[Yu, Mingli]

From: Mingli Yu 

Remove the parallel build patch as the issue have already been
fixed in bison 3.7.2(f7b642cf build: fix incorrect dependencies).

Signed-off-by: Mingli Yu 
---
 .../0001-bison-fix-the-parallel-build.patch   | 63 ---
 meta/recipes-devtools/bison/bison_3.7.2.bb|  1 -
 2 files changed, 64 deletions(-)
 delete mode 100644 
meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch

diff --git 
a/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch 
b/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
deleted file mode 100644
index c3be91a109..00
--- a/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
+++ /dev/null
@@ -1,63 +0,0 @@
-From e0dbcee6e25b3c0cb11a627bbfe3af45ef67ec30 Mon Sep 17 00:00:00 2001
-From: Mingli Yu 
-Date: Thu, 14 May 2020 15:23:16 +0800
-Subject: [PATCH] bison: fix the parallel build
-
-Explicitly make the BUILT_SOURCES which
-are the generated headers such as stdio.h,
-fcntl.h and etc to be the dependencies of
-the gl_LIBOBJS such as libbison_a-sprintf.o,
-libbison_a-printf.o and etc to guarantee the
-BUILT_SOURCES is generated before begin to
-compile EXTRA_lib_libbison_a_SOURCES such as
-fprintf.c in parallel builid, otherwise there
-may come below error:
- | muscle-tab.c:(.text+0x77a): undefined reference to `rpl_sprintf'
-
-It does the same for src_bison_OBJECTS and
-lib_libbison_a_OBJECTS to make sure BUILT_SOURCES
-generated before begin to compile src_bison_SOURCES
-which contains AnnotationList.c and etc.
-
-BTW, the MOSTLYCLEANFILES also contains the
-generated header needs to be created early
-in the build process, so add it also in to
-avoid below error:
- | ./lib/uniwidth/width.c:21:10: fatal error: uniwidth.h: No such file or 
directory
-
-Upstream-Status: Submitted [bison-patc...@gnu.org maillist]
-
-Signed-off-by: Mingli Yu 

- lib/gnulib.mk | 2 ++
- src/local.mk  | 1 +
- 2 files changed, 3 insertions(+)
-
-diff --git a/lib/gnulib.mk b/lib/gnulib.mk
-index c21c656..27fb3dc 100644
 a/lib/gnulib.mk
-+++ b/lib/gnulib.mk
-@@ -120,6 +120,8 @@ lib_libbison_a_SOURCES =
- lib_libbison_a_LIBADD = $(gl_LIBOBJS)
- lib_libbison_a_DEPENDENCIES = $(gl_LIBOBJS)
- EXTRA_lib_libbison_a_SOURCES =
-+$(lib_libbison_a_OBJECTS): $(BUILT_SOURCES) $(MOSTLYCLEANFILES:%.h)
-+$(gl_LIBOBJS): $(BUILT_SOURCES) $(MOSTLYCLEANFILES:%.h)
- 
- lib_libbison_a_CPPFLAGS = $(AM_CPPFLAGS) 
-DDEFAULT_TEXT_DOMAIN=\"bison-gnulib\"
- 
-diff --git a/src/local.mk b/src/local.mk
-index 61dc573..b5b9079 100644
 a/src/local.mk
-+++ b/src/local.mk
-@@ -24,6 +24,7 @@ if RELOCATABLE_VIA_LD
-   src_bison_LDFLAGS = `$(RELOCATABLE_LDFLAGS) $(bindir)`
- endif
- 
-+$(src_bison_OBJECTS): $(BUILT_SOURCES) $(MOSTLYCLEANFILES:%.h)
- src_bison_CFLAGS = $(AM_CFLAGS) $(WERROR_CFLAGS)
- src_bison_SOURCES = \
-   src/AnnotationList.c  \
--- 
-2.17.1
-
diff --git a/meta/recipes-devtools/bison/bison_3.7.2.bb 
b/meta/recipes-devtools/bison/bison_3.7.2.bb
index f7bf70fff3..efc426376d 100644
--- a/meta/recipes-devtools/bison/bison_3.7.2.bb
+++ b/meta/recipes-devtools/bison/bison_3.7.2.bb
@@ -11,7 +11,6 @@ DEPENDS = "bison-native flex-native"
 
 SRC_URI = "${GNU_MIRROR}/bison/bison-${PV}.tar.xz \
file://add-with-bisonlocaledir.patch \
-   file://0001-bison-fix-the-parallel-build.patch \
"
 SRC_URI[sha256sum] = 
"7948d193104d979c0fb0294a1854c73c89d72ae41acfc081826142578a78a91b"
 
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142498): 
https://lists.openembedded.org/g/openembedded-core/message/142498
Mute This Topic: https://lists.openembedded.org/mt/76837897/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] lttng-modules: backport patch to fix build for linux-5.4.62+

[Jens Rehsack]

From: Jens Rehsack 

Backport patch from lttng-modules/stable-2.12
87b2aff fix: writeback: Fix sync livelock due to b_dirty_time processing 
(v5.9)

with minor modfication to catch
6623c19042b6 writeback: Fix sync livelock due to b_dirty_time processing

from linux/stable-5.4 v5.4.62+

Signed-off-by: Jens Rehsack 
---
 ...x-sync-livelock-due-to-b_dirty_time-.patch | 117 ++
 .../lttng/lttng-modules_2.12.2.bb |   1 +
 2 files changed, 118 insertions(+)
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch

diff --git 
a/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
 
b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
new file mode 100644
index 00..96a1c486ef
--- /dev/null
+++ 
b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
@@ -0,0 +1,117 @@
+From 87b2affc3eb06f3fb2d0923f18af37713eb6814b Mon Sep 17 00:00:00 2001
+From: Michael Jeanson 
+Date: Mon, 31 Aug 2020 14:16:01 -0400
+Subject: [PATCH] fix: writeback: Fix sync livelock due to b_dirty_time
+ processing (v5.9)
+
+See upstream commit:
+
+  commit f9cae926f35e8230330f28c7b743ad088611a8de
+  Author: Jan Kara 
+  Date:   Fri May 29 16:08:58 2020 +0200
+
+writeback: Fix sync livelock due to b_dirty_time processing
+
+When we are processing writeback for sync(2), move_expired_inodes()
+didn't set any inode expiry value (older_than_this). This can result in
+writeback never completing if there's steady stream of inodes added to
+b_dirty_time list as writeback rechecks dirty lists after each writeback
+round whether there's more work to be done. Fix the problem by using
+sync(2) start time is inode expiry value when processing b_dirty_time
+list similarly as for ordinarily dirtied inodes. This requires some
+refactoring of older_than_this handling which simplifies the code
+noticeably as a bonus.
+
+Change-Id: I8b894b13ccc14d9b8983ee4c2810a927c319560b
+Signed-off-by: Michael Jeanson 
+Signed-off-by: Mathieu Desnoyers 
+---
+ .../events/lttng-module/writeback.h   | 39 ---
+ 1 file changed, 26 insertions(+), 13 deletions(-)
+
+Upstream Status: Backport
+
+diff --git a/instrumentation/events/lttng-module/writeback.h 
b/instrumentation/events/lttng-module/writeback.h
+index ece67ad..e9018dd 100644
+--- a/instrumentation/events/lttng-module/writeback.h
 b/instrumentation/events/lttng-module/writeback.h
+@@ -384,34 +384,48 @@ 
LTTNG_TRACEPOINT_EVENT_WBC_INSTANCE(wbc_balance_dirty_wait, writeback_wbc_balanc
+ #endif
+ LTTNG_TRACEPOINT_EVENT_WBC_INSTANCE(wbc_writepage, writeback_wbc_writepage)
+ 
+-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,1,0))
++#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,9,0)) || (LINUX_VERSION_CODE >= 
KERNEL_VERSION(5,4,62))
++LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
++  TP_PROTO(struct bdi_writeback *wb,
++   struct wb_writeback_work *work,
++   unsigned long dirtied_before,
++   int moved),
++  TP_ARGS(wb, work, dirtied_before, moved),
++  TP_FIELDS(
++  ctf_array_text(char, name, dev_name(wb->bdi->dev), 32)
++  ctf_integer(unsigned long, older, dirtied_before)
++  ctf_integer(int, moved, moved)
++  )
++)
++#elif (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
+ LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
+   TP_PROTO(struct bdi_writeback *wb,
+-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
+struct wb_writeback_work *work,
+-#else
+-   unsigned long *older_than_this,
+-#endif
+int moved),
+-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
+   TP_ARGS(wb, work, moved),
+-#else
++  TP_FIELDS(
++  ctf_array_text(char, name, dev_name(wb->bdi->dev), 32)
++  ctf_integer(int, moved, moved)
++  )
++)
++#elif (LINUX_VERSION_CODE >= KERNEL_VERSION(3,1,0))
++LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
++  TP_PROTO(struct bdi_writeback *wb,
++   unsigned long *older_than_this,
++   int moved),
+   TP_ARGS(wb, older_than_this, moved),
+-#endif
+   TP_FIELDS(
+   ctf_array_text(char, name, dev_name(wb->bdi->dev), 32)
+-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
+-#else
+   ctf_integer(unsigned long, older,
+   older_than_this ? *older_than_this : 0)
+   ctf_integer(long, age,
+   older_than_this ?
+   (jiffies - *older_than_this) * 1000 / HZ
+   : -1)
+-#endif
+   ctf_integer(int, moved, moved)
+   )
+ )
++#endif
+ 
+ #if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,8,0))
+ LTTNG_TRACEPOINT_EVENT_MAP(global_dirty_state,
+@@ -460,7 +474,7 @@ LTTNG_TRACEPOINT

Re: [OE-core] [PATCH] core-image-sato: qemumips use 512 mem

[Richard Purdie]

On Sat, 2020-09-12 at 20:59 -0700, akuster wrote:
> From: Armin Kuster 
> 
> Fixes:
> 
> WARNING: core-image-sato-sdk-1.0-r0 do_testimage: Couldn't login into
> serial console as root using blank password
> WARNING: core-image-sato-sdk-1.0-r0 do_testimage: The output:
> root
> <<< run_serial(): command timed out after 60 seconds without output
> >>>
> 
> In another run, this error was seen:
> 
> Failed to reload daemon: Refusing to reload, not enough space
> available on /run/systemd. Currently, 14.3M are free, but a safety
> buffer of 16.0M is enforced.
> 
> With updates to systemd and Qemu we should revert: 499a31cf06 core-
> image-sato: don't use 512MB in qemumips
> 
> Signed-off-by: Armin Kuster  
> ---
>  meta/recipes-sato/images/core-image-sato.bb | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/meta/recipes-sato/images/core-image-sato.bb
> b/meta/recipes-sato/images/core-image-sato.bb
> index 673106eb6d..878e0eaa8d 100644
> --- a/meta/recipes-sato/images/core-image-sato.bb
> +++ b/meta/recipes-sato/images/core-image-sato.bb
> @@ -12,4 +12,3 @@ TOOLCHAIN_HOST_TASK_append = " nativesdk-intltool
> nativesdk-glib-2.0"
>  TOOLCHAIN_HOST_TASK_remove_task-populate-sdk-ext = " nativesdk-
> intltool nativesdk-glib-2.0"
>  
>  QB_MEM = '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m
> 512", "-m 256", d)}'
> -QB_MEM_qemumips = "-m 256"


We have now seen:

https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/2452

with this applied, not sure if its related. We have seen this kind of
network dropout elsewhere but we don't seem to have good debug when it
happens.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#142496): 
https://lists.openembedded.org/g/openembedded-core/message/142496
Mute This Topic: https://lists.openembedded.org/mt/76814331/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-