Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: 62cfaf0f by Ben Hutchingsat 2019-06-14T13:16:12ZAdd fixes on CIP branches that import_stable missedIn these

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: f57c3e1b by Ben Hutchingsat 2019-06-14T13:10:05ZImport today's CIP releases30 changed

wrote: So the README should refer to that file rather than repeating a list of remotes. import_stable.py doesn't update the "torvalds" remote, and neither did you, so you don't have all the expected

Hi all, CIP kernel team has released Linux kernel 4.19.50-cip3 and 4.4.181-cip33. You can get this release via the git tree at: 4.19.50-cip3: repository:

Hello Ben, I am trying to write a Quickstart about "cip-kernel-sec" for the CIP wiki (see initial draft attached). The Readme file mentions that you need two remote branches (torvalds and stable)

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: ffa1ed40 by Ben Hutchingsat 2019-06-13T21:18:59ZAdd fix for CVE-2019-5489 in 4.41 changed

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: 45959f97 by Ben Hutchingsat 2019-06-13T21:07:43ZMark CVE-2019-11487 to be ignored for 3.16 and 4.4 f06464f8 by

Hello SZ, Sorry for the delay, I'm still waiting on an internal discussion to conclude before making a proposal to CIP. Hopefully I'll get this done by next week. Kind regards, Chris

OK, I added that and sent the patch to the list. I have also sent you a merge request on gitlab with the 3 patches. Thanks, Daniel

A similar bmap patch has been sent to ISAR upstream, but while it gets accepted and until we update the ISAR version, we can use this backport. Signed-off-by: Daniel Sangorrin

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. *Please note that IRC meeting was rescheduled to UTC (GMT) 09:00 starting from

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: 4bc90875 by Ben Hutchingsat 2019-06-11T19:11:20ZImport more data ebea96ce by Ben Hutchingsat

Thanks Michael, It seems that worked out! https://gitlab.com/cip-project/cip-core/deby/-/jobs/229463821 Best regards, Daniel

Hi, Sorry for loooooooooooooooong time. I got kernel config for 4.19 from our development team. Attachment is for OpenBlocks IoT VX2. Best regards. minmin Plat'Home Co., Ltd.

Hi Daniel, I've done some experiments as well [1]. Could you try prefixing the "kas build" command with "gosu builder"? Something like this: gosu builder kas build --target core-image-minimal

Hi Michael, [snip] I tried but I got this weird behavior: https://gitlab.com/cip-project/cip-core/deby/-/jobs/228110647 $ export USER_ID=30000 $ /bin/bash /kas/docker-entrypoint $ whoami root $ cat

Oh, good. I understand the desire to limit the support burden. But I hope that there is a plan to support a newer kernel version eventually, if necessary. Ben. -- Ben Hutchings, Software

Hello, Actually, the iwg20m board does work with the upstream Kernel as well as v4.19.y-cip, e.g. [1]. I think it's just that Renesas doesn't intend to support the board with anything other than

[...] "-Wl,-z,relro" is a gcc option which should result in passing "-z relro" to the linker. Perhaps a Makefile is invoking $(LD) with $(LDFLAGS), where it should be invoking $(CC) instead? In any

[...] This really shouldn't be allowed to happen. All the patches applied to 4.4-cip to support this board were already upstream, so this must be a regression. If this board is used as a basis for