Skip to contentSkip to conversation

Pull request (cover letter only)

PATCH In review Steve Sakoman 2 participants 5 messages Oct 27, 2020 – Oct 30, 2020 3 messages not in the archive

lore
Share & tools
lore
#0 lore raw

cover Pull request (cover letter only)

The following changes since commit 3ee9590f96cb50e93864db768b254773e2ff9465:

uninative: Fix typo in error message (2020-10-19 04:27:15 -1000)

are available in the Git repository at:

git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next

Alexander Kanavin (1):
selftest/virgl: drop the custom 30 sec timeout

Changqing Li (1):
toolchain-shar-extract.sh: don't print useless info

Khem Raj (1):
packagegroup-core-tools-debug: Disable for rv32/glibc as well

Lee Chee Yang (3):
libproxy: fix CVE-2020-25219
python3: fix CVE-2020-26116
grub2: fix CVE-2020-10713

Martin Jansa (7):
arch-armv7a.inc: fix typo
arch-mips.inc: remove duplicated mips64el-o32 from
PACKAGE_EXTRA_ARCHS_tune-mips64el-o32
tune-mips64r6.inc: fix typo in mipsisa64r6-nf tune-ep9312.inc: add t suffix for thumb to

    PACKAGE_EXTRA_ARCHS_tune-ep9312

tune-riscv.inc: use nf suffix also for TUNE_PKGARCH
siteinfo: Recognize 32bit PPC LE
siteinfo: Recognize bigendian sh3be and sh4be

Victor Kamensky (1):
qemu: change TLBs number to 64 in 34Kf mips cpu model

 meta-selftest/lib/oeqa/runtime/cases/virgl.py |   2 +-
 meta/classes/siteinfo.bbclass                 |   5 +
 meta/conf/machine/include/arm/arch-armv7a.inc |   2 +-
 meta/conf/machine/include/mips/arch-mips.inc  |   2 +-
 .../conf/machine/include/riscv/tune-riscv.inc |   4 +-
 meta/conf/machine/include/tune-ep9312.inc     |   3 +-
 meta/conf/machine/include/tune-mips64r6.inc   |   2 +-
 meta/files/toolchain-shar-extract.sh          |   2 +-
 .../grub/files/CVE-2020-10713.patch           |  73 ++++++++++++
 meta/recipes-bsp/grub/grub2.inc               |   1 +
 .../packagegroup-core-tools-debug.bb          |   2 +-
 .../python/python3/CVE-2020-26116.patch       | 104 ++++++++++++++++++
 meta/recipes-devtools/python/python3_3.8.2.bb |   1 +
 meta/recipes-devtools/qemu/qemu.inc           |   1 +
 ...ease-number-of-TLB-entries-on-the-34.patch |  59 ++++++++++
 .../libproxy/libproxy/CVE-2020-25219.patch    |  61 ++++++++++
 .../libproxy/libproxy_0.4.15.bb               |   1 +
 17 files changed, 315 insertions(+), 10 deletions(-)
 create mode 100644 meta/recipes-bsp/grub/files/CVE-2020-10713.patch
 create mode 100644 meta/recipes-devtools/python/python3/CVE-2020-26116.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/0001-target-mips-Increase-number-of-TLB-entries-on-the-34.patch
 create mode 100644 meta/recipes-support/libproxy/libproxy/CVE-2020-25219.patch
Signature · 1 line
2.17.1
#1 lore raw
Quoted 29 lines · Steve Sakoman

The following changes since commit 3ee9590f96cb50e93864db768b254773e2ff9465:

uninative: Fix typo in error message (2020-10-19 04:27:15 -1000)

are available in the Git repository at:

git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next

Alexander Kanavin (1):
selftest/virgl: drop the custom 30 sec timeout

Changqing Li (1):
toolchain-shar-extract.sh: don't print useless info

Khem Raj (1):
packagegroup-core-tools-debug: Disable for rv32/glibc as well

Lee Chee Yang (3):
libproxy: fix CVE-2020-25219
python3: fix CVE-2020-26116
grub2: fix CVE-2020-10713

Martin Jansa (7):
arch-armv7a.inc: fix typo
arch-mips.inc: remove duplicated mips64el-o32 from
PACKAGE_EXTRA_ARCHS_tune-mips64el-o32
tune-mips64r6.inc: fix typo in mipsisa64r6-nf tune-ep9312.inc: add t suffix for thumb to

