I can confirm that this patch fixes the problem reported here:
https://lists.openembedded.org/g/openembedded-core/message/193907
We tried it on three sets of 8 builds, and all of them passed successfully:
https://tuxapi.tuxsuite.com/v1/groups/tuxsuite/projects/vishal/plans/2bBF73bS9lx2GFzroGyjf8Nm
On Fri, Jan 19, 2024 at 2:00 PM Alexandre Belloni
wrote:
>
>
> On 19/01/2024 19:24:44+, Richard Purdie wrote:
> > On Fri, 2024-01-19 at 18:48 +0100, Thomas Perrot wrote:
> > > Hello Richard,
> > >
> > > On Fri, 2024-01-19 at 17:22 +, Richard Purdie wrote:
> > > > On Wed, 2024-01-17 at 10:4
On 19/01/2024 19:24:44+, Richard Purdie wrote:
> On Fri, 2024-01-19 at 18:48 +0100, Thomas Perrot wrote:
> > Hello Richard,
> >
> > On Fri, 2024-01-19 at 17:22 +, Richard Purdie wrote:
> > > On Wed, 2024-01-17 at 10:47 +0100, Thomas Perrot via
> > > lists.openembedded.org wrote:
> > > > F
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 15Jan24
Date: Mon, 15 Jan 2024 12:48:45 -0500
]
Signed-off-by: Bruce Ashfield
---
.
From: Bruce Ashfield
Updating linux-yocto/6.1 to the latest korg -stable release that comprises
the following commits:
fec3b1451d5f Linux 6.1.73
f9ee31dc7fcd cifs: fix flushing folio regression for 6.1 backport
0f22c8a6efe6 ipv6: remove max_size check inline with ipv4
b2c545c3987
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 15Jan24
Date: Mon, 15 Jan 2024 12:48:45 -0500
]
Signed-off-by: Bruce Ashfield
---
.
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
47345b4264bc Linux 6.6.12
edbc56139579 nfsd: drop the nfsd_put helper
Signed-off-by: Bruce Ashfield
---
.../linux/linux-yocto-rt_6.6.bb | 6 ++--
.../l
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
1/1 [
Author: Xiangyu Chen
Email: xiangyu.c...@windriver.com
Subject: feature/security: add configs to harden protection
Date: Tue, 16 Jan 2024 18:22:31 +0800
Add some configs to harden protection:
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
1/1 [
Author: Xiangyu Chen
Email: xiangyu.c...@windriver.com
Subject: feature/security: add configs to harden protection
Date: Tue, 16 Jan 2024 18:22:31 +0800
Add some configs to harden protection:
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
22852eaf43ec Linux 6.6.11
e53b78e3cfb1 media: qcom: camss: Comment CSID dt_id field
c897fb3da8a7 cxl/memdev: Hold region_rwsem during inject and clear poison
ops
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
1/1 [
Author: Ross Burton
Email: ross.bur...@arm.com
Subject: arch/arm: add fragments to explicitly select 4/16/64 KB pages on
arm64
Date: Tue, 9 Jan 2024 13:33:06 +
Linux on aarch64 supports var
From: Bruce Ashfield
Updating linux-yocto/6.1 to the latest korg -stable release that comprises
the following commits:
7c58bfa711cb Linux 6.1.72
2dbe25ae06e6 Revert "interconnect: qcom: sm8250: Enable sync_state"
f73a374c1969 smb3: Replace smb2pdu 1-element arrays with flex-arrays
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 27Dec23
Date: Wed, 27 Dec 2023 19:47:13 -0500
]
Signed-off-by: Bruce Ashfield
---
m
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 27Dec23
Date: Wed, 27 Dec 2023 19:47:13 -0500
]
Signed-off-by: Bruce Ashfield
---
m
From: Bruce Ashfield
Richard,
Here's the colllected -stable updates for 6.6 and 6.1. This will probably be
the last round of 6.1 updates for master, since I'll drop it shortly in
preparation for the release. 6.1 will of course continue to be updated in
linux-yocto and in older releases.
I've al
On Fri, 2024-01-19 at 18:48 +0100, Thomas Perrot wrote:
> Hello Richard,
>
> On Fri, 2024-01-19 at 17:22 +, Richard Purdie wrote:
> > On Wed, 2024-01-17 at 10:47 +0100, Thomas Perrot via
> > lists.openembedded.org wrote:
> > > From: Thomas Perrot
> > >
> > > This release has:
> > > - Synopsy
On 19/01/2024 19:13:25+0100, Alexandre Belloni wrote:
> On 19/01/2024 11:09:20+0800, Chen Qi via lists.openembedded.org wrote:
> > What's the status of this patch series?
> > Is there any issue or concern that I missed?
>
> I'm glad you asked, I got this today:
>
> https://autobuilder.yoctoprojec
On 19/01/2024 11:09:20+0800, Chen Qi via lists.openembedded.org wrote:
> What's the status of this patch series?
> Is there any issue or concern that I missed?
I'm glad you asked, I got this today:
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8466/steps/26/logs/warnings
>
>
Following your suggestions and iteratively adding packages based on error
message, I am finally able to come up with quite a long list of perl-module-*
packages that fix the dependencies of openssl-ptest.
However, I am worried about if the list I came up with is truly comprehensive
in the sense
Hello Richard,
On Fri, 2024-01-19 at 17:22 +, Richard Purdie wrote:
> On Wed, 2024-01-17 at 10:47 +0100, Thomas Perrot via
> lists.openembedded.org wrote:
> > From: Thomas Perrot
> >
> > This release has:
> > - Synopsys DesignWare APB GPIO driver
> > - Zicntr and Zihpm support
> > - Console
> On 19 Jan 2024, at 11:33, Yu, Mingli via lists.openembedded.org
> wrote:
>file://0004-autogen.sh-fix-find-version-for-beta-checking.patch \
>file://0001-Woverride-init-is-not-needed-with-gcc-9.patch \
>file://fix-ldap.patch \
> + file://0001-autog
On Wed, 2024-01-17 at 10:47 +0100, Thomas Perrot via
lists.openembedded.org wrote:
> From: Thomas Perrot
>
> This release has:
> - Synopsys DesignWare APB GPIO driver
> - Zicntr and Zihpm support
> - Console print improvements
> - Smepmp support
> - Simple FDT based syscon regmap driver
> - Sysco
On Tue, 2023-12-26 at 12:44 +0800, Chen Qi via lists.openembedded.org
wrote:
> From: Chen Qi
>
> The initial_revs["."] does not have an initial value, resulting
> in the following error:
>
> KeyError: '.'
>
> The problem could be reproduced by running:
>
> devtool modify -n systemd
>
> S
From: Yash Shinde
Tests which are failing from below modules are added to exclude list
tests/run-make
tests/rustdoc
tests/mir-opt
tests/ui-fulldeps
* Redundent test cases whose parent dir is also present in exclud list are
removed.
* Newly addded tests are sort
From: Yash Shinde
Fixes: thread 'main' panicked at 'assertion failed: `(left == right)`
left: `x86_64-unknown-linux-gnu`,
right: `x86_64-poky-linux-gnu`: Cannot obtain compiler for non-native build
triple at stage 0', compile.rs:1474:13
Add correct target value for cross-compiled targets on sta
From: Yash Shinde
Fixes: error: the option `Z` is only accepted on the nightly compiler
When rust.channel is set to either beta or stable, we can't use
nightly features on bootstrap without RUSTC_BOOTSTRAP.
Set RUSTC_BOOTSTRAP=1 to use nightly features on stable or beta.
Signed-off-by: Yash Shi
From: Yash Shinde
Fixes: thread 'main' panicked at 'failed to gather the target spec
for '-unknown-linux-gnu', synthetic_targets.rs:66:9
Detect and fetch custom target configurations when rustc is
bootstrapped in rust oe-selftest.
Signed-off-by: Yash Shinde
---
.../rust/files/custom-ta
From: Yash Shinde
Fixes: Exception: no cargo executable found at
`${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo`
Fix the cargo binary path error on oe-selftest and path set to rust-snapshot
dir.
Patch sent to upstream- https://github.com/rust-lang/rust/pull/12012
Please ignore this series as it contains wrong commit shortlog
format(https://lists.openembedded.org/g/openembedded-core/message/194050).
I will a send v2.
Regards,
Yash.
On 19-01-2024 19:13, yash.shi...@windriver.com wrote:
From: Yash Shinde
Tests which are failing from below modules are ad
On Thu, Jan 18, 2024 at 11:22 PM Andrej Valek wrote:
>
> Hello Raj,
>
> I will try to take a look on this today. Is the patch the same as here
> https://git.yoctoproject.org/poky-contrib/commit/?h=yoe/mut&id=c0594edef0d2108860421d0cfd460993264e18c3
> ? Means, if I can take it from there.
yes. Kee
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch /home/patchtest/share/mboxes/5-5-Rust-oe-selftest-enabled..patch
FAIL: test shortlog format: Commit shortlog (first line of commit message)
shou
From: Yash Shinde
Tests which are failing from below modules are added to exclude list
tests/run-make
tests/rustdoc
tests/mir-opt
tests/ui-fulldeps
* Redundent test cases whose parent dir is also present in exclud list are
removed.
* Newly addded tests are sort
From: Yash Shinde
Fixes: thread 'main' panicked at 'assertion failed: `(left == right)`
left: `x86_64-unknown-linux-gnu`,
right: `x86_64-poky-linux-gnu`: Cannot obtain compiler for non-native build
triple at stage 0', compile.rs:1474:13
Add correct target value for cross-compiled targets on sta
From: Yash Shinde
Fixes: error: the option `Z` is only accepted on the nightly compiler
When rust.channel is set to either beta or stable, we can't use
nightly features on bootstrap without RUSTC_BOOTSTRAP.
Set RUSTC_BOOTSTRAP=1 to use nightly features on stable or beta.
Signed-off-by: Yash Shi
From: Yash Shinde
Fixes: thread 'main' panicked at 'failed to gather the target spec
for '-unknown-linux-gnu', synthetic_targets.rs:66:9
Detect and fetch custom target configurations when rustc is
bootstrapped in rust oe-selftest.
Signed-off-by: Yash Shinde
---
.../rust/files/custom-ta
In qemu's configuration this is an 'auto' configuration option so if the host
has
the sndio headers on then it gets enabled, causing sstate reuse problems. This
is
particularly problematic as some qemu pieces can 'see' into the host pkg-config
due to openGL linkage.
Add config and disable by def
From: Yash Shinde
Fixes: Exception: no cargo executable found at
`${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo`
Fix the cargo binary path error on oe-selftest and path set to rust-snapshot
dir.
Patch sent to upstream- https://github.com/rust-lang/rust/pull/12012
On 19-01-2024 01:38, Randy MacLeod wrote:
On 2024-01-18 5:57 a.m., yash.shi...@windriver.com wrote:
From: Yash Shinde
Enable rust oe-selftest for rust 1.74.1 version and
add target_cfg.patch to handle target configurations
for custom targets.
Hi Yashe,
Yay, getting the rust test suite worki
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/shadow-replace-static-linking-with-dynamic-libraries-in-a-custom-location-and-bundled-with-shadow.patch
FAIL: test
Despite our efforts to make static linking work, there have
been new reports of bizarre build failures:
https://lists.openembedded.org/g/openembedded-core/message/194006
https://lists.openembedded.org/g/openembedded-core/message/193907
This commit changes back to dynamic linking, but places
the li
I've seen issues where static libraries built on one host were not
usable on a different host with default compiler options. This may be
another one of these.
We're reverting to dynamic linking with libraries in a custom
directory in sysroot that would be bundled together with shadow-native
proper
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/kirkstone-xserver-xorg-Multiple-CVE-fixes.patch
FAIL: test CVE check ignore: CVE_CHECK_IGNORE is deprecated and sho
Issue:
the usage of a gpt table with i.MX processor is not compatible by default.
This is due to a memory conflict: the main partition table is placed into
the same memory space used to flash the header of the U-Boot. This last
can not be moved since the ROM code of the i.MX6 starts to read to that
I didn't do anything particular, but as several people are sharing the server,
it's possible that its environment is somewhat messed up. I'll check more and
fix the environment. Thanks for your double check.
Regards,
Qi
-Original Message-
From: Alexander Kanavin
Sent: Friday, January
From: Vijay Anusuri
Fix below CVE's
CVE-2023-6816
CVE-2024-0229
CVE-2024-21885
CVE-2024-21886
CVE-2024-0408
CVE-2024-0409
Signed-off-by: Vijay Anusuri
---
.../xserver-xorg/CVE-2023-6816.patch | 55 +
.../xserver-xorg/CVE-2024-0229-1.patch| 87 +++
.../xserver-xorg/CV
Do you need to override the PREFERRED_VERSION_? instead of overriding
LLVMVERSION?
Aren't you trying to fix what was fixed in proposed change a while ago:
https://patchwork.yoctoproject.org/project/oe-core/patch/20230401163241.354257-1-martin.ja...@gmail.com/
On Fri, Jan 19, 2024 at 8:35 AM Chan
Le ven. 19 janv. 2024 à 12:40, davide.cardillo via lists.openembedded.org
a écrit :
> Issue:
> the usage of a gpt table with i.MX processor is not compatible by default.
> This is due to a memory conflict: the main partition table is placed into
> the same memory space used to flash the header of
On Fri, 2024-01-19 at 19:33 +0800, Yu, Mingli wrote:
> From: Mingli Yu
>
> The commit [b67e4e523 Improve the beta number generation.] [1]
> extends the version to make it work well for no release version,
> but it introduces the version inconsistency.
>
> Considering we mainly use a release vers
Issue:
the usage of a gpt table with i.MX processor is not compatible by default.
This is due to a memory conflict: the main partition table is placed into
the same memory space used to flash the header of the U-Boot. This last
can not be moved since the ROM code of the i.MX6 starts to read to that
From: Mingli Yu
The change [1] extends a -unknown suffix to version and introduces
the version inconsistency.
Before the patch:
# rpm -qa | grep libgcrypt
libgcrypt-1.10.3-r0.core2_64
libgcrypt-ptest-1.10.3-r0.core2_64
# rpm -ql libgcrypt
/usr
/usr/bin
/usr/bin/mpicalc
/u
From: Mingli Yu
The commit [b67e4e523 Improve the beta number generation.] [1]
extends the version to make it work well for no release version,
but it introduces the version inconsistency.
Considering we mainly use a release version in oe, so remove the
added suffix to keep consistent.
Before t
From: Mingli Yu
The latest release for xmlto is 0.0.28 [1], but the PV is set
individually [2] in terms of backport several patches to fix
builds with newer compilers after 0.0.28 was releases in 2015.
[1] https://releases.pagure.org/xmlto/
[2]
https://git.openembedded.org/openembedded-core/com
On Fri, 19 Jan 2024 at 11:24, Richard Purdie
wrote:
> There is another report about issues from the shadow static linking
> change.
>
> I'm worried that there are now accesses to files with are out of sight
> of pseudo so that some combinations of builds are breaking. I'd
> forgotten about pseudo
On Fri, 2024-01-19 at 11:12 +0100, Alexander Kanavin wrote:
> I just tried poky master on ubuntu 20.04, and the issues do not
> appear. Do you have a custom setup?
There is another report about issues from the shadow static linking
change.
I'm worried that there are now accesses to files with are
This causes oe-selftest failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/6326/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/6317/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/6328/steps/14/lo
I just tried poky master on ubuntu 20.04, and the issues do not
appear. Do you have a custom setup?
Alex
On Fri, 19 Jan 2024 at 04:06, ChenQi wrote:
>
> I'm seeing build failures on Ubuntu 20.04.
> GCC version: 9.4.0
>
> 1. error: parameter name omitted
> The problem is that the active_sessions_
I believe this series is the cause of some repro failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4254/steps/12/logs/stdio
On 18/01/2024 11:24:09+0100, Alexander Kanavin wrote:
> Upstream has replaced autoconf with cmake, which necessitates a rewrite of the
> recipe an
I got this failure:
https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/8493/steps/23/logs/stdio
On 18/01/2024 11:24:07+0100, Alexander Kanavin wrote:
> Per
> https://github.com/rpm-software-management/rpm/commit/77d3529c31ca090a40b8d3959a0bcdd721a556d6
> rpm 4.19.1+ will not consi
Hi Steve,
I will send v2.
../Yogita
On 19-01-2024 03:56, Steve Sakoman wrote:
**
*CAUTION: This email comes from a non Wind River email account!*
Do not click links or open attachments unless you recognize the sender
and know the content is safe.
On Thu, Jan 18, 2024 at 12:21 PM Randy MacL
On Fri, 2024-01-19 at 15:35 +0800, Changqing Li wrote:
> From: Changqing Li
>
> use ?= to set following configs in order to allow user
> to override the default settings:
> PREFERRED_VERSION_llvm
> PREFERRED_VERSION_llvm-native
> PREFERRED_VERSION_nativesdk-llvm
>
> Signed-off-by: Changqing Li
Hello,
Le 19/01/2024 à 09:38, davide.cardillo via lists.openembedded.org a écrit :
> Issue:
> the usage of a gpt table with i.MX processor is not compatible by default.
> This is due to a memory conflict: the main partition table is placed into
> the same memory space used to flash the header of
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/WIC-Configurable-addressing-of-GTP-main-table.patch
FAIL: test mbox format: Series has malformed diff lines. Create
Issue:
the usage of a gpt table with i.MX processor is not compatible by default.
This is due to a memory conflict: the main partition table is placed into
the same memory space used to flash the header of the U-Boot. This last
can not be moved since the ROM code of the i.MX6 starts to read to that
63 matches
Mail list logo
