|
Yocto Project Status WW42`21
Richard Purdie
Current Dev Position: YP 3.4 M4 Next Deadline: 29th Oct. 2021 YP 3.4 M4 release Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 3.4 Milestone Dates:
Proposed YP 3.5 Milestone Dates:
Proposed upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: meta-selinux: dunfell: libselinux: 0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch fails to apply
Jonas Brich
Hi,
yes college uploaded again. That is the correct patch. Thanks BMW Car IT GmbH Jonas Brich Spezialist Entwicklung Lise-Meitner-Str. 14 89081 Ulm Tel.: +49 731 3780 4292 Mail: jonas.brich@bmw.de Web: http://www.bmw-carit.de ---------------------------------------------------------------------- BMW Car IT GmbH Geschaeftsfuehrer: Kai-Uwe Balszuweit und Michael Böttrich Sitz und Registergericht: Muenchen HRB 134810 ---------------------------------------------------------------------- ________________________________________ From: Jason Andryuk <jandryuk@gmail.com> Sent: Tuesday, October 19, 2021 3:51 PM To: joe@deserted.net; Brich Jonas, JC-4; yocto@lists.yoctoproject.org; flihp@twobit.us; yi.zhao@windriver.com Subject: meta-selinux: dunfell: libselinux: 0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch fails to apply Hi, libselinux in meta-selinux dunfell fails in do_patch. Patch 0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch fails to apply. The patch in git has a leading a/b path component, which throws off the strip level. The posting here doesn't have the a/b: https://lists.yoctoproject.org/g/yocto/message/55083 so it should work. Thanks, Jason
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[meta-parsec][v2][PATCH] meta-parsec/README: remove rust layer req.
Rust is now in core. No need to include the layer referenece.
Drop Priority and ref from repo definition. Not used Signed-off-by: Armin Kuster <akuster808@gmail.com> [v2] fixup mailing list --- meta-parsec/README.md | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/meta-parsec/README.md b/meta-parsec/README.md index 24958ac..aeb48a6 100644 --- a/meta-parsec/README.md +++ b/meta-parsec/README.md @@ -11,23 +11,12 @@ This layer depends on: URI: git://git.openembedded.org/meta-openembedded branch: master - revision: HEAD - prio: default URI git://git.yoctoproject.org/meta-security branch: master - revision: HEAD - prio: default - - URI https://github.com/meta-rust/meta-rust.git - branch: master - revision: HEAD - prio: default URI https://github.com/kraj/meta-clang.git branch: master - revision: HEAD - prio: default Adding the meta-parsec layer to your build ========================================== @@ -44,7 +33,6 @@ other layers needed. e.g.: /path/to/yocto/meta-yocto-bsp \ /path/to/meta-openembedded/meta-oe \ /path/to/meta-openembedded/meta-python \ - /path/to/meta-rust \ /path/to/meta-clang \ /path/to/meta-security/meta-tpm \ /path/to/meta-security/meta-parsec \ @@ -165,11 +153,11 @@ Maintenance Send pull requests, patches, comments or questions to yocto@yoctoproject.org When sending single patches, please using something like: -'git send-email -1 --to yocto@yoctoproject.org --subject-prefix=meta-parsec][PATCH' +'git send-email -1 --to yocto@lists.yoctoproject.org --subject-prefix=meta-parsec][PATCH' These values can be set as defaults for this repository: -$ git config sendemail.to yocto@yoctoproject.org +$ git config sendemail.to yocto@lists.yoctoproject.org $ git config format.subjectPrefix meta-parsec][PATCH Now you can just do 'git send-email origin/master' to send all local patches. -- 2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[meta-parsec][PATCH] meta-parsec/README: remove rust layer req.
Rust is now in core. No need to include the layer referenece.
Drop Priority and ref from repo definition. Not used Signed-off-by: Armin Kuster <akuster808@gmail.com> --- meta-parsec/README.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/meta-parsec/README.md b/meta-parsec/README.md index 24958ac..84cf4a6 100644 --- a/meta-parsec/README.md +++ b/meta-parsec/README.md @@ -11,23 +11,12 @@ This layer depends on: URI: git://git.openembedded.org/meta-openembedded branch: master - revision: HEAD - prio: default URI git://git.yoctoproject.org/meta-security branch: master - revision: HEAD - prio: default - - URI https://github.com/meta-rust/meta-rust.git - branch: master - revision: HEAD - prio: default URI https://github.com/kraj/meta-clang.git branch: master - revision: HEAD - prio: default Adding the meta-parsec layer to your build ========================================== @@ -44,7 +33,6 @@ other layers needed. e.g.: /path/to/yocto/meta-yocto-bsp \ /path/to/meta-openembedded/meta-oe \ /path/to/meta-openembedded/meta-python \ - /path/to/meta-rust \ /path/to/meta-clang \ /path/to/meta-security/meta-tpm \ /path/to/meta-security/meta-parsec \ -- 2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [meta-cgl][PATCH] libsocket6-perl: inherit autotools-brokensep
Merged, thanks.
toggle quoted messageShow quoted text
On 10/14/2021 11:04 PM, Yi Zhao wrote:
Inherit autotools-brokensep to fix the build error which is introduced
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Enhancements/Bugs closed WW42!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Current high bug count owners for Yocto Project 3.5
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi 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 397 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.4”, “3.5, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.
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.pm@...) 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.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@prashant2314
Dear Team,
I've built a desktop based image for Rpi4, now I need to configure the network from front end not via terminal access, so for this I'm not getting solution, please assist me if some one have any suggestion on the same. Thanks is advance,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.4.rc1)
Teoh, Jay Shen
Hi All,
toggle quoted messageShow quoted text
This is the full report for yocto-3.4.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone defects. No new issue found. Thanks, Jay
-----Original Message-----
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [PATCH v2 1/1] sssd: re-package to fix QA issues
kai
On 10/14/21 4:59 PM, kai wrote:
From: Kai Kang <kai.kang@...> It packages all file in ${libdir} to package sssd, including the .so symlink files. Then it causes QA issues: | ERROR: QA Issue: sssd rdepends on dbus-dev [dev-deps] | ERROR: QA Issue: sssd rdepends on ding-libs-dev [dev-deps] So re-package sssd then the .so symlink files and .pc files are packaged to sssd-dev which should be. File ${libdir}/libsss_sudo.so is not a symlink file but packaged to sssd-dev too. Then causes another QA issue: | ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue: -dev package sssd-dev contains non-symlink .so '/usr/lib/libsss_sudo.so' [dev-elf] So create a new sub-package libsss-sudo to package file libsss_sudo.so and make sssd rdepends on it. Hi Armin, Ping in case you may miss it. Regards, Signed-off-by: Kai Kang <kai.kang@...> --- recipes-security/sssd/sssd_2.5.2.bb | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/recipes-security/sssd/sssd_2.5.2.bb b/recipes-security/sssd/sssd_2.5.2.bb index 76d6e03..ed8af5e 100644 --- a/recipes-security/sssd/sssd_2.5.2.bb +++ b/recipes-security/sssd/sssd_2.5.2.bb @@ -125,10 +125,14 @@ SYSTEMD_SERVICE:${PN} = " \ " SYSTEMD_AUTO_ENABLE = "disable" -FILES:${PN} += "${libdir} ${datadir} ${base_libdir}/security/pam_sss*.so" -FILES:${PN}-dev = " ${includedir}/* ${libdir}/*la ${libdir}/*/*la" +PACKAGES =+ "libsss-sudo" +ALLOW_EMPTY:libsss-sudo = "1" -# The package contains symlinks that trip up insane -INSANE_SKIP:${PN} = "dev-so" +FILES:${PN} += "${base_libdir}/security/pam_sss*.so \ + ${datadir}/dbus-1/system-services/*.service \ + ${libdir}/krb5/* \ + ${libdir}/ldb/* \ + " +FILES:libsss-sudo = "${libdir}/libsss_sudo.so" -RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam" +RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam libsss-sudo"
-- Kai Kang Wind River Linux
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: SRC_URI Directory Change
On Fri, Oct 15, 2021 at 6:58 AM Richard Purdie <richard.purdie@...> wrote:
I tested the patch you posted on IRC against bitbake 1.50.0. It seems to work quite well, but I think I found two minor bugs in it. I pasted an updated patch below. In a nutshell... If you have a SRC_URI file:// entry that ends in a "/", then you get a "." that is not enclosed in "/./" when running the checksum_dir method, which causes checksum_file to throw warnings that look like this: I think the simplest fix is to add a "pth = pth.rstrip("/")" in the checksum_dir method after the guard statement. But then that exposes a different issue in the patch. For recipes that trigger the above warning, the rstrip() fix fixes the warning, but then you expose a new problem in siggen.py calc_taskhash(). In your patched version, the check for the "/" fails to include the filename in the hash calculation for files at the root of a SRC_URI entry (there is no "/" to be found). This results in a task hash mismatch error on the first build, but not on subsequent builds for fairly obvious reasons. I solved this by adding a third field to the tuple with a True/False value, which is a much more reliable semaphore (IMHO). I tested these fixes and it worked perfectly. Here is an updated version of your patch that takes into account the fixes I described. I can produce a "patch against your patch" if these fixes are considered correct and do not cause even bigger problems that are not obvious to me. diff --git a/bitbake/lib/bb/checksum.py b/bitbake/lib/bb/checksum.py
index 1d50a26426..fb8a77f6ab 100644
--- a/bitbake/lib/bb/checksum.py
+++ b/bitbake/lib/bb/checksum.py
@@ -50,6 +50,7 @@ class FileChecksumCache(MultiProcessCache):
MultiProcessCache.__init__(self)
def get_checksum(self, f):
+ f = os.path.normpath(f)
entry = self.cachedata[0].get(f)
cmtime = self.mtime_cache.cached_mtime(f)
if entry:
@@ -84,15 +85,24 @@ class FileChecksumCache(MultiProcessCache):
return None
return checksum
+ #
+ # Changing the format of file-checksums is problematic as both OE and Bitbake have
+ # knowledge of them. We need to encode a new piece of data, the portion of the path
+ # we care about from a checksum perspective. This means that files that change subdirectory
+ # are tracked by the task hashes. To do this, we do something horrible and put a "/./" into
+ # the path. The filesystem handles it but it gives us a marker to know which subsection
+ # of the path to cache.
+ #
def checksum_dir(pth):
# Handle directories recursively
if pth == "/":
bb.fatal("Refusing to checksum /")
+ pth = pth.rstrip("/")
dirchecksums = []
for root, dirs, files in os.walk(pth, topdown=True):
[dirs.remove(d) for d in list(dirs) if d in localdirsexclude]
for name in files:
- fullpth = os.path.join(root, name)
+ fullpth = os.path.join(root, name).replace(pth, os.path.join(pth, "."))
checksum = checksum_file(fullpth)
if checksum:
dirchecksums.append((fullpth, checksum))
diff --git a/bitbake/lib/bb/siggen.py b/bitbake/lib/bb/siggen.py
index 0d88c6ec68..f649f39ced 100644
--- a/bitbake/lib/bb/siggen.py
+++ b/bitbake/lib/bb/siggen.py
@@ -308,13 +308,14 @@ class SignatureGeneratorBasic(SignatureGenerator):
return
def get_taskhash(self, tid, deps, dataCaches):
-
data = self.basehash[tid]
for dep in self.runtaskdeps[tid]:
data = data + self.get_unihash(dep)
for (f, cs) in self.file_checksum_values[tid]:
if cs:
+ if "/./" in f:
+ data = data + f.split("/./")[1]
data = data + cs
if tid in self.taints:
@@ -372,7 +373,12 @@ class SignatureGeneratorBasic(SignatureGenerator):
if runtime and tid in self.taskhash:
data['runtaskdeps'] = self.runtaskdeps[tid]
- data['file_checksum_values'] = [(os.path.basename(f), cs) for f,cs in self.file_checksum_values[tid]]
+ data['file_checksum_values'] = []
+ for f,cs in self.file_checksum_values[tid]:
+ if "/./" in f:
+ data['file_checksum_values'].append((f.split("/./")[1], cs, True))
+ else:
+ data['file_checksum_values'].append((os.path.basename(f), cs, False))
data['runtaskhashes'] = {}
for dep in data['runtaskdeps']:
data['runtaskhashes'][dep] = self.get_unihash(dep)
@@ -1017,6 +1023,8 @@ def calc_taskhash(sigdata):
for c in sigdata['file_checksum_values']:
if c[1]:
+ if c[2]:
+ data = data + c[0]
data = data + c[1]
if 'taint' in sigdata:..Ch:W.. P.S. The gettext-minimal-native_0.21.bb (from OEC) is a very good example of something that triggers this behavior. But I found plenty of others as well. "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: How to enable graphics acceleration on qemux86-64?
Alexander Kanavin
On Sat, 16 Oct 2021 at 14:08, Manuel Wagesreither <ManWag@...> wrote:
You need to replicate the settings from oe-selftest (link provided previously). I think on dunfell it's not enabled out of the box, and needs to be configured explicitly.
DISPLAY is a setting for the host, so qemu can display the sdl or gtk window. On the qemu guest you need to get weston to start first. Alex
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: How to enable graphics acceleration on qemux86-64?
Manuel Wagesreither
Am Mi, 13. Okt 2021, um 22:56, schrieb Alexander Kanavin:
Here are some updates: Building core-image-weston on hardknott succeeded. Couldn't `runqmu kvm slirp sdl core-image-weston` first because I got an error message about 'dri.pc' being missing. Debian package search told me it's part of 'mesa-commond-dev', so I installed it on my host machine and indeed, that runqemu command above got working again. Not just that, now even OpenGL acceleration with `runqmu kvm slirp sdl gl core-image-weston` worked, altough I didn't change anything OpenGL-wise. core-image-weston feels really snappy now. Great! I got curious and reverted back to dunfell to check if the now-installed dri.pc made a difference, but no, it didn't. `runqemu` with `sdl` started (like it did before), and with `sdl gl` it still said "OpenGL support is disabled". Ok, so then I moved on to get my own image which is on hardknott now working. I `runqemu`d my image with 'sdl' and 'gl' and it started up fine. Weston did no longer start automatically so I did manually. Ran `DISPLAY=:0 glxgears` but it told me "couldn't open display :0". Installed 'weston-xwayland' so I'd get "/usr/lib/libweston-9/xwayland.so" but that didn't change anything. Can't yet say if `DISPLAY=:0 glxgears` works on core-image-weston as it's still building. Regards, Manuel
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Dunfell: problem with kernel-module install and libkmod.so
Patrick Boettcher
Hi list,
I'm facing an issue with a BSP I created using dunfell (up-to-date on poky and oe). I'm using a stable kernel and u-boot 2021.07 from denx's mainline-stable-layer. I stripped down my machine.conf and basically the boot is working fine. Was working fine. When finally I created a functional defconfig (one which didn't strip down the kernel next to nothing - thanks to KCONFIG_MODE="alldefconfig" ). I started to create fragments to remove unused parts. The very first fragment I created was leading to rootfs which crashed at the moment when /sbin/init was invoked, with the strangest errors I've ever seen: /sbin/init: error while loading shared libraries: libkmod.so.2: cannot open shared object file: No such file or directory Of course libkmod.so.2 (and its target) is present. Then I realized that no modules where installed in the rootfs. (modules are there if I don't have the fragment) So I added kernel-modules to IMAGE_INSTALL:append . The modules appeared, but the panic still occurred. What can I do to understand what's going on? I diff'ed the rootfs, the only difference I could was in ldconfig's aux-cache. Thanks for any help in advance, -- Patrick.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: SRC_URI Directory Change
Richard Purdie
On Fri, 2021-10-15 at 03:03 -0700, Chuck Wolber wrote:
Is there a recommended strategy to get do_fetch to invalidate on directoryI can see why this breaks and it isn't entirely straightforward to fix since we'd have to add data to the file-checksums entries which are generated by both OE and Bitbake. I have a bit of a horrible idea to do this in master-next which does solve the problem. We probably need a new bitbake selftest testcase before I could think about merging it though. Cheers, Richard
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[PATCH][meta-selinux][dunfell] MAINTAINERS: update email address
Mikko Rapeli
From: Armin Kuster <akuster808@gmail.com>
Include example send-email Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Joe MacDonald <joe@deserted.net> (cherry picked from commit 48038b45dc114592991c069eb66d174820c0701d) --- MAINTAINERS | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 36c451f..0dc492e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1,7 +1,14 @@ This file contains a list of maintainers for the meta-selinux layer. Please submit any patches against meta-selinux to the Yocto Project mailing -list (yocto@yoctoproject.org). +list (yocto@lists.yoctoproject.org). + +git send-email -1 --to yocto@lists.yoctoproject.org --subject-prefix=meta-selinux][PATCH + +These values can be set as defaults for this repository: + +$ git config sendemail.to yocto@lists.yoctoproject.org +$ git config format.subjectPrefix meta-selinux][PATCH You may also contact the maintainers directly. -- 2.20.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[PATCH][meta-selinux][dunfell] libselinux: Backport NULL pointer fix from 3.1
Jonas Brich
From: Mikko Rapeli <mikko.rapeli@bmw.de>
From: Jonas Brich <Jonas.Brich@bmw.de> Using function restorecon_init inside selinux_restorecon.c can result in a NULL pointer. This happens because function selinux_restorecon_set_sehandle can return a NULL pointer. But it is not checked and directly given to the next function. This problem is already fixed in libselinux 3.1 and above. Therefore backport this fix. Signed-off-by: Jonas Brich <Jonas.Brich@bmw.de> --- ...e-in-selinux_restorecon_set_sehandle.patch | 32 +++++++++++++++++++ recipes-security/selinux/libselinux_3.0.bb | 1 + 2 files changed, 33 insertions(+) create mode 100644 recipes-security/selinux/libselinux/0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch diff --git a/recipes-security/selinux/libselinux/0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch b/recipes-security/selinux/libselinux/0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch new file mode 100644 index 0000000..f12164f --- /dev/null +++ b/recipes-security/selinux/libselinux/0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch @@ -0,0 +1,32 @@ +From 08f5e30177218fae7ce9f5c8d6856690126b2b30 Mon Sep 17 00:00:00 2001 +From: Ji Qin <jiqin.ji@huawei.com> +Date: Sun, 14 Jun 2020 21:20:23 -0400 +Subject: [PATCH] libselinux: Fix NULL pointer use in + selinux_restorecon_set_sehandle + +error occur when selinux_restorecon_default_handle return NULL in +restorecon_init. + +fixes: https://github.com/SELinuxProject/selinux/issues/249 + +Signed-off-by: Ji Qin <jiqin.ji@huawei.com> +Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com> +--- + libselinux/src/selinux_restorecon.c | 2 ++ + 1 file changed, 2 insertions(+) + +Upstream-Status: Backport [https://github.com/SELinuxProject/selinux/commit/08f5e30177218fae7ce9f5c8d6856690126b2b30] + +diff --git libselinux/src/selinux_restorecon.c libselinux/src/selinux_restorecon.c +index d1ce830c5..6993be6fd 100644 +--- libselinux/src/selinux_restorecon.c ++++ libselinux/src/selinux_restorecon.c +@@ -1154,6 +1154,8 @@ void selinux_restorecon_set_sehandle(struct selabel_handle *hndl) + size_t num_specfiles, fc_digest_len; + + fc_sehandle = (struct selabel_handle *) hndl; ++ if (!fc_sehandle) ++ return; + + /* Check if digest requested in selabel_open(3), if so use it. */ + if (selabel_digest(fc_sehandle, &fc_digest, &fc_digest_len, diff --git a/recipes-security/selinux/libselinux_3.0.bb b/recipes-security/selinux/libselinux_3.0.bb index 17a25a9..01f9b7b 100644 --- a/recipes-security/selinux/libselinux_3.0.bb +++ b/recipes-security/selinux/libselinux_3.0.bb @@ -13,4 +13,5 @@ SRC_URI += "\ file://libselinux-define-FD_CLOEXEC-as-necessary.patch \ file://0001-Fix-building-against-musl-and-uClibc-libc-libraries.patch \ file://0001-libselinux-export-flush_class_cache-call-it-on-polic.patch \ + file://0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch \ " -- 2.20.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
SRC_URI Directory Change
Is there a recommended strategy to get do_fetch to invalidate on
directory path changes in paths pointed to by file:// URLs in SRC_URI? Example: SRC_URI += "file://src;subdir=${S}" A
file at src/foo/bar/baz is recognized just fine. But then a directory
change to something like src/foo/bar2/baz is not recognized and does not
invalidate any tasks in subsequent builds. Use
case is a recipe that has a fair bit of metadata that is not even
remotely amenable to the typical flat layout expected of a set of
patches. ..Ch:W.. P.S.
I attempted to do this with an event handler that was run when
bb.event.RecipePreFinalise is is fired. It would compare directory trees
and set do_fetch[nostamp] = "1" to invalidate the fetcher task. But I
got really spotty behavior. It seems like event handlers are cached
like tasks. -- "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[meta-cgl][PATCH] libsocket6-perl: inherit autotools-brokensep
Yi Zhao
Inherit autotools-brokensep to fix the build error which is introduced
by oe-commit: commit 8e26252b45b7660c7c67c702411bdec187a76ffc Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Sun Sep 19 16:17:31 2021 +0100 layer.conf: Extend recipes not to install without explict dependencies Fixes: libsocket6-perl/0.29-r2/temp/run.do_configure.27951: autoreconf: not found libsocket6-perl/0.29-r2/temp/run.do_configure.27951: oefatal: not found Signed-off-by: Yi Zhao <yi.zhao@windriver.com> --- meta-cgl-common/recipes-perl/perl/libsocket6-perl_0.29.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-cgl-common/recipes-perl/perl/libsocket6-perl_0.29.bb b/meta-cgl-common/recipes-perl/perl/libsocket6-perl_0.29.bb index bbeab8e..9f38380 100644 --- a/meta-cgl-common/recipes-perl/perl/libsocket6-perl_0.29.bb +++ b/meta-cgl-common/recipes-perl/perl/libsocket6-perl_0.29.bb @@ -23,4 +23,4 @@ do_configure:prepend () { sed -i 's:\./configure\(.[^-]\):./configure --build=${BUILD_SYS} --host=${HOST_SYS} --target=${TARGET_SYS} --prefix=${prefix} --exec_prefix=${exec_prefix} --bindir=${bindir} --sbindir=${sbindir} --libexecdir=${libexecdir} --datadir=${datadir} --sysconfdir=${sysconfdir} --sharedstatedir=${sharedstatedir} --localstatedir=${localstatedir} --libdir=${libdir} --includedir=${includedir} --oldincludedir=${oldincludedir} --infodir=${infodir} --mandir=${mandir}\1:' Makefile.PL } -inherit cpan +inherit autotools-brokensep cpan -- 2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|