From: pgowda
The patch implements Rust testing framework similar to other selftest,
specifically the gcc selftest in OE. It uses the client and server
based method to test the binaries for cross-target on the image.
The test framework is a wrapper around the Rust build system as ./x.py
test. It
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5c831a3c7f3ca98d6aba1200353311e1a1f84c70]
Signed-off-by: pgowda
---
.../binutils/binutils-2.39.inc| 1 +
.../binutils/0015-CVE-2022-4285.patch | 37
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=175b91507b83ad42607d2f6dadaf55b7b511bdbe]
Upstream-Status
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=19c26da69d68d5d863f37c06ad73ab6292d02ffa]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=ec41dd75c866599fc03c390c6afb5736c159c0ff]
Upstream-Status
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=175b91507b83ad42607d2f6dadaf55b7b511bdbe]
Upstream-Status
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e3e5ae049371a27fd1737aba946fe26d06e029b5]
Signed-off-by: pgowda
---
.../binutils/binutils-2.38.inc| 1 +
.../binutils/0016-CVE-2022-38126.patch| 34
find the patch posted with all the above modifications as :-
https://lists.openembedded.org/g/openembedded-core/message/170420
Thanks,
Pgowda
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170421):
https://lists.openembedded.org/g/openembedded-co
From: pgowda
The patch implements Rust testing framework similar to other selftest,
specifically the gcc selftest in OE. It uses the client and server
based method to test the binaries for cross-target on the image.
The test framework is a wrapper around the Rust build system as ./x.py
test. It
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ef186fe54aa6d281a3ff8a9528417e5cc614c797]
Signed-off-by: pgowda
---
.../binutils/binutils-2.38.inc| 1 +
.../binutils/0015-CVE-2022-38533.patch| 36
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ef186fe54aa6d281a3ff8a9528417e5cc614c797]
Signed-off-by: pgowda
---
.../binutils/binutils-2.39.inc| 1 +
.../binutils/0013-CVE-2022-38533.patch| 36
Hi Richard,
Thanks very much for reviewing the patch and your comments regarding it.
>> thread 'main' panicked at 'RUSTDOC_LIBDIR was not set',
>> src/bootstrap/bin/rustdoc.rs:15:48
>> note: run with `RUST_BACKTRACE=1` environment variable to display a
>> backtrace
>> error: could not document `c
From: pgowda
The patch implements Rust testing framework similar to other selftest,
specifically the gcc selftest in OE. It uses the client and server
based method to test the binaries for cross-target on the image.
The test framework is a wrapper around the Rust build system as ./x.py
test. It
From: pgowda
Fixes the following error while building the rust-testuite
error: linker cc not found
Signed-off-by: pgowda
---
meta/recipes-devtools/rust/rust.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-devtools/rust/rust.inc
b/meta/recipes-devtools/rust/rust.inc
From: pgowda
Emits complete details regarding the test results to understand
and debug from logfiles
Signed-off-by: pgowda
---
meta/recipes-devtools/rust/rust.inc | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-devtools/rust/rust.inc
b/meta/recipes-devtools/rust/rust.inc
From: pgowda
Adds the cross compilation linker for build, host and target.
Ensure the main rust config has the appropriate sections added
to match the configurations.
Signed-off-by: pgowda
---
meta/recipes-devtools/rust/rust.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta
From: pgowda
Implemented Rust Oe-Selftest on the latest Rust sources with
modifications. Rust testsuite will be merged with Rust to avoid
duplication. rust-testsuite.inc modifications will be merged into
rust.inc file. There were errors encountered during the rust-testsuite
build which are fixed
Hi Luca,
Thanks for informing me about the error.
The patch has been updated to fix the libstdc++ environment issue as
reported by you.
https://lists.openembedded.org/g/openembedded-core/message/168974
Thanks,
Pgowda
On Fri, Aug 5, 2022 at 12:42 PM Luca Ceresoli wrote:
>
> Hello Pgowda,
From: pgowda
The patch implements Rust testing framework similar to other selftest,
specifically the gcc selftest in OE. It uses the client and server
based method to test the binaries for cross-target on the image.
The test framework is a wrapper around the Rust build system as ./x.py
test. It
in the host machine as a prerequisite for rust-1.62??
Thanks,
Pgowda
On Fri, Aug 5, 2022 at 12:42 PM Luca Ceresoli wrote:
>
> Hello Pgowda,
>
> On Wed, 3 Aug 2022 19:57:34 +0530
> "Pgowda" wrote:
>
> > From: pgowda
> >
> > The patch implements Ru
Hi Luca,
Updated the maintainers list and submitted the patch as:-
https://lists.openembedded.org/g/openembedded-core/message/168819
Thanks,
Pgowda
On Wed, Aug 3, 2022 at 7:13 PM Luca Ceresoli wrote:
>
> Hi Pgowda,
>
> On Wed, 3 Aug 2022 15:40:15 +0200
> &qu
From: pgowda
The patch implements Rust testing framework similar to other selftest,
specifically the gcc selftest in OE. It uses the client and server
based method to test the binaries for cross-target on the image.
The test framework is a wrapper around the Rust build system as ./x.py
test.
It
Hi Luca,
Thanks very much for checking the patch and comment about the elf-tls.
An explanatory comment has been added as per your suggestion and patch
posted as:-
https://lists.openembedded.org/g/openembedded-core/message/168778
Thanks,
Pgowda
On Tue, Aug 2, 2022 at 3:22 PM Luca Ceresoli
From: pgowda
The patch implements Rust testing framework similar to other selftest,
specifically the gcc selftest in OE. It uses the client and server
based method to test the binaries for cross-target on the image.
The test framework is a wrapper around the Rust build system as ./x.py
test.
It
Hi Luca,
There were around 270 testcase failing when "has-elf-tls" has been
enabled while building llvm.
Hence, we had to remove the option to enable the proper working of these tests.
The patch has been tested on Ubuntu and also fedora (using docker image).
Thanks,
Pgowda
On Tue, A
From: pgowda
The patch implements Rust testing framework similar to other selftest,
specifically the gcc selftest in OE. It uses the client and server
based method to test the binaries for cross-target on the image.
The test framework is a wrapper around the Rust build system as ./x.py
test.
It
Hi,
I had referred the following link in buildroot :-
https://lore.kernel.org/buildroot/20220720213853.1a27184...@busybox.osuosl.org/t/
Sending the patches would be very helpful.
Thanks,
Pgowda
On Mon, Jul 25, 2022 at 4:03 PM Martin Jansa wrote:
>
> Hi,
>
> it was reverted in
Hi Martin,
Thanks for the confirmation from your side.
I had the same issue and reverting the commit on master branch fixed the issue.
Please let me know whether the patch should be reverted in the master branch to
avoid building issues when "DEBUG_BUILD" is enabled.
Thanks & Reg
From: Naveen
Backport a fix from:
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=9234cdca6ee88badfc00297e72f13dac4e540c79
which fixes rust recursion issues in the demangler.
Signed-off-by: Naveen
---
meta/recipes-devtools/gcc/gcc-11.3.inc| 2 +-
.../gcc/gcc/0030-rust-recursion-limit.
From: pgowda
Upstream-Status: Backport
[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=9234cdca6ee88badfc00297e72f13dac4e540c79]
Signed-off-by: pgowda
---
meta/recipes-devtools/gcc/gcc-12.1.inc| 1 +
.../gcc/gcc/0026-rust-recursion-limit.patch | 92 +++
2 files
From: Pgowda
Below commits are on Binutils-2.38 and Glibc-2.35 development branches are
updated.
glibc:
b6aade18a7 nss: handle stat failure in check_reload_and_get (BZ #28752)
ccac2d6d95 nss: add assert to DB_LOOKUP_FCT (BZ #28752)
9d8ae95604 nios2: Remove _dl_skip_args usage (BZ# 29187
20245c35f2 Automatic date update in version.in
39c6088537b Automatic date update in version.in
6a8f2255438 Automatic date update in version.in
Signed-off-by: Pgowda
---
meta/recipes-core/glibc/glibc-version.inc| 2 +-
meta/recipes-devtools/binutils/binutils-2.38.inc | 2 +-
2 files changed, 2
Upstream-Status: Backport
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2a4fc266dbf77ed7ab83da16468e9ba627b8bc2d]
Signed-off-by: Pgowda
---
.../binutils/binutils-2.38.inc| 1 +
.../binutils/0014-CVE-2019-1010204.patch | 49 +++
2 files
recipes as well.
It would help us in fixing the issue appropriately.
Thanks,
Pgowda
On Mon, Jun 6, 2022 at 2:21 PM Richard Purdie
wrote:
>
> On Fri, 2022-06-03 at 18:37 +0530, pgowda cve wrote:
> > Hi Luca,
> >
> > Regarding the issue
> > https://bugzilla.yoctopro
Upstream-Status: Backport
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2a4fc266dbf77ed7ab83da16468e9ba627b8bc2d]
Signed-off-by: Pgowda
---
.../binutils/binutils-2.38.inc| 1 +
.../binutils/0014-CVE-2019-1010204.patch | 49 +++
2 files
- INFO - oe-selftest - OK - All
required tests passed (successes=15, skipped=1, failures=0, errors=0)
I also ran the Rust Oe-Selftest individually and did not find any issues.
Can you please share the environment file so that I can reproduce and
fix the issue?
Thanks,
Pgowda
On Tue, May 31, 2022 at
disables tests. When updating to a newer version of Rust,
the patch can usually be ported in a day.
Signed-off-by: pgowda
Signed-off-by: Vinay Kumar
---
meta/conf/distro/include/maintainers.inc | 1 +
meta/lib/oeqa/selftest/cases/rust.py | 57 +++
meta/recipes-devtools/rust/rust
Gentle Ping on the following patch
On Fri, May 13, 2022 at 5:50 PM pgowda wrote:
>
> The patch implements Rust testing framework similar to other selftest,
> specifically the gcc selftest in OE. It uses the client and server
> based method to test the binaries for cross-target
let me know if I have to export any specific
environment to replicate the failure?
Thanks,
Pgowda
On Fri, May 13, 2022 at 6:15 PM wrote:
>
> On Fri, 2022-05-13 at 17:58 +0530, Pgowda wrote:
> > Hi Luca,
> >
> > I have checked it again at my end and it seems to be working fin
Hi Luca,
I have checked it again at my end and it seems to be working fine.
The error is related to "setup NFS mount on target" and does not seem
to be related to the patch.
Can the patch be included again while running oe-selftest and checked?
Thanks,
Pgowda
On Thu, May 5, 2022
disables tests. When updating to a newer version of Rust,
the patch can usually be ported in a day.
Signed-off-by: pgowda
Signed-off-by: Vinay Kumar
---
meta/lib/oeqa/selftest/cases/rust.py | 57 +++
meta/recipes-devtools/rust/rust-common.inc| 1 -
meta/recipes-devtools/rust/rust
)
I did a run of the following command in latest Poky sources after
applying the patch:-
oe-selftest -a -t machine -t toolchain-system
pgowda@ala-lpggp3:/pgowda/check$ uname -a
Linux 5.4.0-107-generic #121~18.04.1-Ubuntu
While running lib32-glibc-tests, it fails with the following error
as the recipe is not PROVIDED. BBCLASSEXTEND is cleaned in glibc-tests
and is not able to recognize the multilibs.
ERROR: Nothing PROVIDES 'lib32-glibc-tests'
Signed-off-by: pgowda
---
meta/recipes-core/glibc/glibc-
out after seeing the warning message from Luca Ceresoli.
It's was updated, tested for all the recipes and a new version of the
patch is posted as:-
https://lists.openembedded.org/g/openembedded-core/message/164872
Thanks,
Pgowda
On Tue, Apr 26, 2022 at 5:36 PM Alex Kiernan wrote:
>
> On Tue
Rust has been upgraded to rust-1.60.0 that uses LLVM 14.
Please refer the following link for more detailed features.
https://blog.rust-lang.org/2022/04/07/Rust-1.60.0.html
https://github.com/rust-lang/rust/blob/master/RELEASES.md
Signed-off-by: pgowda
---
meta/conf/distro/include/tcmode
Rust has been upgraded to rust-1.60.0 that uses LLVM 14.
Please refer the following link for more detailed features.
https://blog.rust-lang.org/2022/04/07/Rust-1.60.0.html
https://github.com/rust-lang/rust/blob/master/RELEASES.md
Signed-off-by: pgowda
---
...59.0.bb => cargo-cr
latest
version of glibc-2.33?
Thanks,
Pgowda
On Wed, Apr 20, 2022 at 9:11 PM Randy MacLeod
wrote:
>
> On 2022-04-20 11:30, pgowda cve wrote:
> > Hi Randy,
> >
> > The GLIBC was already updated to the latest version on top of [BZ #28353].
> >
> > Please find th
Hi Randy,
The GLIBC was already updated to the latest version on top of [BZ #28353].
Please find the commit which had [BZ #28353] patch along with others.
https://git.openembedded.org/openembedded-core/commit/?h=hardknott&id=d5bdff460cc8b0f38177f1f38d625eeda729b459
Thanks,
Pgowda
On Wed,
Run glibc-tests only when its enabled in the DISTRO_FEATURES.
Signed-off-by: pgowda
---
meta/recipes-core/glibc/glibc-tests_2.35.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc-tests_2.35.bb
b/meta/recipes-core/glibc/glibc-tests_2.35.bb
it's been implemented.
Thanks & Regards
Pgowda
On Fri, Apr 15, 2022 at 6:32 PM Richard Purdie
wrote:
>
> On Fri, 2022-04-15 at 04:11 -0700, pgowda wrote:
> > The current default DISTRO_FEATURES does not support ptest.
> > Hence, the following error is generated during
th "DISTRO = Yocto" as DISTRO_FEATURES
in Yocto supports ptest. However, when we run "glibc-tests" using
Open-embedded master sources; it generates the error as default
DISTRO is used.
Signed-off-by: pgowda
---
meta/recipes-core/glibc/glibc-tests_2.35.bb | 2 ++
1 file changed,
th "DISTRO = Yocto" as DISTRO_FEATURES
in Yocto supports ptest. However, when we run "glibc-tests" using
Open-embedded master sources; it generates the error as default
DISTRO is used.
Signed-off-by: pgowda
---
meta/conf/distro/include/default-distrovars.inc | 2 +-
1 file chang
#14725]
Signed-off-by: pgowda
---
.../binutils/binutils-2.38.inc| 1 +
.../0013-Avoid-as-info-race-condition.patch | 75 +++
2 files changed, 76 insertions(+)
create mode 100644
meta/recipes-devtools/binutils/binutils/0013-Avoid-as-info-race-condition.patch
es tests. When updating to a newer version of Rust, the patch can
usually be rebased in under a day.
Signed-off-by: pgowda
Signed-off-by: Vinay Kumar
---
meta/lib/oeqa/selftest/cases/rust.py | 57 +
meta/recipes-devtools/rust/rust-testsuite.inc | 163 +++
.../rust-testsuite/rust-oe-sel
" }',
src/bootstrap/bin/rustc.rs:175:37
=======
Signed-off-by: pgowda
Signed-off-by: Vinay Kumar
---
meta/lib/oeqa/selftest/cases/rust.py | 57 +
meta/recipes-devtools/rust/rust-testsuite.inc | 163 +++
.../rust-testsuite/rust-oe-selftest.patch | 995
at
> could
> solve the LooseVersion problem too!
Thanks for pointing this out. It has been removed as not needed.
> s/Yocto/OE/
Done.
> PARALLEL_MAKE isn't used above so I doubt this is needed now? (I realise the
Removed as it's not required.
Thanks,
pgowda
-=-=-=-=-=-
h has been run and tested for X86 and X86_64 targets on
Ubuntu-18 successfully.
Signed-off-by: pgowda
Signed-off-by: Vinay Kumar
---
meta/lib/oeqa/selftest/cases/rust.py | 53 ++
meta/recipes-devtools/rust/rust-testsuite.inc | 160
.../rust-testsuite/rust-oe-selftest.patch
-804e1d2731595192.so"
thread 'main' panicked at 'io::copy(&mut file, dst) failed with
Connection reset by peer (os error 104)',
src/tools/remote-test-client/src/main.rs:353:5
The patch will be posted for master branch after fixing the issue.
Signed-off-by: pgowda
Signe
Gentle Ping on this patch.
On Sun, Jan 30, 2022 at 11:50 AM pgowda wrote:
>
> glibc-2.33 has been upgraded to latest version that includes many CVE and
> other bug fixes. Ran the regressions and results are better.
>
> Signed-off-by: pgowda
> ---
> meta/recipes-core/glibc/
Upstream-Status: Backport
[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f10bec5ffa487ad3033ed5f38cfd0fc7d696deab]
Signed-off-by: pgowda
---
meta/recipes-devtools/gcc/gcc-11.2.inc| 1 +
.../gcc/gcc/0001-CVE-2021-46195.patch | 128 ++
2 files changed, 129
XPASS
Latest glibc-2.33
Summary of test results:
164 FAIL
3801 PASS
20 UNSUPPORTED
16 XFAIL
2 XPASS
Thanks,
Pgowda
On Tue, Jan 25, 2022 at 8:14 PM Mittal, Anuj wrote:
>
> Can you please rebase all the glibc CVE patches for hardknott on top
> of:
glibc-2.33 has been upgraded to latest version that includes many CVE and
other bug fixes. Ran the regressions and results are better.
Signed-off-by: pgowda
---
meta/recipes-core/glibc/glibc-version.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc
/?p=glibc.git;a=commit;h=1b9cd6a7214db1812a20eb3591cf42f9190a5d1a]
Signed-off-by: pgowda
---
.../glibc/glibc/0001-CVE-2021-3999.patch | 35 ++
.../glibc/glibc/0002-CVE-2021-3999.patch | 356 ++
.../glibc/glibc/0003-CVE-2021-3999.patch | 28 ++
meta/recipes-core
/?p=glibc.git;a=commit;h=84d2d0fe20bdf94feed82b21b4d7d136db471f03]
Signed-off-by: pgowda
---
.../glibc/glibc/0001-CVE-2021-3998.patch | 282 ++
.../glibc/glibc/0002-CVE-2021-3998.patch | 138 +
.../glibc/glibc/0003-CVE-2021-3998.patch | 35 +++
meta/recipes
Upstream-Status: Backport
[https://sourceware.org/git/?p=glibc.git;a=commit;h=8c8a71c85f2ed5cc90d08d82ce645513fc907cb6]
Upstream-Status: Backport
[https://sourceware.org/git/?p=glibc.git;a=commit;h=472e799a5f2102bc0c3206dbd5a801765fceb39c]
Signed-off-by: pgowda
---
.../glibc/glibc/0001-CVE
Upstream-Status: Backport
[https://sourceware.org/git/?p=glibc.git;a=commit;h=062ff490c1467059f6cd64bb9c3d85f6cc6cf97a]
Upstream-Status: Backport
[https://sourceware.org/git/?p=glibc.git;a=commit;h=f7a79879c0b2bef0dadd6caaaeeb0d26423e04e5]
Signed-off-by: pgowda
---
.../glibc/glibc/0001-CVE
gcc-10.2 in Hardknott branch has been upgraded to gcc-10.3 version
that includes many bug fixes.
Regression tested on X86-64, Arm and Aarch64 without issues.
Signed-off-by: pgowda
---
.../gcc/{gcc-10.2.inc => gcc-10.3.inc}| 12 +-
...ian_10.2.bb => gcc-cross-canadian_10.3.bb}
binutils-2.36 in Hardknott branch has been upgraded to latest version
that includes many bug fixes.
Regression tested on X86-64, Arm and Aarch64 without any new issues.
Signed-off-by: pgowda
---
.../binutils/binutils-2.36.inc| 5 +-
.../binutils/0001-CVE-2021-20197.patch
glibc-2.33 has been upgraded to latest version that includes many CVE and
other bug fixes.
Signed-off-by: pgowda
---
meta/recipes-core/glibc/glibc-version.inc | 2 +-
.../glibc/glibc/0031-CVE-2021-43396.patch | 182 --
meta/recipes-core/glibc/glibc_2.33.bb
Upstream-Status: Backport
[https://sourceware.org/git/?p=glibc.git;a=commit;h=226b46770c82899b555986583294b049c6ec9b40]
Upstream-Status: Backport
[https://sourceware.org/git/?p=glibc.git;a=commit;h=ef972a4c50014a16132b5c75571cfb6b30bef136]
Signed-off-by: pgowda
---
.../glibc/glibc/0001-CVE
Upstream-Status: Backport
[https://sourceware.org/git/?p=glibc.git;a=commit;h=e368b12f6c16b6888dda99ba641e999b9c9643c8]
Upstream-Status: Backport
[https://sourceware.org/git/?p=glibc.git;a=commit;h=f545ad4928fa1f27a3075265182b38a4f939a5f7]
Signed-off-by: pgowda
---
.../glibc/glibc/0001-CVE
This patch backports the Arm support for Neoverse N2 CPU.
Upstream-Status: Backport
[https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=d7e8411f6a333d4054894ad3b23f23415a525230]
Signed-off-by: pgowda
---
meta/recipes-devtools/gcc/gcc-10.2.inc | 1 +
...verse-n2
Backport the fix for CVE-2021-43396. It is disputed that this is a
security issue.
(From OE-Core rev: e8de9b01c6b305b2498c5f942397a49ae2af0cde)
Signed-off-by: pgowda
---
.../glibc/glibc/0031-CVE-2021-43396.patch | 182 ++
meta/recipes-core/glibc/glibc_2.33.bb | 1
Hi Anuj,
Thanks very much for the information.
Regards,
Pgowda
On Thu, Jan 6, 2022 at 7:57 PM Mittal, Anuj wrote:
>
> On Thu, 2022-01-06 at 16:11 +0530, pgowda cve wrote:
> > Hi,
> >
> > Gentle ping on this patch.
> >
>
> I will take this and rest of gcc
Hi,
Gentle ping on this patch.
The patch modifies the testcases in UTF-8 format to execute as expected.
Thanks,
Pgowda
On Sat, Dec 25, 2021 at 8:02 PM pgowda wrote:
>
> Modify the testcases properly to generate expected output.
>
> Upstream-Status: Backport
> [https://
Hi,
Gentle ping on this patch.
Thanks,
Pgowda
On Tue, Dec 21, 2021 at 4:11 PM pgowda wrote:
>
> The patch backports the AArch64 support for Arm's Neoverse N2 CPU
> Upstream-Status: Backport
> [https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9428e9267435a62f672e2ba
Hi,
Gentle ping on this patch.
Thanks,
Pgowda
On Fri, Dec 24, 2021 at 11:16 AM Khem Raj wrote:
>
> lgtm
>
> On Mon, Dec 20, 2021 at 10:00 PM Pgowda wrote:
> >
> > This patch backports the AArch32 support for Arm's Neoverse N2 CPU.
> >
> > Upstream-Stat
Hi,
Gentle ping on this patch.
Thanks,
Pgowda
On Thu, Dec 2, 2021 at 1:08 PM pgowda wrote:
>
> Backport the fix for CVE-2021-43396. It is disputed that this is a
> security issue.
>
> (From OE-Core rev: e8de9b01c6b305b2498c5f942397a49ae2af0cde)
>
> Signed-off-by: pgowd
dded-core/message/160175
Thanks,
Pgowda
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#160177):
https://lists.openembedded.org/g/openembedded-core/message/160177
Mute This Topic: https://lists.openembedded.org/mt/88011740/21656
Group Owner: openembe
]
Signed-off-by: pgowda
---
.../gcc/gcc/0002-CVE-2021-42574.patch | 536 --
.../gcc/gcc/0004-CVE-2021-42574.patch | 20 +-
2 files changed, 258 insertions(+), 298 deletions(-)
diff --git a/meta/recipes-devtools/gcc/gcc/0002-CVE-2021-42574.patch
b/meta/recipes-devtools
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b3aa80b45c4f46029efeb204bb9f2d2c4278a0e5]
Signed-off-by: pgowda
---
.../binutils/binutils-2.36.inc|1 +
.../binutils/0001-CVE-2021-42574.patch| 2006 +
2 files
commitdiff;h=795588aec4f894206863c938bd6d716895886009
Updated the patch and tested on mingw and ran regression for
"qemux86-64" without any regressions.
https://lists.openembedded.org/g/openembedded-core/message/159941
Thanks,
Pgowda
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b3aa80b45c4f46029efeb204bb9f2d2c4278a0e5]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=795588aec4f894206863c938bd6d716895886009]
Signed-off-by: pgowda
The patch backports the AArch64 support for Arm's Neoverse N2 CPU
Upstream-Status: Backport
[https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9428e9267435a62f672e2ba42df46432c021a9cf]
Signed-off-by: pgowda
---
meta/recipes-devtools/gcc/gcc-10.2.inc| 1 +
.../gcc/0039-arm64-neo
This patch backports the AArch32 support for Arm's Neoverse N2 CPU.
Upstream-Status: Backport
[https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=d7e8411f6a333d4054894ad3b23f23415a525230]
Signed-off-by: pgowda
---
meta/recipes-devtools/gcc/gcc-10.2.inc| 1 +
.../0038-aarch64-neo
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b3aa80b45c4f46029efeb204bb9f2d2c4278a0e5]
Signed-off-by: pgowda
---
.../binutils/binutils-2.37.inc|1 +
.../binutils/0001-CVE-2021-42574.patch| 1998 +
2 files
RO definitions that are present in the CVE patches.
We can just implement those macros and drop the complete patch which
is quite large.
Please let me know if we keep the patches as is or just implement the
macros to make patch smaller?
Thanks,
pgowda
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all me
ng libstd-rs in "release" mode as that works
around the issue and builds mozjs successfully. This is a
work-around that can be used until the root cause of the debug
build error is resolved.
Signed-off-by: pgowda
---
meta/recipes-devtools/rust/libstd-rs.inc | 3 +++
1 file changed, 3 in
Backport the fix for CVE-2021-43396. It is disputed that this is a
security issue.
(From OE-Core rev: e8de9b01c6b305b2498c5f942397a49ae2af0cde)
Signed-off-by: pgowda
---
.../glibc/glibc/0031-CVE-2021-43396.patch | 188 ++
meta/recipes-core/glibc/glibc_2.33.bb | 1
Hi,
Gentle ping on this patch.
Thanks,
pgowda
On Mon, Nov 15, 2021 at 5:44 PM Pgowda wrote:
>
> source : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102035
>
> Upstream-Status:
> Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=3929bca9ca95de9d35e82ae8828b188029e3e
Hi,
Gentle ping on this patch.
Thanks,
pgowda
On Mon, Nov 15, 2021 at 7:33 PM Pgowda wrote:
>
> rust-cross-* imported from meta-rust has incorrect signatures,
> depending on MACHINEOVERRIDES making it effectively MACHINE_ARCH
> as shown by sstate-diff-machines.sh:
>
> openemb
Hi Anuj,
I'm sorry regarding the patch subject.
The patch is for the master branch. However, the same issue exists for
other branches as well.
I will check the comments from others and will post the patch to the
Hardknott branch once it's approved in the master branch.
Thanks,
Pgow
Signed-off-by: Pgowda
---
meta/recipes-devtools/rust/rust-cross.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/rust/rust-cross.inc
b/meta/recipes-devtools/rust/rust-cross.inc
index bb625f4240..a77f7d5122 100644
--- a/meta/recipes-devtools/rust/rust
Source:- https://bugzilla.yoctoproject.org/show_bug.cgi?id=14613
Adds TUNE_PKGARCH to PN so that it picks correct TUNE_FEATURES.
Signed-off-by: Pgowda
---
meta/recipes-devtools/rust/rust-cross.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/rust
]
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=30461cf8dba3d3adb15a125e4da48800eb2b9b8f]
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=809330ab8450261e05919b472783bf15e4b000f7]
Signed-off-by: Pgowda
---
meta/recipes-devtools/gcc/gcc-10.2.inc
]
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=30461cf8dba3d3adb15a125e4da48800eb2b9b8f]
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=809330ab8450261e05919b472783bf15e4b000f7]
Signed-off-by: Pgowda
---
meta/recipes-devtools/gcc/gcc-11.2.inc
tsuite run
due to some test case failures from rust source.
Can you please let me know how to deal with this?
Is there a way we can provide these failures as expected or ignore them?
Thanks,
Pgowda
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply On
>> Did you mean CVE-2021-3530 here and in the patches below as well?
Should I have it in the commit message or in the patches?
Thanks,
Naveen
On Thu, Oct 28, 2021 at 3:32 PM Mittal, Anuj wrote:
>
> On Thu, 2021-10-28 at 02:58 -0700, Pgowda wrote:
> > CVE: CVE-2015-3530
&g
Please find the modified patch posted at following link:-
https://lists.openembedded.org/g/openembedded-core/message/157582
Thanks,
Pgowda
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157583):
https://lists.openembedded.org/g/openembedded-core/me
CVE: CVE-2015-3530
Upstream-Status:
Backport[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=25162c795b1a2becf936bb3581d86a307ea491eb]
Upstream-Status:
Backport[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=999566402e3]
Signed-off-by: Pgowda
---
.../binutils/binutils
Backport from binutils-2_37
Signed-off-by: Pgowda
---
.../binutils/binutils-2.36.inc| 1 +
.../binutils/0017-CVE-2021-3530.patch | 97 +++
2 files changed, 98 insertions(+)
create mode 100644
meta/recipes-devtools/binutils/binutils/0017-CVE-2021-3530
1 - 100 of 125 matches
Mail list logo
