date:20220704

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.2.rc1)

2022-07-04 Thread Teoh, Jay Shen

Hi All,

QA for yocto-4.0.2.rc1 is completed. This is the full report for this release:  
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-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Wednesday, 29 June, 2022 7:48 PM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-4.0.2.rc1)
> 
> 
> A build flagged for QA (yocto-4.0.2.rc1) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-4.0.2.rc1
> 
> 
> Build hash information:
> 
> bitbake: b8fd6f5d9959d27176ea016c249cf6d35ac8ba03
> meta-agl: c4cc627f4d65da8c3b0860c791d9b9687ba8f5d6
> meta-arm: af928569b421431347c84f5941cee7aaa9f0ac74
> meta-aws: 8b8eec4bde3b1ff00783503bd77b3a5fb7d904ec
> meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
> meta-intel: ef3aa3064b9bbfa19f600eafb1e7d3473f62af74
> meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1
> meta-openembedded: fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7
> meta-virtualization: 320f44c6e9af463a85b58e0d87ca70273c6b87f6
> oecore: eea52e0c3d24c79464f4afdbc3c397e1cb982231
> poky: a5ea426b1da472fc8549459fff3c1b8c6e02f4b5
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57447): https://lists.yoctoproject.org/g/yocto/message/57447
Mute This Topic: https://lists.yoctoproject.org/mt/92179326/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc][PATCH 1/1] crypto: caam: fix a build error 'needs_entropy_delay_adjustment' undefined

2022-07-04 Thread Xiaolei Wang

Fix commit f816aa7947c7 merge conflict, refer to
commit dd36037d4ae7 ("crypto: CAAM - fix i.mx6sx
entry delay value"), needs_ entropy_ delay_ Adjustment
function is referenced for this reason.

Signed-off-by: Xiaolei Wang 
---
 drivers/crypto/caam/ctrl.c | 25 ++---
 1 file changed, 18 insertions(+), 7 deletions(-)

diff --git a/drivers/crypto/caam/ctrl.c b/drivers/crypto/caam/ctrl.c
index 6cd43ddb403b..37e01b0faf38 100644
--- a/drivers/crypto/caam/ctrl.c
+++ b/drivers/crypto/caam/ctrl.c
@@ -612,6 +612,13 @@ static void caam_dma_dev_unregister(void *data)
platform_device_unregister(data);
 }
 
