Wolfgang Mauerer (Siemens) (Representative) (Voting)
Daniel Sangorrin (Toshiba)
Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair
Action items from previous meeting
AI (IEC62443): AI (Jan): arrange a call
23rd: DONE
Discussions
Debian-LTS
Finished legal review for contract 24th May
Already submitted for signature on 25th May
Agustín encouraged CIP Members to provide the Debian LTS community a clear message that ARM64 needs to be supported in the next LTS release.
Supporting Reproducible builds
Any opinion?
[Agustin]: this is an important effort for CIP. I would first put effort in creating CIP core with Debian toolset. Then understanding/learning what is required to produce builds following the reproducible builds initiative at Debian.
[SZ]: Agree, maybe we can offer some human resources in this team to reduce the total cost. More information is needed.
Comment: If we fund them, we need to ask them which package need to be reproducible.
AI: Yoshi ask to Chris L. to join this discussion.
IEC62443 Cyber Security Standard
See cip-members mail list
Slides from IEC 62443-4 discussion
Action items
- Comment on previous slides
- Analyze list, map to IEC 62443 requirements
- Select technologies / OSS packages
- Create test cases
Kernel maintenance and testing
Stable kernel review
Backport of pipe.c patch to 4.4.y that fixes LTP fcntl35 test error
Anh The reported that the kernelci build script doesn't copy uImage onto the webserver. kernelci webserver is not aware of the uImage file. Under investigation.
When Greg send stable patches for review, there are some testing results also posted to mail list.
Linaro, buildtests, …
If we can send some results to stable kernel mail list by using LTS kernel, it makes a good impression about CIP effort.
Other topics
cip-dev IRC weekly meetings ongoing.
Codethink requested one pass for OSSJ 2018. Can we have it?
Each member can get one pass.
Additional passes will be allocate by request
CIP kernel talk at OSSJ under preparation.
OSSJ
MOXA will not able to attend F2F meeting
They will join over the network
AI: Prepare a Zoom meeting bridge
Mentor for CIP kernel team or CIP kernel maintainer
Requirements
Member of Linux kernel security team
Stable kernel team
Familiar with the Kernel mainline process.
Not required to be familiar with the 4.4-stable process, although it is desired he/she has previous experience backporting features/patches.
To decide which feature can be backported
Experience in backporting patches
Roll for mentor
Expected workload for mentor
CIP kernel mentor review review results from CIP kernel maintenance team
(Q) Does mentor need to manage CIP kernel tree ?
No. If CIP have a mentor (not maintainer), CIP kernel team manage a CIP kernel tree.
When distributing patches for stable, the mentor give some hints to review the patches.
URLs, etc..
Provides guidance to the maintainters of best practices, provides appropriate feedback on accepted/rejected PRs, patches, etc.
List of candidates for CIP kernel team mentor(s) (or maintainer)
Will contact to the following persons to ask become a mentor of CIP kernel team
Other topics
AI(ALL): Propose topics to be discussed in CIP F2F meeting - Jeff to send shared doc