cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc kselftest-futex: 7 runs, 1 regressions (v5.10.140-cip16-261-g8fa62effa305f) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline: 107 runs, 6 regressions (v5.10.140-cip16-261-g8fa62effa305f) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline-nfs: 28 runs, 1 regressions (v5.10.140-cip16-261-g8fa62effa305f) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc build: 178 builds: 2 failed, 176 passed, 4 errors, 10 warnings (v5.10.140-cip16-261-g8fa62effa305f) Full Build Summary:

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. Our channel is the following: irc:irc.libera.chat:6667/cip The IRC meeting

Hi ! It's this week's CVE report. This week reported 5 new CVEs and 4 updated CVEs. * New CVEs CVE-2022-40476: io_uring: use original request task for inflight tracking CVSS v3 score is 5.5

We should probably flip the defaults in start-qemu.sh now... Quirin, could you cross-check as well? Seems fine to me on a quick glance. Jan -- Siemens AG, Technology Competence Center Embedded

From: Sai <Sai.Sathujoda@...> Updated steps to enable secureboot with user-generated & snakeoil keys. Signed-off-by: Sai <Sai.Sathujoda@...> --- doc/README.secureboot.md |

No no. No need to appologize or resend anything. This is just information to help in future research. regards, dan carpenter

I found the code that might have the vulnerability, and submitted a patch without actually debugging it. This is entirely my fault. sorry. Should I submit a fix patch that fixes the commit

Btw, the other thing which prevents this from being expliotable is that if you pass a negative value to copy_from_user() it will not copy anything because of the check in check_copy_size(). See

The count variable is actually capped at MAX_RW_COUNT in vfs_write() so "words" cannot be negative. This patch helps clean up the code but it does not affect run time. This is

Thanks, applied. Jan -- Siemens AG, Technology Competence Center Embedded Linux

From: Shivanand Kunijadar <Shivanand.Kunijadar@...> Most of the steps are similar for both qemu-amd64 and BBB targets. Add reference link wherever required instead of repeating

Hi Jan, I have mentioned a reference section "building-and-testing-the-cip-core-image" in the readme for BBB, which means we have to create two images (Non-RT and RT) as per the section. I will

This is missing a step: Build a different image configuration, e.g. switching to the RT kernel. Otherwise, you are now suggesting to flash the same SWU on the disk as you write as full image, and we

Hi Jan, Could you please check the below revised patch and let me know your feedback. Thanks & Regards Shivanand K

From: Jan Kiszka <jan.kiszka@...> Was broken by fa31a98f0d18: Export 'sign' which is also needed inside the sudo env and move checksum injection into the chroot so that the ${WORKDIR}/swu/*

cip-gitlab/ci/pavel/linux-test smc: 9 runs, 8 regressions (v4.4-st20-231-g7349cef09ddd2) Regressions Summary ------------------- platform | arch | lab | compiler |

cip-gitlab/ci/pavel/linux-test ltp-timers: 9 runs, 5 regressions (v4.4-st20-231-g7349cef09ddd2) Regressions Summary ------------------- platform | arch | lab | compiler