[yocto] [meta-zephyr][master][langdale][PATCH] zephyr-kernel/3.1: update to latest commit

Recent commits have CVE-2022-2741 fixed. Also backported CVE-2022-2993 fix. Signed-off-by: Naveen Saini --- ...ix-SMP-local-keys-check-when-startin.patch | 51 +++ .../zephyr-kernel/zephyr-kernel-src-3.1.0.inc | 3 +- 2 files changed, 53 insertions(+), 1 deletion(-) create

Re: [yocto] Issue with accessing network from a recipe

Hi, Thanks! That helped my team find out a solution or at least a work-around: setting do_configure[network] and do_compile[network] to "1" in local.conf. I would have another related questions, though: Should the commands requiring network access work if they are invoked from do_fetch? I

[yocto] [layerindex-web] [PATCH] layerindex/utils.py: Add to baseconfig=True for bb.parse.handle()

Bitbake's api has been changed via: afb8478d3 parse: Add support for addpylib conf file directive and BB_GLOBAL_PYMODULES The conf file won't be parsed without baseconfig=True: bb.parse.ParseError: ParseError at /path/to/oe-core/meta/conf/layer.conf:132: unparsed line: 'addpylib ${LAYERDIR}/lib

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

All, YP M+ or high bugs which moved to a new milestone in WW51 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 14467 curl timeout while dnf is downloading package

[yocto] Enhancements/Bugs closed WW50!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count tim.orl...@konsulko.com 1 Grand Total 1 Thanks, Stephen K. Jolley Yocto Project Program Manager *Cell:(208) 244-4460 * Email: sjolley.yp...@gmail.com

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

All, Below is the list as of top 31 bug owners as of the end of WW51 of who have open medium or higher bugs and enhancements against YP 4.2. There are 89 possible work days left until the final release candidates for YP 4.2 needs to be released. Who Count michael.opdenac...@bootlin.com 35

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

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: [yocto] Issue with accessing network from a recipe

Hi, that is intentional, recipes should fetch sources with bitbake fetcher (which respects MIRROR/PREMIRROR/DL_DIR etc) in do_fetch and network shouldn't be used in other tasks (unless explicitly enabled in well explained exceptions). bitbake can now restrict network access in various tasks

[linux-yocto][v5.10/standard/base][PATCH 13/13] Documentation: arm64: Document PMU counters access from userspace

From: Raphael Gault commit aa1005d15d2aee10e5b93a25db076c47e05c4efa upstream Add documentation to describe the access to the pmu hardware counters from userspace. Signed-off-by: Raphael Gault Signed-off-by: Rob Herring Link: https://lore.kernel.org/r/20211208201124.310740-6-r...@kernel.org

[linux-yocto][v5.10/standard/base][PATCH 12/13] arm64: perf: Enable PMU counter userspace access for perf event

From: Rob Herring commit 83a7a4d643d33a8b74a42229346b7ed7139fcef9 upstream Arm PMUs can support direct userspace access of counters which allows for low overhead (i.e. no syscall) self-monitoring of tasks. The same feature exists on x86 called 'rdpmc'. Unlike x86, userspace access will only be

[linux-yocto][v5.10/standard/base][PATCH 11/13] arm64: perf: Add userspace counter access disable switch

From: Rob Herring commit e2012600810c9ded81f6f63a8d04781be3c300ad upstream Like x86, some users may want to disable userspace PMU counter altogether. Add a sysctl 'perf_user_access' file to control userspace counter access. The default is '0' which is disabled. Writing '1' enables access. Note

[linux-yocto][v5.10/standard/base][PATCH 10/13] perf: Add a counter for number of user access events in context

From: Rob Herring commit 82ff0c022d19c2ad69a472692bb7ee01ac07a40b upstream On arm64, user space counter access will be controlled differently compared to x86. On x86, access in the strictest mode is enabled for all tasks in an MM when any event is mmap'ed. For arm64, access is explicitly

[linux-yocto][v5.10/standard/base][PATCH 09/13] x86: perf: Move RDPMC event flag to a common definition

