linux/poky.git, branch yocto-2.2.2

uninative: Update to 1.7 uninative release

2017-09-06T15:54:37+00:00

This updates to a newer glibc and updates patchelf to include a bugfix to work with gold. (From OE-Core rev: a2ab288bd002ebb6e64d46e941fb122e1157ff49) (From OE-Core rev: 32d172c25072251d6cc7fdd40929d76b5f1f5059) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

yocto-uninative: Update to the 1.6 release

2017-09-06T15:54:37+00:00

This release includes fixes for Windows/Mingw support. (From OE-Core rev: b5f471b74b2da533abfad2601b221fa806fcf3b2) (From OE-Core rev: 267e10420cac19ac3c1194d32993c3407bdc90f6) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

yocto-uninative: Update to the 1.5 release

2017-09-06T15:54:37+00:00

This upgrades to a version of patchelf which works on newer distros and doesn't inflate binaries in crazy ways. (From OE-Core rev: b857ec92564ee3f23adf88d2675d920aff13e141) (From OE-Core rev: 1496ae0ab32315537649dea7e5a22a16fae0a528) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

python3-native: Avoid use of getentropy/getrandom

2017-09-06T15:54:37+00:00

getentropy/random() is only available in glibc 2.25+ and uninative may relocate binaries onto systems that don't have this function. For now, force the code to the older codepaths until we can come up with a better solution for this kind of issue. (From OE-Core rev: 92bda0024d85ae78345665cc2f9646c9881ed61b) (From OE-Core rev: 2dc6ee0c520442418fa14cf3fe12b059209e9ab7) Signed-off-by: Richard Purdie

python-numpy: Fix issues with recent glibc versions

2017-09-06T15:53:39+00:00

Fix issues building on recent glibc versions (for python*-numpy-native). (From OE-Core rev: 08a46b2477c1ea0e76695b51b59dc1bb46b1b521) Signed-off-by: Richard Purdie

qemu: Backport a patch for recent glibc versions

2017-09-06T15:53:39+00:00

This fixes compile failures of qemu-native with new versions of glibc. Patch is taken from upstream. (From OE-Core rev: b1b7a46f0febe7ac17ec46ecdf88b4120a7d75c4) Signed-off-by: Richard Purdie

recipes-kernel: Skip kernel version check on kernel templates

2017-09-04T16:38:09+00:00

Currently, SRCREV is set to AUTOREV, causing mismatch between PV and the kernel version shown in the makefile (see below to see the bitbake log). The solution is to comment the lines which defaults SRCREV to AUTOREV, leaving the previous comment to replace the SRCREVs for real ones once kernel changes are done. ERROR: linux-yocto-4.8.12+gitAUTOINC+4fb6f24600_d4148a2064-r0.1 do_kernel_version_sanity_check: Package Version (4.8.12+gitAUTOINC +4fb6f24600_d4148a2064) does not match of kernel being built (4.8.21). Please update the PV variable to match the kernel source. ERROR: linux-yocto-4.8.12+gitAUTOINC+4fb6f24600_d4148a2064-r0.1 do_kernel_version_sanity_check: Function failed: do_kernel_version_sanity_check (log file is located at ../tmp/work/myqemu-poky-linux/linux-yocto/4.8.12+gitAUTOINC+4fb6f24600_d4148a2064-r0.1/temp/log.do_kernel_version_sanity_check.17509) [YOCTO #11064] (From meta-yocto rev: 51a42001c39d1b7c8170cc84904fa915295f1358) Signed-off-by: Leonardo Sandoval Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

connman: Fix for CVE-2017-12865

2017-09-04T16:38:09+00:00

dnsproxy: Fix crash on malformed DNS response If the response query string is malformed, we might access memory pass the end of "name" variable in parse_response(). [YOCTO #11959] (From OE-Core rev: fb3e30e45eea2042fdb0b667cbc2c79ae3f5a1a9) (From OE-Core rev: 55a5a609e7c25fa3e62e1975a33a9cc10448165c) Signed-off-by: Sona Sarmadi Signed-off-by: Richard Purdie Signed-off-by: Sona Sarmadi Conflicts: meta/recipes-connectivity/connman/connman_1.33.bb Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

scripts/runqemu: avoid overridden user input for bootparams

2017-09-04T16:38:09+00:00

Currently runqemu hardcodes the "ip=" kernel boot parameter when configuring QEMU to use tap or slirp networking. This makes the guest system to have a network interface pre-configured by kernel and causes systemd to fail renaming the interface to whatever pleases it: Feb 21 10:10:20 intel-corei7-64 systemd-udevd[201]: Error changing net interface name 'eth0' to 'enp0s3': Device or resource busy, Always append user input for kernel boot params after the ones added by the script. This way user input has priority over runqemu's default params. (From OE-Core rev: 3f68b5c8d24b52aed5bb3ed970dd8f779b65b1b3) (From OE-Core rev: 6050b4ac146722d6714589225ad58ccc26c9ca32) Signed-off-by: Dmitry Rozhkov Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

kernel, license, sstate, rootfs.py: Remove deploy directory README

2017-08-29T22:43:50+00:00

It isn't clear that the README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt file in the deploy directory warrants the complexity it brings elsewhere. Let's just remove it entirely. In particular, if two do_image_complete tasks run in parallel they risk both trying to put their image into ${DEPLOY_DIR_IMAGE} at the same time. Both will contain a README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt file. In theory this should be safe because "cp -alf" will just cause one to overwrite the other. Unfortunately, coreutils cp also has a race[1] which means that if one copy creates the file at just the wrong point the other will fail with: cp: cannot create hard link ‘..../tmp-glibc/deploy/images/pantera/README_-_DO_NOT_DELETE_FILES_IN_THIS_D.txt’ to +‘..../tmp-glibc/work/rage_against-oe-linux-gnueabi/my-own-image/1.0-r0/deploy-my-own-image-complete/README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt’: File exists [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25680 (From OE-Core rev: 71e9e88847d7000781642ea6187ebd8f40dfdcfe) (From OE-Core rev: 20c39fdbb25c1b1867709c5bfb3ae2baef249be9) Signed-off-by: Mike Crowe Signed-off-by: Ross Burton Signed-off-by: Richard Purdie