Quoted 4 lines
    PACKAGE_EXTRA_ARCHS_tune-ep9312

tune-riscv.inc: use nf suffix also for TUNE_PKGARCH
siteinfo: Recognize 32bit PPC LE
siteinfo: Recognize bigendian sh3be and sh4be

Did you run tune/test.sh script with these on dunfell or do you want me to?

It looks OK, but would be good to confirm that it fixes all issues currently in dunfell.

Quoted 33 lines

Victor Kamensky (1):
qemu: change TLBs number to 64 in 34Kf mips cpu model

 meta-selftest/lib/oeqa/runtime/cases/virgl.py |   2 +-
 meta/classes/siteinfo.bbclass                 |   5 +
 meta/conf/machine/include/arm/arch-armv7a.inc |   2 +-
 meta/conf/machine/include/mips/arch-mips.inc  |   2 +-
 .../conf/machine/include/riscv/tune-riscv.inc |   4 +-
 meta/conf/machine/include/tune-ep9312.inc     |   3 +-
 meta/conf/machine/include/tune-mips64r6.inc   |   2 +-
 meta/files/toolchain-shar-extract.sh          |   2 +-
 .../grub/files/CVE-2020-10713.patch           |  73 ++++++++++++
 meta/recipes-bsp/grub/grub2.inc               |   1 +
 .../packagegroup-core-tools-debug.bb          |   2 +-
 .../python/python3/CVE-2020-26116.patch       | 104 ++++++++++++++++++
 meta/recipes-devtools/python/python3_3.8.2.bb |   1 +
 meta/recipes-devtools/qemu/qemu.inc           |   1 +
 ...ease-number-of-TLB-entries-on-the-34.patch |  59 ++++++++++
 .../libproxy/libproxy/CVE-2020-25219.patch    |  61 ++++++++++
 .../libproxy/libproxy_0.4.15.bb               |   1 +
 17 files changed, 315 insertions(+), 10 deletions(-)
 create mode 100644 meta/recipes-bsp/grub/files/CVE-2020-10713.patch
 create mode 100644 meta/recipes-devtools/python/python3/CVE-2020-26116.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/0001-target-mips-Increase-number-of-TLB-entries-on-the-34.patch
 create mode 100644 meta/recipes-support/libproxy/libproxy/CVE-2020-25219.patch
Signature · 1 line
2.17.1
#4 lore raw
In reply to a message not in the archive

The script just finished, I've uploaded the results here:
https://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

There is a lot of changes compared to master, but mostly because I didn't have ARM_INSTRUCTION_SET set to thumb in this run.