From: Rob Herring commit 369461ce8fb6c8156206c7110d7da48e9fbc41bb upstream In preparation to enable user counter access on arm64 and to move some of the user access handling to perf core, create a common event flag for user counter access and convert x86 to use it. Since the architecture

[linux-yocto][v5.10/standard/base][PATCH 08/13] libperf xyarray: Add bounds checks to xyarray__entry()

From: Rob Herring commit 818869489ba3c4a4ed1360e22b2f66be488ea9f5 upstream xyarray__entry() is missing any bounds checking yet often the x and y parameters come from external callers. Add bounds checks and an unchecked __xyarray__entry(). Committer notes: Make the 'x' and 'y' arguments to the

[linux-yocto][v5.10/standard/base][PATCH 07/13] libperf: Add support for user space counter access

From: Rob Herring commit 47d01e7bb9591077a59a1ecec11c6ce570de upstream x86 and arm64 can both support direct access of event counters in userspace. The access sequence is less than trivial and currently exists in perf test code (tools/perf/arch/x86/tests/rdpmc.c) with copies in projects

[linux-yocto][v5.10/standard/base][PATCH 04/13] tools include: Add an initial math64.h

From: Rob Herring commit 2fc83c2cd77703cfcfc1ffaa092614fb1f837292 upstream Add an initial math64.h similar to linux/math64.h with functions mul_u64_u64_div64() and mul_u64_u32_shr(). This isn't a direct copy of include/linux/math64.h as that doesn't define mul_u64_u64_div64(). Implementation

[linux-yocto][v5.10/standard/base][PATCH 03/13] perf record: Improve 'Workload failed' message printing events + what was exec'ed

From: Arnaldo Carvalho de Melo commit 3535a6967c0d590381c16d6676c6fdfa60f4d733 upstream Before: # perf record -a cycles,instructions,cache-misses Workload failed: No such file or directory # After: # perf record -a cycles,instructions,cache-misses Failed to collect 'cycles' for the

[linux-yocto][v5.10/standard/base][PATCH 06/13] libperf tests: Add support for verbose printing

From: Rob Herring commit d3003d9e686890a1e9f0cc7c08aa02ef2953b1f0 upstream Add __T_VERBOSE() so tests can add verbose output. The verbose output is enabled with the '-v' command line option. Running 'make tests V=1' will enable the '-v' option when running the tests. It'll be used in the next

[linux-yocto][v5.10/standard/base][PATCH 05/13] libperf: Add evsel mmap support

From: Rob Herring commit 6cd70754f262e593febc06a02d7ea637c927ea42 upstream In order to support usersapce access, an event must be mmapped. While there's already mmap support for evlist, the usecase is a bit different than the self monitoring with userspace access. So let's add new

[linux-yocto][v5.10/standard/base][PATCH 01/13] perf annotate: Fix sample events lost in stdio mode

From: Yang Jihong commit 5676dba708bbb1fc94a9d3b2e9c114db9e4c6699 upstream In hist__find_annotations(), since different 'struct hist_entry' entries may point to same symbol, we free notes->src to signal already processed this symbol in stdio mode; when annotate, entry will skipped if notes->src

[linux-yocto][v5.10/standard/base][linux-yocto][v5.10/standard/base][PATCH 02/13] perf evlist: Add a method to return the list of evsels as a string

From: Arnaldo Carvalho de Melo commit 9865ea8ab31f2e56be59125099ee251ce573f293 upstream Add a 'scnprintf' method to obtain the list of evsels in a evlist as a string, excluding the "dummy" event used for things like receiving metadata events (PERF_RECORD_FORK, MMAP, etc) when synthesizing

[linux-yocto][v5.10/standard/base] enable PMU counter userspace access for perf event

Hi Bruce, Please help to merge this patchset into linux-yocto repo. repo: linux-yocto branch: v5.10/standard/base Thanks, Adrian -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12028):

[yocto] Issue with accessing network from a recipe

Hi, I am having an issue with a recipe whose do_configure requires network connections and I wonder if this issue could be related to Yocto so that this list would be the correct place to ask for ideas. The problem appears when trying to build dotnet-hello-world which comes with meta-dotnet