The concern here would be that "family" is negative and we pass a negative value to test_bit() resulting in an out of bounds read and potentially a crash. This patch is based on static analysis and no

Hello All, We would like to know if anyone has any preference or specific opinions about how CIP Security images should be generated from isar-cip-core meta data [1]. In current configuration, by defa

From: Takashi Sakamoto <o-takashi@...> In ALSA control interface, applications can execute two types of request for value of members on each element; ELEM_READ and ELEM_WRITE. In ALSA control core, th

From: Richard Fitzgerald <rf@...> commit 5a23699a39abc5328921a81b89383d088f6ba9cc upstream. The patch "ALSA: control: code refactoring for ELEM_READ/ELEM_WRITE operations" introduced a potential for k

From: Takashi Sakamoto <o-takashi@...> ALSA control core handles ELEM_READ/ELEM_WRITE requests within lock acquisition of a counting semaphore. The lock is acquired in helper functions in the end of c

I found a bug in v4.4-st38 caused by e8064dec769e6 "ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF" The most serious part is a `down_write` call before calling `snd_ctl_elem_write`

cip/linux-5.10.y-cip smc: 4 runs, 2 regressions (v5.10.176-cip30) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions -----------------------------+-----

cip/linux-5.10.y-cip ltp-timers: 14 runs, 6 regressions (v5.10.176-cip30) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions -------------------------+-

cip/linux-4.19.y-cip smc: 4 runs, 2 regressions (v4.19.279-cip95) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions -----------------------------+-----

cip/linux-4.19.y-cip ltp-timers: 9 runs, 3 regressions (v4.19.279-cip95) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions -------------------------+--

cip/linux-5.10.y-cip baseline: 136 runs, 23 regressions (v5.10.176-cip30) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions --------------------------+

cip/linux-5.10.y-cip baseline-nfs: 45 runs, 11 regressions (v5.10.176-cip30) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions ------------------------

cip/linux-4.19.y-cip baseline-nfs: 38 runs, 2 regressions (v4.19.279-cip95) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions -----------------+-------

cip/linux-4.19.y-cip baseline: 129 runs, 22 regressions (v4.19.279-cip95) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions ---------------------------

cip/linux-5.10.y-cip build: 114 builds: 0 failed, 114 passed, 4 warnings (v5.10.176-cip30) Full Build Summary: https://kernelci.org/build/cip/branch/linux-5.10.y-cip/kernel/v5.10.176-cip30/ Tree: cip

cip/linux-4.19.y-cip build: 122 builds: 0 failed, 122 passed, 23 warnings (v4.19.279-cip95) Full Build Summary: https://kernelci.org/build/cip/branch/linux-4.19.y-cip/kernel/v4.19.279-cip95/ Tree: cip

Hi all, CIP kernel team has released Linux kernel v4.19.279-cip95 and v5.10.176-cip30. The linux-4.19.y-cip tree has been updated base version from v4.19.277 to v4.19.279, and the linux-5.10.y-cip tre

[ANNOUNCE] Release v4.4.302-cip73 Hi, the CIP kernel team has released Linux kernel v4.4.302-cip73. The linux-4.4.y-cip tree's base version has been updated to v4.4-st38. You can get this release via

Hi, I found a bug in v4.4-st38 caused by e8064dec769e6e0822e179107d0b5b3d2e03e181 "ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF" 1) It introduces down_read/up_read around a call

Simple follow-up to the already existing enabling for x86, so I think we can safely squeeze this after rc1 and before final 1.0. Jan Jan Kiszka (3): linux-cip: Bump cip-kernel-config revision kconfig: