Date   

CIP IRC weekly meeting today on libera.chat

Jan Kiszka
 

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 is scheduled to UTC (GMT) 12:00:

https://www.timeanddate.com/worldclock/meetingdetails.html?year=2022&month=9&day=22&hour=12&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

USWest USEast UK DE TW JP
05:00 08:00 13:00 14:00 20:00 21:00

Last meeting minutes:
https://ircbot.wl.linuxfoundation.org/meetings/cip/2022/09/cip.2022-09-15-12.11.log.html

* Action items
1. Resolve/ignore failures of KernelCI on 4.4-cip - alicefm
2. Check cip devices on kernelci old pull request - patersonc
* Kernel maintenance updates
* Kernel testing
* AOB
- task distribution around 4.4 maintenance
- enable Uli to make hot-fix releases as well if needed

Jan


New CVE entries this week

Masami Ichikawa
 

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 MEDIUM.

A null pointer dereference issue was discovered in fs/io_uring.c in
the Linux kernel before 5.15.62. A local user could use this flaw to
crash the system or potentially cause a denial of service.

This vulnerability was introduced by commit d536123 ("io_uring: drop
the old style inflight file tracking") which was merged in 5.19-rc1.
Kernel 5.4 and 5.10 doesn't have commit d536123.

Fixed status
mainline: [386e4fb6962b9f248a80f8870aea0870ca603e89]
stable/5.15: [3746d62ecf1c872a520c4866118edccb121c44fd]

CVE-2022-3176: io_uring: disable polling pollfree files

CVSS v3 score is 7.8 HIGH.

There exists a use-after-free in io_uring in the Linux kernel.
Signalfd_poll() and binder_poll() use a waitqueue whose lifetime is
the current task. It will send a POLLFREE notification to all waiters
before the queue is freed. Unfortunately, the io_uring poll doesn't
handle POLLFREE. This allows a use-after-free to occur if a signalfd
or binder fd is polled with io_uring poll, and the waitqueue gets
freed.

Fixed status
mainline: [791f3465c4afde02d7f16cf7424ca87070b69396]
stable/5.10: [28d8d2737e82fc29ff9e788597661abecc7f7994]
stable/5.15: [e9d7ca0c4640cbebe6840ee3bac66a25a9bacaf5]
stable/5.4: [fc78b2fc21f10c4c9c4d5d659a685710ffa63659]

CVE-2022-40768: scsi: stex: properly zero out the passthrough command structure

CVSS v3 score is 5.5 MEDIUM.

drivers/scsi/stex.c in the Linux kernel through 5.19.9 allows local
users to obtain sensitive information from kernel memory because
stex_queuecommand_lck lacks a memset for the PASSTHRU_CMD case.

Fixed status
Patch is available at
lore.kernel.org/all/20220908145154.2284098-1-gregkh@...
but it has not been merged yet as of 2022-09-19.

CVE-2022-41218: media: dvb-core: Fix UAF due to refcount races at releasing

CVSS v3 score is not assigned.

In drivers/media/dvb-core/dmxdev.c in the Linux kernel through
5.19.10, there is a use-after-free caused by refcount races, affecting
dvb_demux_open and dvb_dmxdev_release.

It looks as if kernel 4.4 is affected too.

Fixed status
Patch is available on
https://lore.kernel.org/all/20220908132754.30532-1-tiwai@suse.de/ but
it hasn't been merged into the mainline yet.

CVE-2022-41222: mm/mremap: hold the rmap lock in write mode when
moving page table entries

CVSS v3 score is not assigned.

mm/mremap.c in the Linux kernel before 5.13.3 has a use-after-free via
a stale TLB because an rmap lock is not held during a PUD move.

kernel 4.x doesn't have 2c91bd4 ("mm: speed up mremap by 20x on large
regions") and c49dd34 ("mm: speedup mremap on 1GB or larger regions")
so that these kernels won't be affected.

mainline: [97113eb39fa7972722ff490b947d8af023e1f6a2]
stable/5.10: [2613baa3ab2153cc45b175c58700d93f72ef36c4]
stable/5.4: [79e522101cf40735f1936a10312e17f937b8dcad]

* Updated CVEs

CVE-2021-4159: bpf: Verifer, adjust_scalar_min_max_vals to always call
update_reg_bounds()

4.14 was fixed this week.

Fixed status
mainline: [294f2fc6da27620a506e6c050241655459ccd6bd]
stable/4.14: [a7cf53f9ebcd887c19588c0c1b4b8260f41a3faa]
stable/4.19: [6c6b84ef5ea8dc0ca3559ccf69810960e348c555]
stable/5.4: [7c1134c7da997523e2834dd516e2ddc51920699a]

CVE-2022-40307: efi: capsule-loader: Fix use-after-free in efi_capsule_write

Stable kernels except 4.9 were fixed this week. Applying the patch to
4.9 was failed (https://lore.kernel.org/stable/166265645917687@kroah.com/).

Fixed status
mainline: [9cb636b5f6a8cc6d1b50809ec8f8d33ae0c84c95]
stable/4.14: [233d5c4d18971feee5fc2f33f00b63d8205cfc67]
stable/4.19: [021805af5bedeafc76c117fc771c100b358ab419]
stable/5.10: [918d9c4a4bdf5205f2fb3f64dddfb56c9a1d01d6]
stable/5.15: [dd291e070be0eca8807476b022bda00c891d9066]
stable/5.19: [d46815a8f26ca6db2336106a148265239f73b0af]
stable/5.4: [8028ff4cdbb3f20d3c1c04be33a83bab0cb94997]

CVE-2022-39188: unmap_mapping_range() race with munmap() on VM_PFNMAP
mappings leads to stale TLB entry

stable/4.19 56fa5f3 ("mm: Fix TLB flush for not-first PFNMAP mappings
in unmap_region()") and stable 5.10 891f03f ("mm: Fix TLB flush for
not-first PFNMAP mappings in unmap_region()") have been added.
These commits are stable specific patches which fix an issue when
backporting the upstream commit b67fbeb ("mmu_gather: Force tlb-flush
VM_PFNMAP vmas"). This fix has been sent to 5.4 and 5.15.

Fixed status
mainline: [b67fbebd4cf980aecbcc750e1462128bffe8ae15]
stable/4.14: [b8a54a2a45feacbc96065e5d6b9a1cbee2aa1e9d]
stable/4.19: [c3b1e88f14e7f442e2ddcbec94527eec84ac0ca3,
56fa5f3dd44a05a5eacd75ae9d00c5415046d371]
stable/4.9: [390f33a95419f7fa1254ba6b6feeabde480732f9]
stable/5.10: [895428ee124ad70b9763259308354877b725c31d,
891f03f688de8418f44b32b88f6b4faed5b2aa81]
stable/5.15: [3ffb97fce282df03723995f5eed6a559d008078e]
stable/5.4: [c9c5501e815132530d741ec9fdd22657f91656bc]

CVE-2022-2663: netfilter: nf_conntrack_irc: Tighten matching on DCC message

mainline and stable kernels were fixed. Commit 0efe125 ("netfilter:
nf_conntrack_irc: Fix forged IP logic") can be applied to 4.4.y-st
without any modification.

Fixed status
mainline: [0efe125cfb99e6773a7434f3463f7c2fa28f3a43]
stable/4.14: [6ce66e3442a5989cbe56a6884384bf0b7d1d0725]
stable/4.19: [3275f7804f40de3c578d2253232349b07c25f146]
stable/4.9: [eb4d8d6b44a23ff2b6e2af06c8240de73dff8a7d]
stable/5.10: [e12ce30fe593dd438c5b392290ad7316befc11ca]
stable/5.15: [451c9ce1e2fc9b9e40303bef8e5a0dca1a923cc4]
stable/5.19: [6cf0609154b2ce8d3ae160e7506ab316400a8d3d]
stable/5.4: [36f7b71f8ad8e4d224b45f7d6ecfeff63b091547]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@...
:masami.ichikawa@...


Re: [isar-cip-core] README.secureboot.md : Update steps for bullseye version

Jan Kiszka
 

On 20.09.22 17:40, Sai.Sathujoda@... wrote:
From: Sai <Sai.Sathujoda@...>

Updated steps to enable secureboot with user-generated & snakeoil keys.

Signed-off-by: Sai <Sai.Sathujoda@...>
---
doc/README.secureboot.md | 62 ++++++++++++++++++++++++++--------------
1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/doc/README.secureboot.md b/doc/README.secureboot.md
index 319b4db..977377a 100644
--- a/doc/README.secureboot.md
+++ b/doc/README.secureboot.md
@@ -76,7 +76,7 @@ Set up a secure boot test environment with [QEMU](https://www.qemu.org/)
### Debian Snakeoil keys

The build copies the Debian Snakeoil keys to the directory `./build/tmp/deploy/images/<machine>/OVMF.
-You can use them as described in section [Start Image](### Start the image).
+You can use them as described in section [Start Image](#start-the-image).

### Generate Keys

@@ -113,7 +113,7 @@ cp /lib/efitools/x86_64-linux-gnu/KeyTool.efi secureboot-tools
to the current directory. OVMF_VARS_4M.fd contains no keys can be instrumented for secureboot.
3. Start QEMU with the script scripts/start-efishell.sh
```
-scripts/start-efishell.sh secureboot-tools
+OVMF_CODE=/usr/share/OVMF/OVMF_CODE_4M.secboot.fd OVMF_VARS=./OVMF_VARS_4M.fd ./scripts/start-efishell.sh secureboot-tools
```
4. Start the KeyTool.efi FS0:\KeyTool.efi and execute the the following steps:
```
@@ -147,16 +147,28 @@ For user-generated keys, create a new option file in the repository. This option
header:
version: 10
includes:
- - kas/opt/ebg-secure-boot-base.yml
+ - kas/opt/ebg-swu.yml
+
+local_conf_header:
+ secure-boot-image: |
+ IMAGE_CLASSES += "verity"
+ IMAGE_FSTYPES = "wic"
+ WKS_FILE = "${MACHINE}-efibootguard-secureboot.wks.in"
+ INITRAMFS_INSTALL_append = " initramfs-verity-hook"
+ # abrootfs cannot be installed together with verity
+ INITRAMFS_INSTALL_remove = " initramfs-abrootfs-hook"

local_conf_header:
secure-boot: |
- IMAGER_BUILD_DEPS += "ebg-secure-boot-secrets"
- IMAGER_INSTALL += "ebg-secure-boot-secrets"
+ IMAGER_BUILD_DEPS += "ebg-secure-boot-signer"
+ IMAGER_INSTALL += "ebg-secure-boot-signer"
+
+# Use user-generated keys
+ PREFERRED_PROVIDER_secure-boot-secrets = "secure-boot-key"
+
user-keys: |
- SB_CERTDB = "democertdb"
- SB_VERIFY_CERT = "demo.crt"
- SB_KEY_NAME = "demo"
+ SB_CERT = "demo.crt"
+ SB_KEY = "demo.key"
```

Replace `demo` with the name of the user-generated certificates. The user-generated certificates
@@ -174,7 +186,7 @@ kas-container build kas-cip.yml:kas/board/qemu-amd64.yml:<path to the new option

Start the image with the following command:
```
-SECURE_BOOT=y \
+SECURE_BOOT=y DISTRO_RELEASE=bullseye \
We should probably flip the defaults in start-qemu.sh now...

./start-qemu.sh amd64
```

@@ -194,27 +206,32 @@ To change the boot behavior, enter `exit` in the shell to enter the bios and cha
#### User-generated keys
Start the image with the following command:
```
-SECURE_BOOT=y \
+SECURE_BOOT=y DISTRO_RELEASE=bullseye \
OVMF_CODE=./build/tmp/deploy/images/qemu-amd64/OVMF/OVMF_CODE_4M.secboot.fd \
OVMF_VARS=<path to the modified OVMF_VARS.fd> \
./start-qemu.sh amd64
```
-
+After boot check the dmesg for secure boot status like below:
+```
+root@demo:~# dmesg | grep Secure
+[ 0.008368] Secure boot enabled
+```
## Example: Update the image

For updating the image, the following steps are necessary:
-- [Build the image with snakeoil keys](### Build image)
+- [Build the image with snakeoil keys](#build-image)
- save the generated swu `build/tmp/deploy/images/qemu-amd64/cip-core-image-cip-core-bullseye-qemu-amd64.swu` to /tmp
-- modify the image for example add a new version to the image by adding `PV=2.0.0` to
- [cip-core-image.bb](recipes-core/images/cip-core-image.bb)
-- start the new target and copy the swu `cip-core-image-cip-core-bullseye-qemu-amd64.swu`
- to the running system, e.g.:
+- modify the image for example, switch to the RT kernel as modification:
+```
+kas-container build kas-cip.yml:kas/board/qemu-amd64.yml:kas/opt/ebg-secure-boot-snakeoil.yml:kas/opt/rt.yml
+```
+- start the new target
```
-SECURE=y ./start-qemu.sh amd64 -virtfs local,path=/tmp,mount_tag=host0,security_model=passthrough,id=host0
+SECURE_BOOT=y DISTRO_RELEASE=bullseye ./start-qemu.sh amd64
```
-- mount `host0` on target with:
+Copy the swu cip-core-image-cip-core-bullseye-qemu-amd64.swu to the running system
```
-mount -t 9p -o trans=virtio,version=9p2000.L host0 /mnt
+scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@....0.1:/home/
```
- check which partition is booted, e.g. with `lsblk`:
```
@@ -228,8 +245,11 @@ sda 8:0 0 2G 0 disk
└─sda5 8:5 0 1000M 0 part
```

-- install with `swupdate -i /mnt/cip-core-image-cip-core-bullseye-qemu-amd64.swu`
-- reboot
+- install the swupdate and reboot the image
+```
+root@demo:~# swupdate -i /home/cip-core-image-cip-core-bullseye-qemu-amd64.swu`
+root@demo:~# reboot
+```
- check which partition is booted, e.g. with `lsblk`. The rootfs should have changed:
```
root@demo:~# lsblk
Quirin, could you cross-check as well? Seems fine to me on a quick glance.

Jan

--
Siemens AG, Technology
Competence Center Embedded Linux


[isar-cip-core] README.secureboot.md : Update steps for bullseye version

sai.sathujoda@...
 

From: Sai <Sai.Sathujoda@...>

Updated steps to enable secureboot with user-generated & snakeoil keys.

Signed-off-by: Sai <Sai.Sathujoda@...>
---
doc/README.secureboot.md | 62 ++++++++++++++++++++++++++--------------
1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/doc/README.secureboot.md b/doc/README.secureboot.md
index 319b4db..977377a 100644
--- a/doc/README.secureboot.md
+++ b/doc/README.secureboot.md
@@ -76,7 +76,7 @@ Set up a secure boot test environment with [QEMU](https://www.qemu.org/)
### Debian Snakeoil keys

The build copies the Debian Snakeoil keys to the directory `./build/tmp/deploy/images/<machine>/OVMF.
-You can use them as described in section [Start Image](### Start the image).
+You can use them as described in section [Start Image](#start-the-image).

### Generate Keys

@@ -113,7 +113,7 @@ cp /lib/efitools/x86_64-linux-gnu/KeyTool.efi secureboot-tools
to the current directory. OVMF_VARS_4M.fd contains no keys can be instrumented for secureboot.
3. Start QEMU with the script scripts/start-efishell.sh
```
-scripts/start-efishell.sh secureboot-tools
+OVMF_CODE=/usr/share/OVMF/OVMF_CODE_4M.secboot.fd OVMF_VARS=./OVMF_VARS_4M.fd ./scripts/start-efishell.sh secureboot-tools
```
4. Start the KeyTool.efi FS0:\KeyTool.efi and execute the the following steps:
```
@@ -147,16 +147,28 @@ For user-generated keys, create a new option file in the repository. This option
header:
version: 10
includes:
- - kas/opt/ebg-secure-boot-base.yml
+ - kas/opt/ebg-swu.yml
+
+local_conf_header:
+ secure-boot-image: |
+ IMAGE_CLASSES += "verity"
+ IMAGE_FSTYPES = "wic"
+ WKS_FILE = "${MACHINE}-efibootguard-secureboot.wks.in"
+ INITRAMFS_INSTALL_append = " initramfs-verity-hook"
+ # abrootfs cannot be installed together with verity
+ INITRAMFS_INSTALL_remove = " initramfs-abrootfs-hook"

local_conf_header:
secure-boot: |
- IMAGER_BUILD_DEPS += "ebg-secure-boot-secrets"
- IMAGER_INSTALL += "ebg-secure-boot-secrets"
+ IMAGER_BUILD_DEPS += "ebg-secure-boot-signer"
+ IMAGER_INSTALL += "ebg-secure-boot-signer"
+
+# Use user-generated keys
+ PREFERRED_PROVIDER_secure-boot-secrets = "secure-boot-key"
+
user-keys: |
- SB_CERTDB = "democertdb"
- SB_VERIFY_CERT = "demo.crt"
- SB_KEY_NAME = "demo"
+ SB_CERT = "demo.crt"
+ SB_KEY = "demo.key"
```

Replace `demo` with the name of the user-generated certificates. The user-generated certificates
@@ -174,7 +186,7 @@ kas-container build kas-cip.yml:kas/board/qemu-amd64.yml:<path to the new option

Start the image with the following command:
```
-SECURE_BOOT=y \
+SECURE_BOOT=y DISTRO_RELEASE=bullseye \
./start-qemu.sh amd64
```

@@ -194,27 +206,32 @@ To change the boot behavior, enter `exit` in the shell to enter the bios and cha
#### User-generated keys
Start the image with the following command:
```
-SECURE_BOOT=y \
+SECURE_BOOT=y DISTRO_RELEASE=bullseye \
OVMF_CODE=./build/tmp/deploy/images/qemu-amd64/OVMF/OVMF_CODE_4M.secboot.fd \
OVMF_VARS=<path to the modified OVMF_VARS.fd> \
./start-qemu.sh amd64
```
-
+After boot check the dmesg for secure boot status like below:
+```
+root@demo:~# dmesg | grep Secure
+[ 0.008368] Secure boot enabled
+```
## Example: Update the image

For updating the image, the following steps are necessary:
-- [Build the image with snakeoil keys](### Build image)
+- [Build the image with snakeoil keys](#build-image)
- save the generated swu `build/tmp/deploy/images/qemu-amd64/cip-core-image-cip-core-bullseye-qemu-amd64.swu` to /tmp
-- modify the image for example add a new version to the image by adding `PV=2.0.0` to
- [cip-core-image.bb](recipes-core/images/cip-core-image.bb)
-- start the new target and copy the swu `cip-core-image-cip-core-bullseye-qemu-amd64.swu`
- to the running system, e.g.:
+- modify the image for example, switch to the RT kernel as modification:
+```
+kas-container build kas-cip.yml:kas/board/qemu-amd64.yml:kas/opt/ebg-secure-boot-snakeoil.yml:kas/opt/rt.yml
+```
+- start the new target
```
-SECURE=y ./start-qemu.sh amd64 -virtfs local,path=/tmp,mount_tag=host0,security_model=passthrough,id=host0
+SECURE_BOOT=y DISTRO_RELEASE=bullseye ./start-qemu.sh amd64
```
-- mount `host0` on target with:
+Copy the swu cip-core-image-cip-core-bullseye-qemu-amd64.swu to the running system
```
-mount -t 9p -o trans=virtio,version=9p2000.L host0 /mnt
+scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@....0.1:/home/
```
- check which partition is booted, e.g. with `lsblk`:
```
@@ -228,8 +245,11 @@ sda 8:0 0 2G 0 disk
└─sda5 8:5 0 1000M 0 part
```

-- install with `swupdate -i /mnt/cip-core-image-cip-core-bullseye-qemu-amd64.swu`
-- reboot
+- install the swupdate and reboot the image
+```
+root@demo:~# swupdate -i /home/cip-core-image-cip-core-bullseye-qemu-amd64.swu`
+root@demo:~# reboot
+```
- check which partition is booted, e.g. with `lsblk`. The rootfs should have changed:
```
root@demo:~# lsblk
--
2.20.1


Re: [PATCH] pxa3xx-gcu: Fix integer overflow in pxa3xx_gcu_write

Dan Carpenter <dan.carpenter@...>
 

On Mon, Sep 19, 2022 at 11:22:41PM -0700, Hyunwoo Kim wrote:
On Tue, Sep 20, 2022 at 09:13:31AM +0300, Dan Carpenter wrote:
On Tue, Sep 20, 2022 at 09:02:34AM +0300, Dan Carpenter wrote:
On Mon, Jun 20, 2022 at 07:00:10AM -0700, Hyunwoo Kim wrote:
In pxa3xx_gcu_write, a count parameter of
type size_t is passed to words of type int.
Then, copy_from_user may cause a heap overflow because
it is used as the third argument of copy_from_user.

Signed-off-by: Hyunwoo Kim <imv4bel@...>
---
drivers/video/fbdev/pxa3xx-gcu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/video/fbdev/pxa3xx-gcu.c b/drivers/video/fbdev/pxa3xx-gcu.c
index 043cc8f9ef1c..c3cd1e1cc01b 100644
--- a/drivers/video/fbdev/pxa3xx-gcu.c
+++ b/drivers/video/fbdev/pxa3xx-gcu.c
@@ -381,7 +381,7 @@ pxa3xx_gcu_write(struct file *file, const char *buff,
struct pxa3xx_gcu_batch *buffer;
struct pxa3xx_gcu_priv *priv = to_pxa3xx_gcu_priv(file);

- int words = count / 4;
+ size_t words = count / 4;
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.
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 commit
6d13de1489b6 ("uaccess: disallow > INT_MAX copy sizes").

Linus has sort of gotten annoyed with me before for pointing this stuff
out because it seemed like maybe I wasn't properly grateful to people
auditing the code and fixing bugs. I am grateful. This patch is
totally the correct thing to do. It's just that it's not really
exploitable as described in the commit message.
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 message?

Sorry again.

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

regards,
dan carpenter


Re: [PATCH] pxa3xx-gcu: Fix integer overflow in pxa3xx_gcu_write

Hyunwoo Kim <imv4bel@...>
 

On Tue, Sep 20, 2022 at 09:13:31AM +0300, Dan Carpenter wrote:
On Tue, Sep 20, 2022 at 09:02:34AM +0300, Dan Carpenter wrote:
On Mon, Jun 20, 2022 at 07:00:10AM -0700, Hyunwoo Kim wrote:
In pxa3xx_gcu_write, a count parameter of
type size_t is passed to words of type int.
Then, copy_from_user may cause a heap overflow because
it is used as the third argument of copy_from_user.

Signed-off-by: Hyunwoo Kim <imv4bel@...>
---
drivers/video/fbdev/pxa3xx-gcu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/video/fbdev/pxa3xx-gcu.c b/drivers/video/fbdev/pxa3xx-gcu.c
index 043cc8f9ef1c..c3cd1e1cc01b 100644
--- a/drivers/video/fbdev/pxa3xx-gcu.c
+++ b/drivers/video/fbdev/pxa3xx-gcu.c
@@ -381,7 +381,7 @@ pxa3xx_gcu_write(struct file *file, const char *buff,
struct pxa3xx_gcu_batch *buffer;
struct pxa3xx_gcu_priv *priv = to_pxa3xx_gcu_priv(file);

- int words = count / 4;
+ size_t words = count / 4;
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.
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 commit
6d13de1489b6 ("uaccess: disallow > INT_MAX copy sizes").

Linus has sort of gotten annoyed with me before for pointing this stuff
out because it seemed like maybe I wasn't properly grateful to people
auditing the code and fixing bugs. I am grateful. This patch is
totally the correct thing to do. It's just that it's not really
exploitable as described in the commit message.
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 message?

Sorry again.


Regards,
Hyunwoo Kim.


Re: [PATCH] pxa3xx-gcu: Fix integer overflow in pxa3xx_gcu_write

Dan Carpenter <dan.carpenter@...>
 

On Tue, Sep 20, 2022 at 09:02:34AM +0300, Dan Carpenter wrote:
On Mon, Jun 20, 2022 at 07:00:10AM -0700, Hyunwoo Kim wrote:
In pxa3xx_gcu_write, a count parameter of
type size_t is passed to words of type int.
Then, copy_from_user may cause a heap overflow because
it is used as the third argument of copy_from_user.

Signed-off-by: Hyunwoo Kim <imv4bel@...>
---
drivers/video/fbdev/pxa3xx-gcu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/video/fbdev/pxa3xx-gcu.c b/drivers/video/fbdev/pxa3xx-gcu.c
index 043cc8f9ef1c..c3cd1e1cc01b 100644
--- a/drivers/video/fbdev/pxa3xx-gcu.c
+++ b/drivers/video/fbdev/pxa3xx-gcu.c
@@ -381,7 +381,7 @@ pxa3xx_gcu_write(struct file *file, const char *buff,
struct pxa3xx_gcu_batch *buffer;
struct pxa3xx_gcu_priv *priv = to_pxa3xx_gcu_priv(file);

- int words = count / 4;
+ size_t words = count / 4;
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.
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 commit
6d13de1489b6 ("uaccess: disallow > INT_MAX copy sizes").

Linus has sort of gotten annoyed with me before for pointing this stuff
out because it seemed like maybe I wasn't properly grateful to people
auditing the code and fixing bugs. I am grateful. This patch is
totally the correct thing to do. It's just that it's not really
exploitable as described in the commit message.

regards,
dan carpenter


Re: [PATCH] pxa3xx-gcu: Fix integer overflow in pxa3xx_gcu_write

Dan Carpenter <dan.carpenter@...>
 

On Mon, Jun 20, 2022 at 07:00:10AM -0700, Hyunwoo Kim wrote:
In pxa3xx_gcu_write, a count parameter of
type size_t is passed to words of type int.
Then, copy_from_user may cause a heap overflow because
it is used as the third argument of copy_from_user.

Signed-off-by: Hyunwoo Kim <imv4bel@...>
---
drivers/video/fbdev/pxa3xx-gcu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/video/fbdev/pxa3xx-gcu.c b/drivers/video/fbdev/pxa3xx-gcu.c
index 043cc8f9ef1c..c3cd1e1cc01b 100644
--- a/drivers/video/fbdev/pxa3xx-gcu.c
+++ b/drivers/video/fbdev/pxa3xx-gcu.c
@@ -381,7 +381,7 @@ pxa3xx_gcu_write(struct file *file, const char *buff,
struct pxa3xx_gcu_batch *buffer;
struct pxa3xx_gcu_priv *priv = to_pxa3xx_gcu_priv(file);

- int words = count / 4;
+ size_t words = count / 4;
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 CVE-2022-39842.

regards,
dan carpenter

PS: The other relavant code for people looking for integer overflows in
read/write functions is in rw_verify_area(). That function prevents a
lot of suspicious looking driver code from being exploitable.


Re: [isar-cip-core v3] README.swupdate.md: Add steps to verify SWUpdate on BBB

Jan Kiszka
 

On 20.09.22 12:36, Shivanand.Kunijadar@... wrote:
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 steps.

Signed-off-by: Shivanand Kunijadar <Shivanand.Kunijadar@...>
---
doc/README.swupdate.md | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)

diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md
index 1b242a2..97de777 100644
--- a/doc/README.swupdate.md
+++ b/doc/README.swupdate.md
@@ -32,6 +32,8 @@ Copy `cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in
host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost:
```

+## SWUpdate verification
+
Check which partition is booted, e.g. with lsblk:
```
root@demo:~# lsblk
@@ -215,3 +217,27 @@ user variables:


```
+
+# Building and testing the CIP Core image for BBB
+
+Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files.
+- Replace qemu-amd64.yml kas file with BBB board specific file i.e bbb.yml
+- .swu file will be generated in the following folder build/tmp/deploy/images/bbb/
+- Create Non-RT and RT Kernel images as mentioned in the section
+
+Flash the BeagleBone Black RT kernel image into SDcard
+```
+host$ dd if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \
+ of=/dev/<medium-device> bs=1M status=progress
+```
+
+After flashing the BBB RT kernel image into SD card, mount the SD card on host PC and copy .swu file from `tmp` folder to root partition like below.
+
+```
+host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu /<mnt>/home/root/
+```
+
+Connect a serial port cable between host PC and BBB.
+Insert SD card to BBB, hold S2 button while applying power supply to BBB.
+
+For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification).
Thanks, applied.

Jan
--
Siemens AG, Technology
Competence Center Embedded Linux


[isar-cip-core v3] README.swupdate.md: Add steps to verify SWUpdate on BBB

Kunijadar Shivanand
 

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 steps.

Signed-off-by: Shivanand Kunijadar <Shivanand.Kunijadar@...>
---
doc/README.swupdate.md | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)

diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md
index 1b242a2..97de777 100644
--- a/doc/README.swupdate.md
+++ b/doc/README.swupdate.md
@@ -32,6 +32,8 @@ Copy `cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in
host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost:
```

+## SWUpdate verification
+
Check which partition is booted, e.g. with lsblk:
```
root@demo:~# lsblk
@@ -215,3 +217,27 @@ user variables:


```
+
+# Building and testing the CIP Core image for BBB
+
+Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files.
+- Replace qemu-amd64.yml kas file with BBB board specific file i.e bbb.yml
+- .swu file will be generated in the following folder build/tmp/deploy/images/bbb/
+- Create Non-RT and RT Kernel images as mentioned in the section
+
+Flash the BeagleBone Black RT kernel image into SDcard
+```
+host$ dd if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \
+ of=/dev/<medium-device> bs=1M status=progress
+```
+
+After flashing the BBB RT kernel image into SD card, mount the SD card on host PC and copy .swu file from `tmp` folder to root partition like below.
+
+```
+host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu /<mnt>/home/root/
+```
+
+Connect a serial port cable between host PC and BBB.
+Insert SD card to BBB, hold S2 button while applying power supply to BBB.
+
+For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification).
--
2.20.1


Re: [isar-cip-core v2] README.swupdate.md: Add steps to verify SWUpdate on BBB

Kunijadar Shivanand
 

Hi Jan,

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 know that this is broken (plus we have no error detection for that yet).
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 clearly mention in BBB section to create two images.

Thanks & Regards
Shivanand K

-----Original Message-----
From: cip-dev@... <cip-dev@...> On Behalf Of Jan Kiszka
Sent: Tuesday, September 20, 2022 3:46 PM
To: kunijadar shivanand(TSIP TMIEC ODG Porting) <Shivanand.Kunijadar@...>; cip-dev@...
Cc: dinesh kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@...>; hayashi kazuhiro(林 和宏 □SWC◯ACT) <kazuhiro3.hayashi@...>
Subject: Re: [cip-dev] [isar-cip-core v2] README.swupdate.md: Add steps to verify SWUpdate on BBB

On 16.09.22 13:43, Shivanand.Kunijadar@... wrote:
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 steps.

Signed-off-by: Shivanand Kunijadar
<Shivanand.Kunijadar@...>
---
doc/README.swupdate.md | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)

diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md index
1b242a2..9be3498 100644
--- a/doc/README.swupdate.md
+++ b/doc/README.swupdate.md
@@ -32,6 +32,8 @@ Copy
`cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost:
```

+## SWUpdate verification
+
Check which partition is booted, e.g. with lsblk:
```
root@demo:~# lsblk
@@ -215,3 +217,26 @@ user variables:


```
+
+# Building and testing the CIP Core image for BBB
+
+Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files.
+- Replace qemu-amd64.yml kas file with BBB board specific file i.e
+bbb.yml
+- .swu file will be generated in the following folder
+build/tmp/deploy/images/bbb/
+
+Flash the BeagleBone Black image into SDcard ``` host$ dd
+if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \
+ of=/dev/<medium-device> bs=1M status=progress ```
+
+After flashing the BBB image into SD card, mount the SD card on host PC and copy .swu file directly to root partition like below.
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 know that this is broken (plus we have no error detection for that yet).

Jan

+
+```
+host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu
+/<mnt>/home/root/ ```
+
+Connect a serial port cable between host PC and BBB.
+Insert SD card to BBB, hold S2 button while applying power supply to BBB.
+
+For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification).
--
Siemens AG, Technology
Competence Center Embedded Linux


Re: [isar-cip-core v2] README.swupdate.md: Add steps to verify SWUpdate on BBB

Jan Kiszka
 

On 16.09.22 13:43, Shivanand.Kunijadar@... wrote:
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 steps.

Signed-off-by: Shivanand Kunijadar <Shivanand.Kunijadar@...>
---
doc/README.swupdate.md | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)

diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md
index 1b242a2..9be3498 100644
--- a/doc/README.swupdate.md
+++ b/doc/README.swupdate.md
@@ -32,6 +32,8 @@ Copy `cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in
host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost:
```

+## SWUpdate verification
+
Check which partition is booted, e.g. with lsblk:
```
root@demo:~# lsblk
@@ -215,3 +217,26 @@ user variables:


```
+
+# Building and testing the CIP Core image for BBB
+
+Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files.
+- Replace qemu-amd64.yml kas file with BBB board specific file i.e bbb.yml
+- .swu file will be generated in the following folder build/tmp/deploy/images/bbb/
+
+Flash the BeagleBone Black image into SDcard
+```
+host$ dd if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \
+ of=/dev/<medium-device> bs=1M status=progress
+```
+
+After flashing the BBB image into SD card, mount the SD card on host PC and copy .swu file directly to root partition like below.
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 know that
this is broken (plus we have no error detection for that yet).

Jan

+
+```
+host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu /<mnt>/home/root/
+```
+
+Connect a serial port cable between host PC and BBB.
+Insert SD card to BBB, hold S2 button while applying power supply to BBB.
+
+For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification).
--
Siemens AG, Technology
Competence Center Embedded Linux


Re: [isar-cip-core v2] README.swupdate.md: Add steps to verify SWUpdate on BBB

Kunijadar Shivanand
 

Hi Jan,

Could you please check the below revised patch and let me know your feedback.

Thanks & Regards
Shivanand K

-----Original Message-----
From: Shivanand.Kunijadar@... <Shivanand.Kunijadar@...>
Sent: Friday, September 16, 2022 5:14 PM
To: cip-dev@...; jan.kiszka@...
Cc: kunijadar shivanand(TSIP TMIEC ODG Porting) <Shivanand.Kunijadar@...>; dinesh kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@...>; hayashi kazuhiro(林 和宏 □SWC◯ACT) <kazuhiro3.hayashi@...>
Subject: [isar-cip-core v2] README.swupdate.md: Add steps to verify SWUpdate on BBB

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 steps.

Signed-off-by: Shivanand Kunijadar <Shivanand.Kunijadar@...>
---
doc/README.swupdate.md | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)

diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md index 1b242a2..9be3498 100644
--- a/doc/README.swupdate.md
+++ b/doc/README.swupdate.md
@@ -32,6 +32,8 @@ Copy `cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost:
```

+## SWUpdate verification
+
Check which partition is booted, e.g. with lsblk:
```
root@demo:~# lsblk
@@ -215,3 +217,26 @@ user variables:


```
+
+# Building and testing the CIP Core image for BBB
+
+Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files.
+- Replace qemu-amd64.yml kas file with BBB board specific file i.e
+bbb.yml
+- .swu file will be generated in the following folder
+build/tmp/deploy/images/bbb/
+
+Flash the BeagleBone Black image into SDcard ``` host$ dd
+if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \
+ of=/dev/<medium-device> bs=1M status=progress ```
+
+After flashing the BBB image into SD card, mount the SD card on host PC and copy .swu file directly to root partition like below.
+
+```
+host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu
+/<mnt>/home/root/ ```
+
+Connect a serial port cable between host PC and BBB.
+Insert SD card to BBB, hold S2 button while applying power supply to BBB.
+
+For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification).
--
2.20.1


[PATCH] swupdate: Fix swu signing

Jan Kiszka
 

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/* links work as they should.

Reported by: Rafal Radziejewski <rafal.radziejewski.ext@...>
Signed-off-by: Jan Kiszka <jan.kiszka@...>
---
classes/swupdate.bbclass | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/classes/swupdate.bbclass b/classes/swupdate.bbclass
index 46d2a36..451239e 100644
--- a/classes/swupdate.bbclass
+++ b/classes/swupdate.bbclass
@@ -58,19 +58,18 @@ do_swupdate_binary() {
image_do_mounts

# Prepare for signing
- sign='${@'x' if bb.utils.to_boolean(d.getVar('SWU_SIGNED')) else ''}'
+ export sign='${@'x' if bb.utils.to_boolean(d.getVar('SWU_SIGNED')) else ''}'
if [ -n "$sign" ]; then
cp -f '${SIGN_KEY}' '${WORKDIR}/dev.key'
test -e '${SIGN_CRT}' && cp -f '${SIGN_CRT}' '${WORKDIR}/dev.crt'
fi

- # Fill in file check sums
- for file in ${SWU_ADDITIONAL_FILES}; do
- sed -i "s:$file-sha256:$(sha256sum '${WORKDIR}/swu/'$file | cut -f 1 -d ' '):g" \
- '${WORKDIR}/swu/${SWU_DESCRIPTION_FILE}'
- done
-
sudo -E chroot ${BUILDCHROOT_DIR} sh -c ' \
+ # Fill in file check sums
+ for file in ${SWU_ADDITIONAL_FILES}; do
+ sed -i "s:$file-sha256:$(sha256sum "${PP_WORK}/swu/"$file | cut -f 1 -d " "):g" \
+ "${PP_WORK}/swu/${SWU_DESCRIPTION_FILE}"
+ done
cd "${PP_WORK}/swu"
for file in "${SWU_DESCRIPTION_FILE}" ${SWU_ADDITIONAL_FILES}; do
echo "$file"
--
2.35.3


cip-gitlab/ci/pavel/linux-test smc: 9 runs, 8 regressions (v4.4-st20-231-g7349cef09ddd2) #kernelci

kernelci.org bot <bot@...>
 

cip-gitlab/ci/pavel/linux-test smc: 9 runs, 8 regressions (v4.4-st20-231-g7349cef09ddd2)

Regressions Summary
-------------------

platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
hp-x360-12b-c...4020-octopus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
qemu_arm-virt-gicv3 | arm | lab-broonie | gcc-10 | multi_v7_defconfig | 1
qemu_arm-virt-gicv3 | arm | lab-collabora | gcc-10 | multi_v7_defconfig | 1
qemu_x86_64 | x86_64 | lab-broonie | gcc-10 | x86_64_defconfig | 1
qemu_x86_64 | x86_64 | lab-broonie | gcc-10 | x86_64_defcon...6-chromebook | 1
qemu_x86_64 | x86_64 | lab-collabora | gcc-10 | x86_64_defconfig | 2
qemu_x86_64 | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4-st20-231-g7349cef09ddd2/plan/smc/

Test: smc
Tree: cip-gitlab
Branch: ci/pavel/linux-test
Describe: v4.4-st20-231-g7349cef09ddd2
URL: https://gitlab.com/cip-project/cip-kernel/linux-cip.git
SHA: 7349cef09ddd27c4d55cc11d23fdf232c9184ccc


Test Regressions
----------------


platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
hp-x360-12b-c...4020-octopus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/6327329cf331268b9e355646

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/smc-hp-x360-12b-ca0010nr-n4020-octopus.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/smc-hp-x360-12b-ca0010nr-n4020-octopus.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20220805.0/x86/rootfs.cpio.gz


* smc.login: https://kernelci.org/test/case/id/6327329cf331268b9e355647
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
qemu_arm-virt-gicv3 | arm | lab-broonie | gcc-10 | multi_v7_defconfig | 1

Details: https://kernelci.org/test/plan/id/632731caebf112933e35564d

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/arm/multi_v7_defconfig/gcc-10/lab-broonie/smc-qemu_arm-virt-gicv3.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/arm/multi_v7_defconfig/gcc-10/lab-broonie/smc-qemu_arm-virt-gicv3.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20220805.0/armel/rootfs.cpio.gz


* smc.login: https://kernelci.org/test/case/id/632731caebf112933e35564e
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
qemu_arm-virt-gicv3 | arm | lab-collabora | gcc-10 | multi_v7_defconfig | 1

Details: https://kernelci.org/test/plan/id/632730db068545f19f355660

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/arm/multi_v7_defconfig/gcc-10/lab-collabora/smc-qemu_arm-virt-gicv3.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/arm/multi_v7_defconfig/gcc-10/lab-collabora/smc-qemu_arm-virt-gicv3.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20220805.0/armel/rootfs.cpio.gz


* smc.login: https://kernelci.org/test/case/id/632730db068545f19f355661
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
qemu_x86_64 | x86_64 | lab-broonie | gcc-10 | x86_64_defconfig | 1

Details: https://kernelci.org/test/plan/id/63272e82d997f6677735565b

Results: 15 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig/gcc-10/lab-broonie/smc-qemu_x86_64.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig/gcc-10/lab-broonie/smc-qemu_x86_64.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20220805.0/x86/rootfs.cpio.gz


* smc.CVE-2017-5715: https://kernelci.org/test/case/id/63272e82d997f66777355667
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)

2022-09-18T14:43:06.692296 [ 11.127079] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2017-5715 RESULT=fail>



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
qemu_x86_64 | x86_64 | lab-broonie | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272fb014aec066c4355642

Results: 15 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-broonie/smc-qemu_x86_64.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-broonie/smc-qemu_x86_64.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20220805.0/x86/rootfs.cpio.gz


* smc.CVE-2017-5715: https://kernelci.org/test/case/id/63272fb014aec066c4355651
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)

2022-09-18T14:47:57.404546 [ 11.847407] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2017-5715 RESULT=fail>



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
qemu_x86_64 | x86_64 | lab-collabora | gcc-10 | x86_64_defconfig | 2

Details: https://kernelci.org/test/plan/id/63272e4c1742e1b61235564b

Results: 14 PASS, 2 FAIL, 0 SKIP
Full config: x86_64_defconfig
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig/gcc-10/lab-collabora/smc-qemu_x86_64.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig/gcc-10/lab-collabora/smc-qemu_x86_64.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20220805.0/x86/rootfs.cpio.gz


* smc.CVE-2020-0543: https://kernelci.org/test/case/id/63272e4c1742e1b61235564d
failing since 32 days (last pass: v5.10.131-cip13-49-g1145e9c6352e6, first fail: v5.10.131-cip13-84-g5fcbe4a63ab4d)

2022-09-18T14:42:08.262192 [ 1.957396] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2018-12207 RESULT=pass>
2022-09-18T14:42:08.266287 [ 1.962303] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2020-0543 RESULT=fail>

* smc.CVE-2017-5715: https://kernelci.org/test/case/id/63272e4c1742e1b61235565a
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)

2022-09-18T14:42:08.210437 [ 1.906503] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2017-5715 RESULT=fail>



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
qemu_x86_64 | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272ed3530df17110355679

Results: 15 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/smc-qemu_x86_64.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/smc-qemu_x86_64.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20220805.0/x86/rootfs.cpio.gz


* smc.CVE-2017-5715: https://kernelci.org/test/case/id/63272ed3530df17110355688
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)

2022-09-18T14:44:32.251652 [ 4.825247] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2017-5715 RESULT=fail>


cip-gitlab/ci/pavel/linux-test ltp-timers: 9 runs, 5 regressions (v4.4-st20-231-g7349cef09ddd2) #kernelci

kernelci.org bot <bot@...>
 

cip-gitlab/ci/pavel/linux-test ltp-timers: 9 runs, 5 regressions (v4.4-st20-231-g7349cef09ddd2)

Regressions Summary
-------------------

platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C433TA-AJ0005-rammus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
asus-C436FA-Flip-hatch | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
asus-C523NA-A20057-coral | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
rk3288-veyron-jaq | arm | lab-collabora | gcc-10 | multi_v7_defconfig | 1

Details: https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4-st20-231-g7349cef09ddd2/plan/ltp-timers/

Test: ltp-timers
Tree: cip-gitlab
Branch: ci/pavel/linux-test
Describe: v4.4-st20-231-g7349cef09ddd2
URL: https://gitlab.com/cip-project/cip-kernel/linux-cip.git
SHA: 7349cef09ddd27c4d55cc11d23fdf232c9184ccc

Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: 48cfd7a9977e6268b4aa2600608cebad7e0e42b8


Test Regressions
----------------


platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C433TA-AJ0005-rammus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272f507ed5d5fb4935567a

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-timers-asus-C433TA-AJ0005-rammus.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-timers-asus-C433TA-AJ0005-rammus.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-timers.login: https://kernelci.org/test/case/id/63272f507ed5d5fb4935567b
failing since 12 days (last pass: v5.10.131-cip13-84-g5fcbe4a63ab4d, first fail: v5.10.138-cip15-10-g52cbd8ad1543e)



platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C436FA-Flip-hatch | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/6327300e81ef292161355676

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-timers-asus-C436FA-Flip-hatch.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-timers-asus-C436FA-Flip-hatch.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-timers.login: https://kernelci.org/test/case/id/6327300e81ef292161355677
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C523NA-A20057-coral | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272f058c396b284135565a

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-timers-asus-C523NA-A20057-coral.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-timers-asus-C523NA-A20057-coral.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-timers.login: https://kernelci.org/test/case/id/63272f058c396b284135565b
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272f58ce3da7d112355650

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-timers-hp-11A-G6-EE-grunt.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-timers-hp-11A-G6-EE-grunt.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-timers.login: https://kernelci.org/test/case/id/63272f58ce3da7d112355651
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
rk3288-veyron-jaq | arm | lab-collabora | gcc-10 | multi_v7_defconfig | 1

Details: https://kernelci.org/test/plan/id/632734063cbc79f69e355647

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/arm/multi_v7_defconfig/gcc-10/lab-collabora/ltp-timers-rk3288-veyron-jaq.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/arm/multi_v7_defconfig/gcc-10/lab-collabora/ltp-timers-rk3288-veyron-jaq.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/armhf/initrd.cpio.gz


* ltp-timers.login: https://kernelci.org/test/case/id/632734063cbc79f69e355648
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)


cip-gitlab/ci/pavel/linux-test ltp-pty: 3 runs, 3 regressions (v4.4-st20-231-g7349cef09ddd2) #kernelci

kernelci.org bot <bot@...>
 

cip-gitlab/ci/pavel/linux-test ltp-pty: 3 runs, 3 regressions (v4.4-st20-231-g7349cef09ddd2)

Regressions Summary
-------------------

platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C433TA-AJ0005-rammus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
asus-C523NA-A20057-coral | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4-st20-231-g7349cef09ddd2/plan/ltp-pty/

Test: ltp-pty
Tree: cip-gitlab
Branch: ci/pavel/linux-test
Describe: v4.4-st20-231-g7349cef09ddd2
URL: https://gitlab.com/cip-project/cip-kernel/linux-cip.git
SHA: 7349cef09ddd27c4d55cc11d23fdf232c9184ccc

Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: 48cfd7a9977e6268b4aa2600608cebad7e0e42b8


Test Regressions
----------------


platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C433TA-AJ0005-rammus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272f048c396b2841355656

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-pty-asus-C433TA-AJ0005-rammus.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-pty-asus-C433TA-AJ0005-rammus.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-pty.login: https://kernelci.org/test/case/id/63272f048c396b2841355657
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C523NA-A20057-coral | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272f81018d59c4a0355643

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-pty-asus-C523NA-A20057-coral.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-pty-asus-C523NA-A20057-coral.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-pty.login: https://kernelci.org/test/case/id/63272f81018d59c4a0355644
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/632735c5fcb983254a35564e

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-pty-hp-11A-G6-EE-grunt.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-pty-hp-11A-G6-EE-grunt.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-pty.login: https://kernelci.org/test/case/id/632735c5fcb983254a35564f
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)


cip-gitlab/ci/pavel/linux-test ltp-mm: 4 runs, 4 regressions (v4.4-st20-231-g7349cef09ddd2) #kernelci

kernelci.org bot <bot@...>
 

cip-gitlab/ci/pavel/linux-test ltp-mm: 4 runs, 4 regressions (v4.4-st20-231-g7349cef09ddd2)

Regressions Summary
-------------------

platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
asus-C436FA-Flip-hatch | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
asus-C523NA-A20057-coral | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
hp-x360-12b-c...4020-octopus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4-st20-231-g7349cef09ddd2/plan/ltp-mm/

Test: ltp-mm
Tree: cip-gitlab
Branch: ci/pavel/linux-test
Describe: v4.4-st20-231-g7349cef09ddd2
URL: https://gitlab.com/cip-project/cip-kernel/linux-cip.git
SHA: 7349cef09ddd27c4d55cc11d23fdf232c9184ccc

Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: 48cfd7a9977e6268b4aa2600608cebad7e0e42b8


Test Regressions
----------------


platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
asus-C436FA-Flip-hatch | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/6327315ecd9c92663235565d

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-mm-asus-C436FA-Flip-hatch.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-mm-asus-C436FA-Flip-hatch.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-mm.login: https://kernelci.org/test/case/id/6327315ecd9c92663235565e
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
asus-C523NA-A20057-coral | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/632736495e77a5f365355645

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-mm-asus-C523NA-A20057-coral.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-mm-asus-C523NA-A20057-coral.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-mm.login: https://kernelci.org/test/case/id/632736495e77a5f365355646
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272f5311c5227ef4355662

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-mm-hp-11A-G6-EE-grunt.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-mm-hp-11A-G6-EE-grunt.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-mm.login: https://kernelci.org/test/case/id/63272f5311c5227ef4355663
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
hp-x360-12b-c...4020-octopus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63273005b3730f4785355660

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-mm-hp-x360-12b-ca0010nr-n4020-octopus.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-mm-hp-x360-12b-ca0010nr-n4020-octopus.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-mm.login: https://kernelci.org/test/case/id/63273005b3730f4785355661
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)


cip-gitlab/ci/pavel/linux-test ltp-ipc: 7 runs, 5 regressions (v4.4-st20-231-g7349cef09ddd2) #kernelci

kernelci.org bot <bot@...>
 

cip-gitlab/ci/pavel/linux-test ltp-ipc: 7 runs, 5 regressions (v4.4-st20-231-g7349cef09ddd2)

Regressions Summary
-------------------

platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
asus-C436FA-Flip-hatch | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
asus-C523NA-A20057-coral | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
asus-cx9400-volteer | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
hp-x360-12b-c...4020-octopus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4-st20-231-g7349cef09ddd2/plan/ltp-ipc/

Test: ltp-ipc
Tree: cip-gitlab
Branch: ci/pavel/linux-test
Describe: v4.4-st20-231-g7349cef09ddd2
URL: https://gitlab.com/cip-project/cip-kernel/linux-cip.git
SHA: 7349cef09ddd27c4d55cc11d23fdf232c9184ccc

Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: 48cfd7a9977e6268b4aa2600608cebad7e0e42b8


Test Regressions
----------------


platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
asus-C436FA-Flip-hatch | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63273176cd9c926632355685

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-asus-C436FA-Flip-hatch.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-asus-C436FA-Flip-hatch.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-ipc.login: https://kernelci.org/test/case/id/63273176cd9c926632355686
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
asus-C523NA-A20057-coral | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272ef7b34dab689935566c

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-asus-C523NA-A20057-coral.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-asus-C523NA-A20057-coral.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-ipc.login: https://kernelci.org/test/case/id/63272ef7b34dab689935566d
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
asus-cx9400-volteer | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272ff314aec066c43556a6

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-asus-cx9400-volteer.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-asus-cx9400-volteer.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-ipc.login: https://kernelci.org/test/case/id/63272ff314aec066c43556a7
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272eefcbc36d5a0f35568e

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-hp-11A-G6-EE-grunt.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-hp-11A-G6-EE-grunt.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-ipc.login: https://kernelci.org/test/case/id/63272eefcbc36d5a0f35568f
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
-----------------------------+--------+---------------+----------+------------------------------+------------
hp-x360-12b-c...4020-octopus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/6327315cd949be4e90355689

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-hp-x360-12b-ca0010nr-n4020-octopus.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-ipc-hp-x360-12b-ca0010nr-n4020-octopus.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-ipc.login: https://kernelci.org/test/case/id/6327315cd949be4e9035568a
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)


cip-gitlab/ci/pavel/linux-test ltp-fcntl-locktests: 3 runs, 2 regressions (v4.4-st20-231-g7349cef09ddd2) #kernelci

kernelci.org bot <bot@...>
 

cip-gitlab/ci/pavel/linux-test ltp-fcntl-locktests: 3 runs, 2 regressions (v4.4-st20-231-g7349cef09ddd2)

Regressions Summary
-------------------

platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C433TA-AJ0005-rammus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4-st20-231-g7349cef09ddd2/plan/ltp-fcntl-locktests/

Test: ltp-fcntl-locktests
Tree: cip-gitlab
Branch: ci/pavel/linux-test
Describe: v4.4-st20-231-g7349cef09ddd2
URL: https://gitlab.com/cip-project/cip-kernel/linux-cip.git
SHA: 7349cef09ddd27c4d55cc11d23fdf232c9184ccc

Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: 48cfd7a9977e6268b4aa2600608cebad7e0e42b8


Test Regressions
----------------


platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
asus-C433TA-AJ0005-rammus | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272f09d27ffc3de635564b

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-fcntl-locktests-asus-C433TA-AJ0005-rammus.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-fcntl-locktests-asus-C433TA-AJ0005-rammus.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-fcntl-locktests.login: https://kernelci.org/test/case/id/63272f09d27ffc3de635564c
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)



platform | arch | lab | compiler | defconfig | regressions
--------------------------+--------+---------------+----------+------------------------------+------------
hp-11A-G6-EE-grunt | x86_64 | lab-collabora | gcc-10 | x86_64_defcon...6-chromebook | 1

Details: https://kernelci.org/test/plan/id/63272f08d27ffc3de6355648

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: x86_64_defconfig+x86-chromebook
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-fcntl-locktests-hp-11A-G6-EE-grunt.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st20-231-g7349cef09ddd2/x86_64/x86_64_defconfig+x86-chromebook/gcc-10/lab-collabora/ltp-fcntl-locktests-hp-11A-G6-EE-grunt.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20220826.0/amd64/initrd.cpio.gz


* ltp-fcntl-locktests.login: https://kernelci.org/test/case/id/63272f08d27ffc3de6355649
failing since 0 day (last pass: v5.10.138-cip15-10-g52cbd8ad1543e, first fail: v4.4-st20-229-gb433f12afe250)

41 - 60 of 9573