[OE-core] [PATCH] acpid:upgrade 2.0.31 -> 2.0.32

2019-08-19 Thread Zang Ruochen
Signed-off-by: Zang Ruochen --- meta/recipes-bsp/acpid/{acpid_2.0.31.bb => acpid_2.0.32.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-bsp/acpid/{acpid_2.0.31.bb => acpid_2.0.32.bb} (55%) diff --git a/meta/recipes-bsp/acpid/acpid_2.0.31.bb

Re: [OE-core] Conflict of systemd and sysvinit

2019-08-19 Thread Otavio Salvador
On Mon, Aug 19, 2019 at 1:48 PM Mark Hatle wrote: > On 8/19/19 11:27 AM, Ross Burton wrote: > > On 19/08/2019 11:37, Otavio Salvador wrote: > >> On Sun, Aug 18, 2019 at 11:00 PM Kang Kai wrote: > >>> On 2019/8/18 上午3:27, Otavio Salvador wrote: > >>> Would you like to give more detailed steps how

Re: [OE-core] [PATCH V2] systemd: add menson option to decrease RLIMIT_NOFILE on qemu bsp

2019-08-19 Thread Andre McCurdy
On Mon, Aug 19, 2019 at 9:38 AM Hongxu Jia wrote: > > Since do_testimage for core-image-sato-sdk has memory limitation (256Mib) > which caused rpc.statd failed with out of memory. > [ 531.306146] Out of memory: Kill process 193 (rpc.statd) score 200 or > sacrifice child > > The rpc.statd

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

2019-08-19 Thread sjolley.yp.pm
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:

Re: [OE-core] [PATCH] systemd: decreasing default RLIMIT_NOFILE on qemu bsp

2019-08-19 Thread Alexander Kanavin
Probably in this case it is better to add a patch that allows HIGH_RLIMIT_NOFILE to be configured from the systemd recipe via meson switches, and offer that to systemd upstream. Alex On Mon, 19 Aug 2019 at 16:25, Hongxu Jia wrote: > On 8/19/19 10:01 PM, Alexander Kanavin wrote: > > Should the

Re: [OE-core] [PATCH] systemd: decreasing default RLIMIT_NOFILE on qemu bsp

2019-08-19 Thread richard . purdie
On Mon, 2019-08-19 at 16:01 +0200, Alexander Kanavin wrote: > Should the limit be simply raised? The 256M setup is crumbling on > several fronts (runtime tests, modernisation of X, various non-x86 > qemu targets). Adding per-image/target exceptions, custom non- > upstreamable patches, or sticking

Re: [OE-core] [PATCH] libffi: Upgrade to 3.3-rc0

2019-08-19 Thread Ross Burton
On 19/08/2019 16:09, Khem Raj wrote: Set the PV to 3.3~rc0 and 3.3 will sort after it. I thinking using + terminology is familiar in OE world let’s stick to it I worked on adding ~ explicitly for this exact problem (as used by Fedora, Debian, etc), so please let's use ~ instead of

Re: [OE-core] Conflict of systemd and sysvinit

2019-08-19 Thread Mark Hatle
On 8/19/19 11:27 AM, Ross Burton wrote: > On 19/08/2019 11:37, Otavio Salvador wrote: >> On Sun, Aug 18, 2019 at 11:00 PM Kang Kai wrote: >>> On 2019/8/18 上午3:27, Otavio Salvador wrote: >>> Would you like to give more detailed steps how the error occurred? And >>> what's extra settings in you

Re: [OE-core] [PATCH] libffi: Upgrade to 3.3-rc0

2019-08-19 Thread Ross Burton
On 14/08/2019 23:46, Khem Raj wrote: On Wed, Aug 14, 2019 at 3:42 PM akuster808 wrote: On 8/14/19 3:29 PM, Khem Raj wrote: libffi 3.1 release has been a bit aged and new architectures, compilers have since been come on stage to compile it, we have been carrying patches, but its better to

Re: [OE-core] Conflict of systemd and sysvinit

2019-08-19 Thread Ross Burton
On 19/08/2019 11:37, Otavio Salvador wrote: On Sun, Aug 18, 2019 at 11:00 PM Kang Kai wrote: On 2019/8/18 上午3:27, Otavio Salvador wrote: Would you like to give more detailed steps how the error occurred? And what's extra settings in you local.conf please? I had sysvinit and systemd enabled.

Re: [OE-core] Conflict of systemd and sysvinit

2019-08-19 Thread Mark Hatle
On 8/19/19 11:49 AM, Otavio Salvador wrote: > On Mon, Aug 19, 2019 at 1:48 PM Mark Hatle wrote: >> On 8/19/19 11:27 AM, Ross Burton wrote: >>> On 19/08/2019 11:37, Otavio Salvador wrote: On Sun, Aug 18, 2019 at 11:00 PM Kang Kai wrote: > On 2019/8/18 上午3:27, Otavio Salvador wrote: >

Re: [OE-core] [PATCH] libffi: Upgrade to 3.3-rc0

2019-08-19 Thread Khem Raj
On Mon, Aug 19, 2019 at 7:31 AM Ross Burton wrote: > On 14/08/2019 23:46, Khem Raj wrote: > > On Wed, Aug 14, 2019 at 3:42 PM akuster808 wrote: > >> > >> > >> > >> On 8/14/19 3:29 PM, Khem Raj wrote: > >>> libffi 3.1 release has been a bit aged and new architectures, compilers > >>> have since

Re: [OE-core] [PATCH] systemd: decreasing default RLIMIT_NOFILE on qemu bsp

2019-08-19 Thread Alexander Kanavin
On Mon, 19 Aug 2019 at 16:55, wrote: > I'd even possibly accept a case for higher memory defaults for graphics > images when GL is enabled. Pushing the default qemu memory size to > 512MB everywhere is wrong though and sends out the wrong message for > the project. > Thanks for the response (I

Re: [OE-core] [PATCH] libffi: Upgrade to 3.3-rc0

2019-08-19 Thread Khem Raj
On Mon, Aug 19, 2019 at 9:20 AM Ross Burton wrote: > > On 19/08/2019 16:09, Khem Raj wrote: > > Set the PV to 3.3~rc0 and 3.3 will sort after it. > > > > > > I thinking using + terminology is familiar in OE world let’s stick to it > > I worked on adding ~ explicitly for this exact problem (as

[OE-core] [PATCH V2] systemd: add menson option to decrease RLIMIT_NOFILE on qemu bsp

2019-08-19 Thread Hongxu Jia
Since do_testimage for core-image-sato-sdk has memory limitation (256Mib) which caused rpc.statd failed with out of memory. [ 531.306146] Out of memory: Kill process 193 (rpc.statd) score 200 or sacrifice child The rpc.statd allocates memory according to RLIMIT_NOFILE, so decrease RLIMIT_NOFILE

[OE-core] [PATCH V4 1/2] libffi: Upgrade to 3.3-rc0

2019-08-19 Thread Khem Raj
libffi 3.1 release has been a bit aged and new architectures, compilers have since been come on stage to compile it, we have been carrying patches, but its better to use the latest 3.3 rc0 which has lot of these issues handled and is in good shape. Use 3.3~rc0 for PV to keep room for upgrade path

[OE-core] [PATCH 2/2] opensbi: Disable SECURITY_CFLAGS since it cant link with libssp

2019-08-19 Thread Khem Raj
Signed-off-by: Khem Raj --- meta/recipes-bsp/opensbi/opensbi_0.4.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-bsp/opensbi/opensbi_0.4.bb b/meta/recipes-bsp/opensbi/opensbi_0.4.bb index 382752895c..b030436688 100644 --- a/meta/recipes-bsp/opensbi/opensbi_0.4.bb +++

Re: [OE-core] Long delays with latest bitbake (was: [PATCH 1/7] insane.bbclass: in file-rdeps do not look into RDEPENDS recursively)

2019-08-19 Thread Martin Jansa
On Fri, Aug 16, 2019 at 07:22:55PM +0200, Martin Jansa wrote: > On Fri, Aug 16, 2019 at 04:54:48PM +0100, richard.pur...@linuxfoundation.org > wrote: > > On Fri, 2019-08-16 at 17:00 +0200, Martin Jansa wrote: > > > > Will try to bump BB_NUMBER_THREADS from 8 to 72. > > > > > > I've tried to

[OE-core] [PATCH] qemumips/qemumips64: move QB_SYSTEM_NAME to corresponding conf

2019-08-19 Thread changqing.li
From: Changqing Li Configuration: MACHINE = qemumips64 bitbake lib32-core-image-minimal runqemu slirp nographic qemumips64 ext4 Error: ERROR - Failed to run qemu: qemu-system-mips: unable to find CPU model 'MIPS64R2-generic' Fixed by moving QB_SYSTEM_NAME to Respective configuration file

[OE-core] [PATCH] libnss-nis: upgrade 3.0 -> 3.1

2019-08-19 Thread Yuan Chao
Remove patch 0001-nis-hosts-Remove-use-of-RES_USE_INET6.patch since this is included in 3.1 Signed-off-by: Yuan Chao --- .../recipes-extended/libnss-nis/libnss-nis.bb | 5 +- ...is-hosts-Remove-use-of-RES_USE_INET6.patch | 162 -- 2 files changed, 2 insertions(+), 165

[OE-core] [PATCH V3] nfs-utils: decrease RLIMIT_NOFILE to 4k for systemd

2019-08-19 Thread Hongxu Jia
On systemd, it set RLIMIT_NOFILE to 512k, since do_testimage for core-image-sato-sdk has memory limitation (256Mib) which caused rpc.statd failed with out of memory. [ 531.306146] Out of memory: Kill process 193 (rpc.statd) score 200 or sacrifice child The rpc.statd and rpc.mountd allocates

Re: [OE-core] [PATCH] core-image-sato-sdk: test image with 512M memory

2019-08-19 Thread ChenQi
On 08/16/2019 02:53 PM, Kang Kai wrote: On 2019/8/12 下午4:57, Kang Kai wrote: On 2019/7/27 下午4:42, Kang Kai wrote: On 2019/7/27 上午5:40, richard.pur...@linuxfoundation.org wrote: On Fri, 2019-07-26 at 05:23 -0400, kai.k...@windriver.com wrote: From: Kai Kang When run do_testimage for

Re: [OE-core] [PATCH] systemd: decreasing default RLIMIT_NOFILE on qemu bsp

2019-08-19 Thread Alexander Kanavin
Should the limit be simply raised? The 256M setup is crumbling on several fronts (runtime tests, modernisation of X, various non-x86 qemu targets). Adding per-image/target exceptions, custom non-upstreamable patches, or sticking to deprecated configurations isn't the right thing to do, I think.

[OE-core] ✗ patchtest: failure for "[warrior] binutils: fix CVE-20..." and 2 more

2019-08-19 Thread Patchwork
== Series Details == Series: "[warrior] binutils: fix CVE-20..." and 2 more Revision: 1 URL : https://patchwork.openembedded.org/series/19354/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

Re: [OE-core] [PATCH v2] mesa: Upgrade 19.1.1 -> 19.1.4

2019-08-19 Thread Alexander Kanavin
On Sat, 17 Aug 2019 at 20:49, Otavio Salvador < otavio.salva...@ossystems.com.br> wrote: > I tried but couldn't figure out how to fix it and as I am not a meson > expect, I preferred to rather revert it and succeed with the upgrade. > > Can you send a patch fixing it? > Can you try adding

Re: [OE-core] Yocto Project Summit at ELCE Call for Particpation

2019-08-19 Thread Nicolas Dechesne
hi Philip, thanks for sending this out! On Mon, Aug 19, 2019 at 3:17 AM Philip Balister wrote: > > At the past few OopenEmbedded developer meetings, people have been > asking for more developer and user focused events like a miniconf. > Partly based on this feedback, there is a two day event

[OE-core] Yocto Project Summit at ELCE Call for Particpation

2019-08-19 Thread Philip Balister
At the past few OopenEmbedded developer meetings, people have been asking for more developer and user focused events like a miniconf. Partly based on this feedback, there is a two day event sponsored by the Yocto Project that provides a chance for people to talk about the Yocto Project and

[OE-core] [warrior][PATCH 2/3] pango: fix CVE-2019-1010238

2019-08-19 Thread Anuj Mittal
Signed-off-by: Anuj Mittal --- .../pango/pango/CVE-2019-1010238.patch | 38 ++ meta/recipes-graphics/pango/pango_1.42.4.bb| 4 ++- 2 files changed, 41 insertions(+), 1 deletion(-) create mode 100644

[OE-core] [warrior][PATCH 3/3] glib-2.0: fix CVE-2019-13012

2019-08-19 Thread Anuj Mittal
Signed-off-by: Anuj Mittal --- .../glib-2.0/glib-2.0/CVE-2019-13012.patch | 40 ++ meta/recipes-core/glib-2.0/glib-2.0_2.58.3.bb | 1 + 2 files changed, 41 insertions(+) create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2019-13012.patch diff --git

[OE-core] [warrior][PATCH 1/3] binutils: fix CVE-2019-14250 CVE-2019-14444

2019-08-19 Thread Anuj Mittal
Signed-off-by: Anuj Mittal --- meta/recipes-devtools/binutils/binutils-2.32.inc | 2 ++ .../binutils/binutils/CVE-2019-14250.patch | 33 ++ .../binutils/binutils/CVE-2019-1.patch | 28 ++ 3 files changed, 63 insertions(+) create mode

Re: [OE-core] [PATCH] systemd: decreasing default RLIMIT_NOFILE on qemu bsp

2019-08-19 Thread Hongxu Jia
On 8/19/19 10:01 PM, Alexander Kanavin wrote: Should the limit be simply raised? The 256M setup is crumbling on several fronts (runtime tests, modernisation of X, various non-x86 qemu targets). Adding per-image/target exceptions, custom non-upstreamable patches, or sticking to deprecated

[OE-core] [PATCH] systemd: decreasing default RLIMIT_NOFILE on qemu bsp

2019-08-19 Thread Hongxu Jia
Since do_testimage for core-image-sato-sdk has memory limitation (256Mib) which caused rpc.statd failed with out of memory. [ 531.306146] Out of memory: Kill process 193 (rpc.statd) score 200 or sacrifice child The rpc.statd allocates memory according to RLIMIT_NOFILE, so decrease it to 4k to

[OE-core] ✗ patchtest: failure for psplash: Avoid mount the psplash tmpfs twice

2019-08-19 Thread Patchwork
== Series Details == Series: psplash: Avoid mount the psplash tmpfs twice Revision: 1 URL : https://patchwork.openembedded.org/series/19350/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

Re: [OE-core] ✗ patchtest: failure for "[warrior] binutils: fix CVE-20..." and 2 more

2019-08-19 Thread Mittal, Anuj
On Mon, 2019-08-19 at 14:02 +, Patchwork wrote: > * Issue Series does not apply on top of target branch > [test_series_merge_on_head] > Suggested fixRebase your series on top of targeted branch > Targeted branch warrior (currently at 952bfcc3f4) This is intentional.

[OE-core] [oe-core][PATCH 2/2] ltp: Fix ustat02 failure

2019-08-19 Thread zhe.he
From: He Zhe Backport a patch to fix the following failure. ustat02.c:44: FAIL: ustat(2) failed to produce expected error; 14, errno: EFAULT: EINVAL Signed-off-by: He Zhe --- ...02-Fix-EFAULT-in-32bit-compatibility-mode.patch | 36 ++

[OE-core] [oe-core][PATCH 1/2] ltp: Fix tgkill03 failure

2019-08-19 Thread zhe.he
From: He Zhe Backport a patch to fix the followig failure. tgkill03.c:94: FAIL: Defunct tid should have failed with ESRCH: SUCCESS Signed-off-by: He Zhe --- ...kill03-wait-for-defunct-tid-to-get-detach.patch | 75 ++ meta/recipes-extended/ltp/ltp_20190517.bb | 1

[OE-core] [PATCH] psplash: Avoid mount the psplash tmpfs twice

2019-08-19 Thread Kevin Hao
The /etc/init.d/psplash.sh will be invoked both in boot and shutdown/reboot. And the psplash tmpfs will be mounted twice. This will trigger a bug in umount and let the system hang when shutdown/reboot. I already made a patch [1] to fix the issue in umount, but there is no reason for the psplash to

Re: [OE-core] Conflict of systemd and sysvinit

2019-08-19 Thread Otavio Salvador
On Sun, Aug 18, 2019 at 11:00 PM Kang Kai wrote: > On 2019/8/18 上午3:27, Otavio Salvador wrote: > Would you like to give more detailed steps how the error occurred? And > what's extra settings in you local.conf please? I had sysvinit and systemd enabled. -- Otavio Salvador

[OE-core] [PATCH] binutils: fix CVE-2019-14250 CVE-2019-14444

2019-08-19 Thread Anuj Mittal
Signed-off-by: Anuj Mittal --- meta/recipes-devtools/binutils/binutils-2.32.inc | 2 ++ .../binutils/binutils/CVE-2019-14250.patch | 33 ++ .../binutils/binutils/CVE-2019-1.patch | 28 ++ 3 files changed, 63 insertions(+) create mode