That helped to reveal one issue in meta/conf/machine/include/tune-arm9tdmi.inc
which most likely exists in master as well (wasn't detected before just because ARM_INSTRUCTION_SET).
https://git.openembedded.org/openembedded-core-contrib/diff/scripts/tune/log.fake-arm9tdmi.arm9tdmi?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

And the meta/conf/machine/include/tune-supersparc.inc is failing like it did in master before removal in:
https://git.openembedded.org/openembedded-core/commit/?id=861519337b6e5e986c3c4b8ba253e8339caf0805
which you probably intentionally didn't backport to dunfell.
https://git.openembedded.org/openembedded-core-contrib/diff/scripts/tune/log.fake-supersparc?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

I'll trigger it once more with thumb enabled to better show what's the difference from master.

Cheers,

Quoted 33 lines · Martin Jansa

Hi Steve,

it's from this branch:

https://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/tune-test

I've already started it on top of dunfell with these fixes backported, will report back when it's finished (will take at least rest of today to finish).

Cheers,

Quoted 18 lines · Steve Sakoman

Hi Martin,

Quoted 1 line · Martin Jansa

Did you run tune/test.sh script with these on dunfell or do you want me

to?

No, I didn't. I'm not familiar with that script. Can you point me in the right direction?

Quoted 2 lines

It looks OK, but would be good to confirm that it fixes all issues currently in dunfell.

Agreed!

Steve

#6 lore raw
In reply to a message not in the archive
Quoted 12 lines · Martin Jansa via lists.openembedded.org

The script just finished, I've uploaded the results here:
https://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

There is a lot of changes compared to master, but mostly because I didn't have ARM_INSTRUCTION_SET set to thumb in this run.

That helped to reveal one issue in meta/conf/machine/include/tune-arm9tdmi.inc
which most likely exists in master as well (wasn't detected before just because ARM_INSTRUCTION_SET).
https://git.openembedded.org/openembedded-core-contrib/diff/scripts/tune/log.fake-arm9tdmi.arm9tdmi?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

Quoted 8 lines

And the meta/conf/machine/include/tune-supersparc.inc is failing like it did in master before removal in:
https://git.openembedded.org/openembedded-core/commit/?id=861519337b6e5e986c3c4b8ba253e8339caf0805
which you probably intentionally didn't backport to dunfell.
https://git.openembedded.org/openembedded-core-contrib/diff/scripts/tune/log.fake-supersparc?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

I'll trigger it once more with thumb enabled to better show what's the difference from master.

test with thumb enabled finished and looks OK
https://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/tune-test-dunfell&id=c8a0a19b8585661c39e1ba7e16d061d0ae2afc74

There is a lot of changes compared to results from master, but those are expected.

The arm9tdmi issue I mentioned before is reproducible in master as well, I've sent fix for master:
https://lists.openembedded.org/g/openembedded-core/message/144002
it could be backported later.

Cheers,

Quoted 42 lines

Cheers,

Quoted 33 lines · Martin Jansa

Hi Steve,

it's from this branch:

https://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/tune-test

I've already started it on top of dunfell with these fixes backported, will report back when it's finished (will take at least rest of today to finish).

Cheers,

Quoted 18 lines · Steve Sakoman

Hi Martin,

Quoted 1 line · Martin Jansa

Did you run tune/test.sh script with these on dunfell or do you want me

to?

No, I didn't. I'm not familiar with that script. Can you point me in the right direction?

Quoted 2 lines

It looks OK, but would be good to confirm that it fixes all issues currently in dunfell.

Agreed!

Steve

#7 lore raw

Thanks Martin! I really appreciate the help in testing.

Steve

Quoted 79 lines · Martin Jansa
Quoted 12 lines · Martin Jansa via lists.openembedded.org

The script just finished, I've uploaded the results here:
https://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

There is a lot of changes compared to master, but mostly because I didn't have ARM_INSTRUCTION_SET set to thumb in this run.

That helped to reveal one issue in meta/conf/machine/include/tune-arm9tdmi.inc
which most likely exists in master as well (wasn't detected before just because ARM_INSTRUCTION_SET).
https://git.openembedded.org/openembedded-core-contrib/diff/scripts/tune/log.fake-arm9tdmi.arm9tdmi?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

Quoted 8 lines

And the meta/conf/machine/include/tune-supersparc.inc is failing like it did in master before removal in:
https://git.openembedded.org/openembedded-core/commit/?id=861519337b6e5e986c3c4b8ba253e8339caf0805
which you probably intentionally didn't backport to dunfell.
https://git.openembedded.org/openembedded-core-contrib/diff/scripts/tune/log.fake-supersparc?h=jansa/tune-test-dunfell&id=c87f58e4235fc5c2fe31037917fd999bf4142dca

I'll trigger it once more with thumb enabled to better show what's the difference from master.

test with thumb enabled finished and looks OK
https://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/tune-test-dunfell&id=c8a0a19b8585661c39e1ba7e16d061d0ae2afc74

There is a lot of changes compared to results from master, but those are expected.

The arm9tdmi issue I mentioned before is reproducible in master as well, I've sent fix for master:
https://lists.openembedded.org/g/openembedded-core/message/144002
it could be backported later.

Cheers,

Quoted 42 lines

Cheers,

Quoted 33 lines · Martin Jansa

Hi Steve,

it's from this branch:

https://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/tune-test

I've already started it on top of dunfell with these fixes backported, will report back when it's finished (will take at least rest of today to finish).

Cheers,

Quoted 18 lines · Steve Sakoman

Hi Martin,

Quoted 1 line · Martin Jansa

Did you run tune/test.sh script with these on dunfell or do you want me

to?

No, I didn't. I'm not familiar with that script. Can you point me in the right direction?

Quoted 2 lines

It looks OK, but would be good to confirm that it fixes all issues currently in dunfell.

Agreed!

Steve