linux/poky.git/meta/recipes-connectivity, branch master-next2

openssl: Enable os option for with-rand-seed as well

2019-09-18T10:52:02+00:00

with openSSL 1.1.1d we start seeing errors like Error Generating Key 139979727451584:error:2406C06E:random number generator:RAND_DRBG_instantiate:error retrieving entropy:../openssl-1.1.1d/crypto/rand/drbg_lib.c:342: when using openssl from openssl-native on build hosts, this is due to limiting the random seed to devrandom, to support older hosts, since the option allows to have a comma separated list of methods to try, we can try the default first and if that fails then fallback to devrandom, this will ensure that it keeps working with build systems which dont support getrandom() (From OE-Core rev: 40b1c65943c236abe0bff0347628e17b9bf905c2) Signed-off-by: Khem Raj Cc: Adrian Bunk Cc: Alexander Kanavin Signed-off-by: Richard Purdie

openssl: Upgrade 1.1.1c -> 1.1.1d

2019-09-16T22:02:45+00:00

Backported patches removed. (From OE-Core rev: 24174c6dafefec4ff3bd79b3c871b17cbfa3e840) Signed-off-by: Adrian Bunk Signed-off-by: Richard Purdie

nfs-utils: fix nfs mount error on 32bit nfs server

2019-09-16T22:02:44+00:00

There is a client side error "Stale file handle" when mounting from a nfs server running on 32bit arch. Steps to reproduce: 1. $ MACHINE=qemux86 bitbake core-image-sato 2. $ runqemu qemux86 kvm nographic qemuparams="-m 1024" 3. $ echo "/nfs_root *(insecure,rw,async,no_root_squash,no_subtree_check)" \ >> /etc/exports $ /etc/init.d/nfsserver restart root@qemux86:~# mount -t nfs 127.0.0.1:/nfs_root /mnt mount: mounting 127.0.0.1:/nfs_root on /mnt failed: Stale file handle Backport a patch to fix this issue. (From OE-Core rev: 727e6ce1f904abf1a1059fde759c3aaea37de199) Signed-off-by: Yi Zhao Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

iw: upgrade to 5.3

2019-09-16T22:02:43+00:00

Separated build dir doesn't work because Makefile points out source dir. (From OE-Core rev: fef943ab63d30bd1d6f9be00b0976000a55cca0e) Signed-off-by: Changhyeok Bae Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

avahi: launch avahi-daemon after connman

2019-09-01T21:33:08+00:00

When connman installed to image, /etc/resolv.conf is link to /etc/resolv-conf.connman. So launch avahi-daemon after connman too just same as after systemd-resolved.service. (From OE-Core rev: b4673b5befa339b2ffc3c274b105ab96d730ea2d) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

avahi-ui: support usrmerge

2019-09-01T21:33:07+00:00

(From OE-Core rev: 6e1fc83e7d7285211ae24e38b8fa7fbe7112d126) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie

bind: fix build with python3 PACKAGECONFIG enabled

2019-08-30T16:10:28+00:00

If the PACKAGECONFIG item, python3, is enabled, we get the following QA issue when multilib is enabled. ERROR: bind-9.11.5-P4-r0 do_package: QA Issue: bind: Files/directories were installed but not shipped in any package: /usr/lib /usr/lib/python3.7 /usr/lib/python3.7/site-packages /usr/lib/python3.7/site-packages/isc-2.0-py3.7.egg-info /usr/lib/python3.7/site-packages/isc /usr/lib/python3.7/site-packages/isc/policy.py [snip] The thing is, when --with-python is specified with a path instead of 'yes', the --with-python-install-dir is in fact ignored. Fix this issue by specifying the correct arguments. (From OE-Core rev: 2c36b3e5c7caae07ffe0cfb816d37fad52d69fc9) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

bluez5: fix build against libc-headers 5.2+

2019-08-30T16:10:28+00:00

Backporting the following upstream commit to fix the build against kernel 5.2+ headers: [ Subject: [PATCH] tools: Fix build after y2038 changes in glibc The 32-bit SIOCGSTAMP has been deprecated. Use the deprecated name to fix the build. ] Upstream-Status: backport commit f36f71f60b1e68c0f12e615b9b128d089ec3dd19 (From OE-Core rev: b4731a1202cfa45c7e1f635552398b89a37f2eeb) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

nfs-utils: 2.3.3 -> 2.4.1

2019-08-30T16:10:28+00:00

- Remove 0001-Do-not-pass-null-pointer-to-freeaddrinfo.patch, the new api can check the pointer before free it. - Rmove 0001-makefile.am-update-the-path-of-libnfs.a.patch, it is already in the source. - Rmove nfs-utils-musl-limits.patch, it is already fixed. - Rebased the following patches: 0001-Makefile.am-fix-undefined-function-for-libnsm.a.patch 0001-configure.ac-Do-not-fatalize-Wmissing-prototypes.patch bugfix-adjust-statd-service-name.patch nfs-utils-musl-res_querydomain.patch (From OE-Core rev: 5601523e16ebd35d7de8d22ec5590618ea9f7ffb) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

nfs-utils: decrease RLIMIT_NOFILE to 4k for systemd

2019-08-22T21:48:26+00:00

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 memory according to RLIMIT_NOFILE, so decrease it to 4k to keep sync with sysvinit After applying the patch, the memory cost is the same with sysvinit: root@qemux86-64:~# systemctl status nfs-statd * nfs-statd.service - NFS status monitor for NFSv2/3 locking. Loaded: loaded (/lib/systemd/system/nfs-statd.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-08-20 03:16:18 UTC; 3min 26s ago Main PID: 343 (rpc.statd) Tasks: 1 (limit: 271) Memory: 1.0M root@qemux86-64:~# systemctl status nfs-mountd * nfs-mountd.service - NFS Mount Daemon Loaded: loaded (/etc/systemd/system/nfs-mountd.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-08-20 03:19:01 UTC; 1min 21s ago Main PID: 451 (rpc.mountd) Tasks: 1 (limit: 271) Memory: 736.0K Suggested-by: Chen Qi (From OE-Core rev: 6d61cd2bdc9e326eaa59082b5dd7423e522b96d3) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie