From: Quirin Gylstorff <quirin.gylstorff@...> As we need the output of `veritysetup` to generate the initrd. Therefore do_verity_image must be called before wic generates the final disk

*This patch series adds support for a read-only squashfs based root filesystem wit SWUpdate support and secureboot. The build is somewhat complex as we need the output of dm-verity to generate the

From: Quirin Gylstorff <quirin.gylstorff@...> Adapt the initrd to open a dm-verity partition with a fixed root hash. The initramfs script is based on [1]. [1]:

Hi! So this has enough information to tell me that we have a kernel problem there, good: 02:08:17.792502 <6>[ 18.847320] omap-mailbox 4a0f4000.mailbox: omap mailbox rev 0x400 02:08:17.800596

Hi! So... I tried to understand this report, and still could not. First problem is actually in the From: line. By placing bot there, it is not clear who is responsible for this, and if someone reads

cip/linux-4.19.y-cip baseline: 121 runs, 1 regressions (v4.19.217-cip62) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig |

cip/linux-4.19.y-cip baseline-nfs: 12 runs, 1 regressions (v4.19.217-cip62) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig |

cip/linux-4.19.y-cip build: 118 builds: 1 failed, 117 passed, 2 errors, 13 warnings (v4.19.217-cip62) Full Build Summary:

Hi ! Thank you for the patch ! Yes, applying code and works properly is different question. however, your patch is LGTM. Regards, -- Masami Ichikawa Cybertrust Japan Co., Ltd. Email

Hi! As far as I can tell, logic is quite simple there and the patch would look like this. Whether the final result works and closes the security hole is different question. Best

hello everyone, following on yesterday topic about difference from cip-cip+1 and lts-lts+1 I just made a diff of what was requested yesterday v4.19.216-cip61 vs v4.19.216 the diff can be viewed on

Hi ! Thank you for your analysis result ! I applied it. I checked 27c24fda62b601d6f9ca5e992502578c4310876f is able to apply cleanly to stable/5.10 tree or not. Unfortunately it need to

Hi ! Thank you for the review! I send patch to the stable list.\ Regards, -- Masami Ichikawa Cybertrust Japan Co., Ltd. Email :masami.ichikawa@...

Hi ! <nobuhiro1.iwamatsu@...> wrote: Thank you ! I added a comment and sent patch to the stable list. -- Masami Ichikawa Cybertrust Japan Co., Ltd. Email

Hi Kazu, [1] containts the current state of the integration of [2] into isar-cip-core. It can be tested for booting, but for SWUpdate test the u-boot environment is not correct. [1]:

Hi! Aha, but we have required information in cip-kernel-sec/issues/CVE-2021-3640.yml. It lists patches that should be fixing this. Some searching in the trees reveals that one of those patches is

Hi! Interesting. commit 99c23da0eed4fd20cae8243f2b51e10e66aa0951 Author: Takashi Iwai <tiwai@...> Says: This should be the last piece for fixing CVE-2021-3640 after a few already

Hi! Thank you. Looks good to me, Reviewed-by: Pavel Machek <pavel@...> Best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich,

Hi, Thanks, LGTM. I think it would be better to add the comment of the conflict fixing. e.g.

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. Please note that we moved from Freenode to libera.chat. Our channel is the