+static bool needs_entropy_delay_adjustment(void)
+{
+if (of_machine_is_compatible("fsl,imx6sx"))
+return true;
+return false;
+}
+
 static int caam_ctrl_rng_init(struct device *dev)
 {
struct caam_drv_private *ctrlpriv = dev_get_drvdata(dev);
@@ -666,6 +673,8 @@ static int caam_ctrl_rng_init(struct device *dev)
 * Also, if a handle was instantiated, do not change
 * the TRNG parameters.
 */
+   if (needs_entropy_delay_adjustment())
+   ent_delay = 12000;
if (!(ctrlpriv->rng4_sh_init || inst_handles)) {
dev_info(dev,
 "Entropy delay = %u\n",
@@ -682,6 +691,15 @@ static int caam_ctrl_rng_init(struct device *dev)
 */
ret = instantiate_rng(dev, inst_handles,
  gen_sk);
+   /*
+ * Entropy delay is determined via TRNG 
characterization.
+ * TRNG characterization is run across different 
voltages
+ * and temperatures.
+ * If worst case value for ent_dly is identified,
+ * the loop can be skipped for that platform.
+ */
+if (needs_entropy_delay_adjustment())
+break;
if (ret == -EAGAIN)
/*
 * if here, the loop will rerun,
@@ -835,13 +853,6 @@ static bool check_version(struct fsl_mc_version 
*mc_version, u32 major,
 }
 #endif
 
-static bool needs_entropy_delay_adjustment(void)
-{
-   if (of_machine_is_compatible("fsl,imx6sx"))
-   return true;
-   return false;
-}
-
 /* Probe routine for CAAM top (controller) level */
 static int caam_probe(struct platform_device *pdev)
 {
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11427): 
https://lists.yoctoproject.org/g/linux-yocto/message/11427
Mute This Topic: https://lists.yoctoproject.org/mt/92178631/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW27

2022-07-04 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW27 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  13896

gtk-icon-cache.bbclass passes wrong parameter to update_gtk_icon_cache postinst 
intercept

randy.macl...@windriver.com

ross.bur...@arm.com

4.0.1

4.1 M2


 

  14141

devtool modify fails with submodules

randy.macl...@windriver.com

ross.bur...@arm.com

4.0.1

4.1 M2

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 (#57446): https://lists.yoctoproject.org/g/yocto/message/57446
Mute This Topic: https://lists.yoctoproject.org/mt/92173730/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW27!

2022-07-04 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


michael.opdenac...@bootlin.com

3


randy.macl...@windriver.com

3


ross.bur...@arm.com

2


richard.pur...@linuxfoundation.org

2


Grand Total

10

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 (#57445): https://lists.yoctoproject.org/g/yocto/message/57445
Mute This Topic: https://lists.yoctoproject.org/mt/92173715/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 4.1

2022-07-04 Thread Stephen Jolley

All,

Below is the list as of top 37 bug owners as of the end of WW27 of who have
open medium or higher bugs and enhancements against YP 4.1.   There are 81
possible work days left until the final release candidates for YP 4.1 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

36


ross.bur...@arm.com

25


david.re...@windriver.com

23


bruce.ashfi...@gmail.com

21


randy.macl...@windriver.com

16


richard.pur...@linuxfoundation.org

10


saul.w...@windriver.com

10


jpewhac...@gmail.com

9


sakib.sa...@windriver.com

9


tim.orl...@konsulko.com

7


aryaman.gu...@windriver.com

6


jon.ma...@arm.com

4


mhalst...@linuxfoundation.org

4


akuster...@gmail.com

3


sundeep.kokko...@gmail.com

2


hongxu@windriver.com

2


tvgamb...@gmail.com

2


qi.c...@windriver.com

2


pgowda@gmail.com

2


pa...@zhukoff.net

2


alejan...@enedino.org

2


thr...@amazon.de

1


beh...@converseincode.com

1


luca.ceres...@bootlin.com

1


alexandre.bell...@bootlin.com

1


shac...@vdoo.com

1


mostthings...@gmail.com

1


martin.bee...@online.de

1


thomas.per...@bootlin.com

1


raj.k...@gmail.com

1


ola.x.nils...@axis.com

1


martin.ja...@gmail.com

1


ahmed.hos...@opensynergy.com

1


nicolas.deche...@linaro.org

1


piotr.lob...@vm.pl

1


open.sou...@oleksandr-kravchuk.com

1


aeh...@gmail.com

1


Grand Total

213

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 (#57444): https://lists.yoctoproject.org/g/yocto/message/57444
Mute This Topic: https://lists.yoctoproject.org/mt/92173643/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2022-07-04 Thread 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 409
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,  "4.1", "4.2", "4.99" and "Future", the more pressing/urgent
issues being in "4.1" and then "4.2".

 

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 (#57443): https://lists.yoctoproject.org/g/yocto/message/57443
Mute This Topic: https://lists.yoctoproject.org/mt/92173520/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] dunfell do_image_wic error

2022-07-04 Thread Mauro Ziliani


Sorry for missing information


I get this error when I do


bitbake core-image-minimal


MZ

On 04/07/22 21:17, Mauro Ziliani wrote:

Hi all.

I update dunfell to last version.


But now I get a python exception error on do_image_wic task



| Traceback (most recent call last):
|   File "/home/yocto/sources/poky/scripts/lib/wic/filemap.py", line 
457, in get_mapped_ranges

| first_prev, last_prev = next(iterator)
| StopIteration
|
| The above exception was the direct cause of the following exception:
|
| Traceback (most recent call last):
|   File "/home/yocto/sources/poky/scripts/wic", line 542, in 
| sys.exit(main(sys.argv[1:]))
|   File "/home/yocto/sources/poky/scripts/wic", line 537, in main
| return hlp.invoke_subcommand(args, parser, hlp.wic_help_usage, 
subcommands)
|   File "/home/yocto/sources/poky/scripts/lib/wic/help.py", line 83, 
in invoke_subcommand

| subcmd[0](args, usage)
|   File "/home/yocto/sources/poky/scripts/wic", line 219, in 
wic_create_subcommand

| engine.wic_create(wks_file, rootfs_dir, bootimg_dir, kernel_dir,
|   File "/home/yocto/sources/poky/scripts/lib/wic/engine.py", line 
190, in wic_create

| plugin.do_create()
|   File 
"/home/yocto/sources/poky/scripts/lib/wic/plugins/imager/direct.py", 
line 96, in do_create

| self.create()
|   File 
"/home/yocto/sources/poky/scripts/lib/wic/plugins/imager/direct.py", 
line 180, in create

| self._image.prepare(self)
|   File 
"/home/yocto/sources/poky/scripts/lib/wic/plugins/imager/direct.py", 
line 354, in prepare

| part.prepare(imager, imager.workdir, imager.oe_builddir,
|   File "/home/yocto/sources/poky/scripts/lib/wic/partition.py", line 
182, in prepare

| plugin.do_prepare_partition(self, srcparams_dict, creator,
|   File 
"/home/yocto/sources/poky/scripts/lib/wic/plugins/source/rawcopy.py", 
line 68, in do_prepare_partition

| sparse_copy(src, dst)
|   File "/home/yocto/sources/poky/scripts/lib/wic/filemap.py", line 
539, in sparse_copy

| for first, last in fmap.get_mapped_ranges(0, fmap.blocks_cnt):
| RuntimeError: generator raised StopIteration

MZ





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57442): https://lists.yoctoproject.org/g/yocto/message/57442
Mute This Topic: https://lists.yoctoproject.org/mt/92171800/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] dunfell do_image_wic error

2022-07-04 Thread Mauro Ziliani


Hi all.

I update dunfell to last version.


But now I get a python exception error on do_image_wic task



| Traceback (most recent call last):
|   File "/home/yocto/sources/poky/scripts/lib/wic/filemap.py", line 
457, in get_mapped_ranges

| first_prev, last_prev = next(iterator)
| StopIteration
|
| The above exception was the direct cause of the following exception:
|
| Traceback (most recent call last):
|   File "/home/yocto/sources/poky/scripts/wic", line 542, in 
| sys.exit(main(sys.argv[1:]))
|   File "/home/yocto/sources/poky/scripts/wic", line 537, in main
| return hlp.invoke_subcommand(args, parser, hlp.wic_help_usage, 
subcommands)
|   File "/home/yocto/sources/poky/scripts/lib/wic/help.py", line 83, in 
invoke_subcommand

| subcmd[0](args, usage)
|   File "/home/yocto/sources/poky/scripts/wic", line 219, in 
wic_create_subcommand

| engine.wic_create(wks_file, rootfs_dir, bootimg_dir, kernel_dir,
|   File "/home/yocto/sources/poky/scripts/lib/wic/engine.py", line 190, 
in wic_create

| plugin.do_create()
|   File 
"/home/yocto/sources/poky/scripts/lib/wic/plugins/imager/direct.py", 
line 96, in do_create

| self.create()
|   File 
"/home/yocto/sources/poky/scripts/lib/wic/plugins/imager/direct.py", 
line 180, in create

| self._image.prepare(self)
|   File 
"/home/yocto/sources/poky/scripts/lib/wic/plugins/imager/direct.py", 
line 354, in prepare

| part.prepare(imager, imager.workdir, imager.oe_builddir,
|   File "/home/yocto/sources/poky/scripts/lib/wic/partition.py", line 
182, in prepare

| plugin.do_prepare_partition(self, srcparams_dict, creator,
|   File 
"/home/yocto/sources/poky/scripts/lib/wic/plugins/source/rawcopy.py", 
line 68, in do_prepare_partition

| sparse_copy(src, dst)
|   File "/home/yocto/sources/poky/scripts/lib/wic/filemap.py", line 
539, in sparse_copy

| for first, last in fmap.get_mapped_ranges(0, fmap.blocks_cnt):
| RuntimeError: generator raised StopIteration

MZ


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57441): https://lists.yoctoproject.org/g/yocto/message/57441
Mute This Topic: https://lists.yoctoproject.org/mt/92171800/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [PATCH 2/2] image-without-static-linkage: add selftest

2022-07-04 Thread Johannes Schilling via lists.yoctoproject.org

diff --git a/lib/oeqa/selftest/cases/static_linkage_checker.py 
b/lib/oeqa/selftest/cases/static_linkage_checker.py
new file mode 100644
index 000..a5fdf6b
--- /dev/null
+++ b/lib/oeqa/selftest/cases/static_linkage_checker.py
@@ -0,0 +1,39 @@
+import os
+import re
+
+from oeqa.selftest.case import OESelftestTestCase
+from oeqa.utils.commands import bitbake
+
+class StaticLinkageCheck(OESelftestTestCase):
+def test_static_linkage_check(self):
+self.write_recipeinc('emptytest', """
+SUMMARY = "A small image just capable of allowing a device to boot."
+
+IMAGE_INSTALL = "packagegroup-core-boot ${CORE_IMAGE_EXTRA_INSTALL}"
+
+CORE_IMAGE_EXTRA_INSTALL ?= ""
+
+LICENSE = "MIT"
+
+inherit image
+
+IMAGE_ROOTFS_SIZE ?= "8192"
+
+inherit image-without-static-linkage
+
+STATIC_LINKAGE_CHECK_CONFIG = "${WORKDIR}/static-linkage-check-config.toml"
+
+do_write_config() {
+echo "[checkers]\nmodules = [ "zlib", "librsvg" ]\n" > 
"${STATIC_LINKAGE_CHECK_CONFIG}"
+echo "[exceptions]" >> "${STATIC_LINKAGE_CHECK_CONFIG}"
+echo "ignore_dirs = []" >> "${STATIC_LINKAGE_CHECK_CONFIG}"
+echo "ignore_checks = {}" >> "${STATIC_LINKAGE_CHECK_CONFIG}"
+}
+
+addtask do_write_config before do_image_qa
+""")
+
+result = bitbake("-c image_qa emptytest", ignore_status=True)
+if result.status != 0:
+self.logger.warn(result.output)
+raise self.failureException("build failed, something went 
wrong...")
-- 
2.36.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57440): https://lists.yoctoproject.org/g/yocto/message/57440
Mute This Topic: https://lists.yoctoproject.org/mt/92168378/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [PATCH 1/2] image-without-static-linkage: add class

2022-07-04 Thread Johannes Schilling via lists.yoctoproject.org

This class provides a new image QA check that tries to detect static
linkage of a set of well-known libraries, leveraging the detectors from
cve-bin-tool[0].

To use in your project, provide a config file as described in the header
comment of the class, and inherit image-without-static-linkage in your
image recipe.

[0] https://github.com/intel/cve-bin-tool/tree/main/cve_bin_tool/checkers
---
 classes/image-without-static-linkage.bbclass  |  65 +
 .../python/python3-packaging_%.bbappend   |   1 +
 .../cve-bin-tool/cve-bin-tool-native.bb   |  34 +
 .../files/cve-bin-tool-static-linkage-checker | 126 ++
 4 files changed, 226 insertions(+)
 create mode 100644 classes/image-without-static-linkage.bbclass
 create mode 100644 recipes-devtools/python/python3-packaging_%.bbappend
 create mode 100644 recipes-security/cve-bin-tool/cve-bin-tool-native.bb
 create mode 100644 
recipes-security/cve-bin-tool/files/cve-bin-tool-static-linkage-checker

diff --git a/classes/image-without-static-linkage.bbclass 
b/classes/image-without-static-linkage.bbclass
new file mode 100644
index 000..c6f2013
--- /dev/null
+++ b/classes/image-without-static-linkage.bbclass
@@ -0,0 +1,65 @@
+# Provide a QA check for statically linked copies of libraries.
+#
+# You need to provide a config file in TOML format and point the
+# variable `STATIC_LINKAGE_CHECK_CONFIG_FILE` to it.
+#
+# The file format is as follows
+# ```
+# [checkers]
+# modules = [
+#   # list of checker module names of cve-bin-tool checkers lib to
+#   # enable, i.e. file names in the cve_bin_tool/checkers subfolder.
+#   # https://github.com/intel/cve-bin-tool/tree/main/cve_bin_tool/checkers
+#   "librsvg",
+#   "zlib",
+# ]
+#
+# [exceptions]
+# ignore_dirs = [
+#   # list of directories, everything under these is completely ignored
+#   "/var/lib/opkg",
+# ]
+#
+# [exceptions.ignore_checks]
+#   # for each binary path, a list of checkers from the global list to
+#   # ignore for this binary (allowlist)
+#   "/bin/ary/name" = [ "zlib" ],
+# ```
+
+IMAGE_QA_COMMANDS += "image_check_static_linkage"
+
+DEPENDS += "cve-bin-tool-native"
+
+inherit python3native
+
+
+STATIC_LINKAGE_CUSTOM_ERROR_MESSAGE ??= ""
+
+python image_check_static_linkage() {
+import json
+from pathlib import Path
+import subprocess
+
+from oe.utils import ImageQAFailed
+
+check_result = 
subprocess.check_output(["cve-bin-tool-static-linkage-checker",
+"--config", d.getVar("STATIC_LINKAGE_CHECK_CONFIG_FILE"),
+d.getVar("IMAGE_ROOTFS"),
+])
+check_result = json.loads(check_result)
+
+deploy_dir = Path(d.getVar("DEPLOYDIR"))
+deploy_dir.mkdir(parents=True, exist_ok=True)
+image_basename = d.getVar("IMAGE_BASENAME")
+stats_filename = "static_linkage_stats-" + image_basename + ".json"
+with open(deploy_dir / stats_filename, "w") as stats_out:
+json.dump(check_result, stats_out)
+
+binaries_with_violations = {k: v for k, v in check_result.items() if v}
+if binaries_with_violations:
+msg = "Static linkage check: found {} 
violations".format(len(binaries_with_violations))
+for violator, violations in binaries_with_violations.items():
+msg += "\n{}: {}".format(violator, violations)
+
+raise ImageQAFailed(msg, image_check_static_linkage)
+}
diff --git a/recipes-devtools/python/python3-packaging_%.bbappend 
b/recipes-devtools/python/python3-packaging_%.bbappend
new file mode 100644
index 000..d6f5869
--- /dev/null
+++ b/recipes-devtools/python/python3-packaging_%.bbappend
@@ -0,0 +1 @@
+BBCLASSEXTEND += "native"
diff --git a/recipes-security/cve-bin-tool/cve-bin-tool-native.bb 
b/recipes-security/cve-bin-tool/cve-bin-tool-native.bb
new file mode 100644
index 000..3efbdf7
--- /dev/null
+++ b/recipes-security/cve-bin-tool/cve-bin-tool-native.bb
@@ -0,0 +1,34 @@
+SUMMARY = "Scanner for statically linked library copies"
+HOMEPAGE = "https://github.com/intel/cve-bin-tool;
+
+LICENSE = "GPL-3.0"
+LIC_FILES_CHKSUM = "file://LICENSE.md;md5=97a733ff40c50b4bfc74471e1f6ca88b"
+
+VERSION = "3.1"
+
+
+SRC_URI = "\
+https://github.com/intel/cve-bin-tool/archive/refs/tags/v${VERSION}.tar.gz 
\
+file://cve-bin-tool-static-linkage-checker \
+"
+
+SRC_URI[md5sum] = "af6958f8be7f7ce0d2b5ddffa34a1aee"
+SRC_URI[sha256sum] = 
"c4faaa401a2605a0d3f3c947deaf01cb56b4da927bfc29b5e959cde243bf5daf"
+
+inherit python3native native
+
+S = "${WORKDIR}/cve-bin-tool-3.1"
+inherit setuptools3
+
+RDEPENDS_${PN} = "\
+  python3-rich-native \
+  python3-packaging-native \
+"
+
+do_install:append() {
+  install -m 0755 "${WORKDIR}/cve-bin-tool-static-linkage-checker" 
"${D}${bindir}"
+}
+FILES-${PN}:append = "${bindir}/cve-bin-tool-static-linkage-checker"
+
+do_configure[noexec] = "1"
+do_compile[noexec] = "1"
diff --git 
a/recipes-security/cve-bin-tool/files/cve-bin-tool-static-linkage-checker 
b/recipes-security/cve-bin-tool/files/cve-bin-tool-static-linkage-checker
new file mode

Re: [yocto] [PATCH yocto-autobuilder-helper] run-docs-build: allow build warnings again

2022-07-04 Thread Richard Purdie

On Mon, 2022-07-04 at 15:24 +0200, Quentin Schulz wrote:
> Hi Michael,
> 
> On 6/22/22 17:32, Michael Opdenacker via lists.yoctoproject.org wrote:
> > From: Michael Opdenacker 
> > 
> > This allows to switch to a more recent of Sphinx
> > which will generate warnings with old versions of docs.
> > 
> > This way, it's not immediately necessary to patch
> > all such versions.
> > 
> > This commit reverts
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__git.yoctoproject.org_yocto-2Dautobuilder-2Dhelper_commit_-3Fid-3D8273124feb9da2ffe93fcee7c4529d5597e1684a=DwIDAg=_sEr5x9kUWhuk4_nFwjJtA=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t=je4C362aUVxZ2rdozdrQVTgzhi9iRYrxNfYtH5LHkXdlsay9SEphJ_ekBm4830_n=9u5-2R_NLEQy5w0pFgklKIUQnAvVLuHX1ASaeEBBJJ4=
> > which originally reverted
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__git.yoctoproject.org_yocto-2Dautobuilder-2Dhelper_commit_-3Fid-3D931d409b255a85f2217ca093d8391a678ce00ddb=DwIDAg=_sEr5x9kUWhuk4_nFwjJtA=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t=je4C362aUVxZ2rdozdrQVTgzhi9iRYrxNfYtH5LHkXdlsay9SEphJ_ekBm4830_n=bTED2gTptfT6bSvLayy3fEpQJyUdbo5gLlt7ZGKkD1c=
> > 
> > Signed-off-by: Michael Opdenacker 
> > ---
> >   scripts/run-docs-build | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/scripts/run-docs-build b/scripts/run-docs-build
> > index 648a29d..0f74520 100755
> > --- a/scripts/run-docs-build
> > +++ b/scripts/run-docs-build
> > @@ -63,7 +63,7 @@ for branch in 1.46 $(git branch --remote --contains 
> > "$first_sphinx_commit" --for
> >   git checkout $branch
> >   git checkout master releases.rst
> >   make clean
> > -make publish
> > +SPHINXOPTS="-j auto" make publish
> >   
> >   if [ "$branch" = "master-next" ]; then
> >   branch="next"
> > @@ -136,7 +136,7 @@ for branch in dunfell $(git branch --remote --contains 
> > "$first_sphinx_commit" --
> >   fi
> >   
> >   make clean
> > -make publish
> > +SPHINXOPTS="-j auto" make publish
> >   
> 
> What about doing this for all branches except master? To have at least 
> some checks and not completely disable the warnings.
> 
> I'm a bit afraid we'll just not care about warnings anymore since they 
> won't fail the autobuilder anymore. I also understand it's not really 
> sustainable to leave them on for old docs since they won't be maintained 
> at one point in time but we still very mnuch would like to be able to 
> build them.
> 
> Not sure what's the best solution here right now unfortunately :/

Enabling them for master could be a compromise, I'd take such a patch
(Michael is away for a while).

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57438): https://lists.yoctoproject.org/g/yocto/message/57438
Mute This Topic: https://lists.yoctoproject.org/mt/91924295/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [PATCH yocto-autobuilder-helper] run-docs-build: allow build warnings again

2022-07-04 Thread Quentin Schulz


Hi Michael,

On 6/22/22 17:32, Michael Opdenacker via lists.yoctoproject.org wrote:

From: Michael Opdenacker 

This allows to switch to a more recent of Sphinx
which will generate warnings with old versions of docs.

This way, it's not immediately necessary to patch
all such versions.

This commit reverts
https://urldefense.proofpoint.com/v2/url?u=https-3A__git.yoctoproject.org_yocto-2Dautobuilder-2Dhelper_commit_-3Fid-3D8273124feb9da2ffe93fcee7c4529d5597e1684a=DwIDAg=_sEr5x9kUWhuk4_nFwjJtA=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t=je4C362aUVxZ2rdozdrQVTgzhi9iRYrxNfYtH5LHkXdlsay9SEphJ_ekBm4830_n=9u5-2R_NLEQy5w0pFgklKIUQnAvVLuHX1ASaeEBBJJ4=
which originally reverted
https://urldefense.proofpoint.com/v2/url?u=https-3A__git.yoctoproject.org_yocto-2Dautobuilder-2Dhelper_commit_-3Fid-3D931d409b255a85f2217ca093d8391a678ce00ddb=DwIDAg=_sEr5x9kUWhuk4_nFwjJtA=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t=je4C362aUVxZ2rdozdrQVTgzhi9iRYrxNfYtH5LHkXdlsay9SEphJ_ekBm4830_n=bTED2gTptfT6bSvLayy3fEpQJyUdbo5gLlt7ZGKkD1c=

Signed-off-by: Michael Opdenacker 
---
  scripts/run-docs-build | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 648a29d..0f74520 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -63,7 +63,7 @@ for branch in 1.46 $(git branch --remote --contains 
"$first_sphinx_commit" --for
  git checkout $branch
  git checkout master releases.rst
  make clean
-make publish
+SPHINXOPTS="-j auto" make publish
  
  if [ "$branch" = "master-next" ]; then

  branch="next"
@@ -136,7 +136,7 @@ for branch in dunfell $(git branch --remote --contains 
"$first_sphinx_commit" --
  fi
  
  make clean

-make publish
+SPHINXOPTS="-j auto" make publish
  


What about doing this for all branches except master? To have at least 
some checks and not completely disable the warnings.


I'm a bit afraid we'll just not care about warnings anymore since they 
won't fail the autobuilder anymore. I also understand it's not really 
sustainable to leave them on for old docs since they won't be maintained 
at one point in time but we still very mnuch would like to be able to 
build them.


Not sure what's the best solution here right now unfortunately :/

Cheers,
Quentin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57437): https://lists.yoctoproject.org/g/yocto/message/57437
Mute This Topic: https://lists.yoctoproject.org/mt/91924295/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [yocto-kernel-cache][yocto-5.15][PATCH 2/2] xilinx-zynqmp: disable CONFIG_ARM_CCI_PMU for preempt-rt

2022-07-04 Thread quanyang.wang

From: Quanyang Wang 

CONFIG_ARM_CCI_PMU depends on PERF_EVENTS which is not enabled for
preempt-rt, so the building warning as below can be caught:

   [NOTE]: 'CONFIG_ARM_CCI_PMU' last val (y) and .config val (n) do not match
[INFO]: CONFIG_ARM_CCI_PMU : n
[INFO]: raw config text:

config ARM_CCI_PMU
tristate "ARM CCI PMU driver"
select ARM_CCI
depends on ((ARM && CPU_V7) || ARM64) && PERF_EVENTS
help
  Support for PMU events monitoring on the ARM CCI (Cache 
Coherent
  Interconnect) family of products.

  If compiled as a module, it will be called arm-cci.

Config 'ARM_CCI_PMU' has the following Direct dependencies 
(ARM_CCI_PMU=n):
(ARM(undefined/n) && CPU_V7(undefined/n)) || ARM64(=y) (=y) && 
PERF_EVENTS(=n)
Parent dependencies are:
 PERF_EVENTS [n] CPU_V7 [CPU_V7] ARM64 [y] ARM [ARM]
[INFO]: config 'CONFIG_ARM_CCI_PMU' was set, but it wasn't assignable, 
check (parent) dependencies

Disable CONFIG_ARM_CCI_PMU to fix this.

Signed-off-by: Quanyang Wang 
Signed-off-by: Bruce Ashfield 
---
Hi Bruce,
Would you please help merge this patch to the branch:
yocto-5.15

It's picked up from yocto-5.10.

Thanks,
Quanyang
---
 bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.cfg | 3 +++
 bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc | 2 ++
 2 files changed, 5 insertions(+)
 create mode 100644 bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.cfg

diff --git a/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.cfg 
b/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.cfg
new file mode 100644
index 00..af791ac987
--- /dev/null
+++ b/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.cfg
@@ -0,0 +1,3 @@
+# SPDX-License-Identifier: MIT
+
+# CONFIG_ARM_CCI_PMU is not set
diff --git a/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc 
b/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc
index b6b42972ff..6efecd9740 100644
--- a/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc
+++ b/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc
@@ -7,3 +7,5 @@ include ktypes/preempt-rt
 branch xilinx-zynqmp
 
 include xilinx-zynqmp.scc
+
+kconf hardware xilinx-zynqmp-preempt-rt.cfg
-- 
2.36.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11425): 
https://lists.yoctoproject.org/g/linux-yocto/message/11425
Mute This Topic: https://lists.yoctoproject.org/mt/92161221/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [yocto-kernel-cache][yocto-5.15][PATCH 1/2] xilinx-zynqmp: add preempt-rt support

2022-07-04 Thread quanyang.wang

From: Quanyang Wang 

Add xilinx-zynqmp-preempt-rt.scc to enable preempt-rt for xilinx-zynqmp.

Signed-off-by: Quanyang Wang 
Signed-off-by: Bruce Ashfield 
---
Hi Bruce,
Would you please help merge this patch to the branch:
yocto-5.15

It's picked up from yocto-5.10.

Thanks,
Quanyang
---
 bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc | 9 +
 1 file changed, 9 insertions(+)
 create mode 100644 bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc

diff --git a/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc 
b/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc
new file mode 100644
index 00..b6b42972ff
--- /dev/null
+++ b/bsp/xilinx-zynqmp/xilinx-zynqmp-preempt-rt.scc
@@ -0,0 +1,9 @@
+# SPDX-License-Identifier: MIT
+define KMACHINE xilinx-zynqmp
+define KTYPE preempt-rt
+define KARCH arm64
+
+include ktypes/preempt-rt
+branch xilinx-zynqmp
+
+include xilinx-zynqmp.scc
-- 
2.36.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11426): 
https://lists.yoctoproject.org/g/linux-yocto/message/11426
Mute This Topic: https://lists.yoctoproject.org/mt/92161222/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.2.rc1)

[linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc][PATCH 1/1] crypto: caam: fix a build error 'needs_entropy_delay_adjustment' undefined

[yocto] M+ & H bugs with Milestone Movements WW27

[yocto] Enhancements/Bugs closed WW27!

[yocto] Current high bug count owners for Yocto Project 4.1

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

Re: [yocto] dunfell do_image_wic error

[yocto] dunfell do_image_wic error

[yocto] [PATCH 2/2] image-without-static-linkage: add selftest

[yocto] [PATCH 1/2] image-without-static-linkage: add class

Re: [yocto] [PATCH yocto-autobuilder-helper] run-docs-build: allow build warnings again

Re: [yocto] [PATCH yocto-autobuilder-helper] run-docs-build: allow build warnings again

[linux-yocto] [yocto-kernel-cache][yocto-5.15][PATCH 2/2] xilinx-zynqmp: disable CONFIG_ARM_CCI_PMU for preempt-rt

[linux-yocto] [yocto-kernel-cache][yocto-5.15][PATCH 1/2] xilinx-zynqmp: add preempt-rt support

14 matches

Site Navigation

Mail list logo

Footer information