civilinfrastructureplatform:tsc-meetings:tsc_mm_jul232018
Differences
This shows you the differences between two versions of the page.
|
civilinfrastructureplatform:tsc-meetings:tsc_mm_jul232018 [2018/09/20 15:58] yoshi created |
civilinfrastructureplatform:tsc-meetings:tsc_mm_jul232018 [2018/09/20 15:59] (current) yoshi |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== CIP Technical Steering Committee Meeting ====== | ====== CIP Technical Steering Committee Meeting ====== | ||
| - | Date: 06 August, 2018 | + | Date: 23 July, 2018 |
| ===== Roll Call ===== | ===== Roll Call ===== | ||
| Line 9: | Line 9: | ||
| * Attendees | * Attendees | ||
| * Agustin Benito Bethencourt (Codethink) (Representative) | * Agustin Benito Bethencourt (Codethink) (Representative) | ||
| + | * Chris Paterson (Renesas) | ||
| * Masashi Kudo (Cybertrust) | * Masashi Kudo (Cybertrust) | ||
| - | * HIroshi Mine (Hitachi) | ||
| * Hidehiro Kawai (Hitachi) (Representative) (Voting) | * Hidehiro Kawai (Hitachi) (Representative) (Voting) | ||
| * Masato Minda (Plat’Home) (Representative) | * Masato Minda (Plat’Home) (Representative) | ||
| * Takehisa Katayama (Renesas) (Representative) (Voting) | * Takehisa Katayama (Renesas) (Representative) (Voting) | ||
| + | * Wolfgang Mauerer (Siemens) (Representative) (Voting) | ||
| * Dinesh Kumar (Toshiba India) | * Dinesh Kumar (Toshiba India) | ||
| - | * Daniel Sangorrin (Toshiba) | ||
| * Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair | * Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair | ||
| + | * | ||
| ===== Discussions ===== | ===== Discussions ===== | ||
| Line 22: | Line 23: | ||
| ==== Action items status update ==== | ==== Action items status update ==== | ||
| + | * AI(Yoshi): Send slide PPT file to SZ (Done) | ||
| * Reproducible builds | * Reproducible builds | ||
| - | * See below | + | * Had CIP GB meeting. |
| * Kernel development for next CIP kernel | * Kernel development for next CIP kernel | ||
| * (On going) MOXA: Send the board support package to upstream | * (On going) MOXA: Send the board support package to upstream | ||
| Line 29: | Line 31: | ||
| * Spectre/Meltdown | * Spectre/Meltdown | ||
| * Arm vulnerability list: [[https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability|https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability]] | * Arm vulnerability list: [[https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability|https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability]] | ||
| - | * AI: tidy up this information | + | * Renesas wants to backport Spectre/Meltdown mitigations on 4.4.y |
| - | * Discussion with partners internally | + | * Spectre variant 1 |
| - | * May be in the next meeting | + | * For x86 only backport 2nd wave of patches |
| + | * Many drivers still need to be fixed | ||
| + | * Spectre variant 2 | ||
| + | * No patches available for ARM | ||
| + | * Meltdown (variant 3/3a) for ARM | ||
| + | * Only required for Cortex-a75/72/57/15 (RZ/G1) | ||
| + | * Spectre variant 4 | ||
| + | * No patches available for ARM | ||
| + | * AI: tidy up this information | ||
| + | * Status: Investigating. Can be comment soon. (7/23) | ||
| + | * Cybertrust is interested in this issue. | ||
| + | * Planning to provide first revision of patch. | ||
| + | * Not sure on timescales yet though. | ||
| + | * Patches would need to be ported from upstream to LTS v4.4. | ||
| + | * Status: nothing to report at this moment. (7/23) | ||
| * Kernel maintainer | * Kernel maintainer | ||
| - | * AI(Yoshi): Arrange a F2F meeting at DebConf with Ben, Wolfgang, Iwamatsu-san. (DONE) | + | * Cybertrust: AI(CTJ) Check possible options for kernel maintenance |
| + | * CTJ answered to CIP | ||
| + | * Iwamatsu-san will be CIP kernel maintainer (20% to Sep, 40% from Oct.). | ||
| + | * Others? | ||
| + | * Renesas | ||
| + | * Katayama-san | ||
| + | * If CIP itself has maintainer from CTJ, it is good situation. | ||
| + | * Maintainer should be one person. | ||
| + | * Chris | ||
| + | * While Greg is maintaining 4.4, CIP need to have only one maintainer. | ||
| + | * One maintainer and CIP kernel team will be enough. | ||
| + | * Cybertrust: Iwamatsu | ||
| + | * Considering the maintenance system, I think that one person is better. | ||
| + | * Siemens: Wolfgang | ||
| + | * We should urgently follow up with Bootlin, they replied swiftly and their experience as a team would be a valuable asset for CIP. Since rather more than less will come to our kernel plate, we think having two paid maintainers would be justified. We should also clarify at the earliest possible moment (ideally DebConf) if we can align the next CIP kernel with Debian-LTS, and if BenH can take over maintenance in this case. | ||
| + | * Toshiba: Yoshi | ||
| + | * IMHO, Bootlin has experienced kernel maintainers. We should consider much deeply what is the best way. I will also ask Ben, what does he think. | ||
| + | * Agustin: Having as many as maintainer is good choice. But initially having one maintainer is enough. Bit worried if they don’t know each other. | ||
| + | * Multi maintainer approach will be good if they know each other. | ||
| + | * AI(Yoshi): Arrange a F2F meeting at DebConf with Ben, Wolfgang, Iwamatsu-san. | ||
| * CIP Core package list | * CIP Core package list | ||
| * AI(Daniel.S): Send to public mail list to get feedback from Ben. (DONE) | * AI(Daniel.S): Send to public mail list to get feedback from Ben. (DONE) | ||
| * [cip-dev] [CIP Core] Criteria for prioritizing security fixes in Debian LTS | * [cip-dev] [CIP Core] Criteria for prioritizing security fixes in Debian LTS | ||
| - | * [[https://lists.cip-project.org/pipermail/cip-dev/2018-July/001398.html|https://lists.cip-project.org/pipermail/cip-dev/2018-July/001398.htm]] | + | * [[https://lists.cip-project.org/pipermail/cip-dev/2018-July/001398.html|https://lists.cip-project.org/pipermail/cip-dev/2018-July/001398.html]] |
| - | * Already submitted to Reproducible builds | + | |
| * Agustin sent the link to the spreadsheet and the internal thread about the topic to Ben H. so he can get some background. | * Agustin sent the link to the spreadsheet and the internal thread about the topic to Ben H. so he can get some background. | ||
| - | * DebConf: DONE | + | * DebConf |
| - | * WhitePaper | + | * AI(LF): Send booth materials to DebConf (Table cover and roll stand). |
| - | * Still not available | + | * Table cover was sent, please ask front desk to pick up it. |
| + | * Unable to find the roll-up screen, sigh… | ||
| + | * Giveaways: CIP LEGO (They will go with Kazu) | ||
| + | * Whitepaper (finalized?) | ||
| + | * Submitted long one. | ||
| + | * AI(LF/TSC): make sure when it is ready. | ||
| + | * AI(Yoshi): Ask to LF Japan to find the old one. | ||
| + | * ELC-E | ||
| + | * AI: Yoshi: Submit a talk to ELC-E | ||
| + | * Under review process. | ||
| + | * | ||
| - | ==== Spectre/Meltdown mitigation for CIP kernel ==== | ||
| - | * See above | + | |
| + | * | ||
| ==== CIP Core packages ==== | ==== CIP Core packages ==== | ||
| Line 59: | Line 103: | ||
| * AI(Daniel.S): Send to public mail list to get feedback. (DONE) | * AI(Daniel.S): Send to public mail list to get feedback. (DONE) | ||
| * (On going. See above) | * (On going. See above) | ||
| - | * Comments | + | * Criteria for prioritizing security fixes: |
| - | * LTS: We should send package list with source packages | + | - Member package list |
| - | * AI(Daniel S.): Ask to Raphael for the package list format. | + | - CVEs with high "base score", high "impact score", high "exploitability score", and low "attack complexity" |
| - | * Initial reference implementation with meta-debian however, we need to decide if we are going to use other build system (e.g. ISAR) for reference implementation and include more packages in the base layer. | + | - Network software (CVEs with "Access Vector (AV): Network") |
| + | - Security software | ||
| + | - Language runtimes/compilers | ||
| + | |||
| + | ==== DebConf ==== | ||
| + | |||
| + | * Ben H. sent a list of activities to follow or participate on. | ||
| + | * Who will attend? The last day to confirm attendance is 6/21 | ||
| + | * Ben, Wolfgang, SZ, Nobu, Kazu and Yoshi | ||
| + | * Booth Openday should be managed by SZ, Nobu, Kazu | ||
| + | * Job fair will be held 28th July(Sat). | ||
| + | * Kazu and Nobu (and maybe SZ) | ||
| + | * AI(Yoshi) ask to them to run the booth. | ||
| + | * CIP will have a booth. | ||
| + | * Address for shipping items to DebConf: | ||
| - | ==== CIP kernel team ==== | + | AnHui Lee, Microelectronics and Information Research Center, |
| + | National Chiao Tung University | ||
| + | No.1001, University Rd., East Dist., Hsinchu City 300, Taiwan (R.O.C.) | ||
| + | +886-3-5712121*31944 | ||
| - | * Discussed at DebConf to decide the structure of CIP kernel team | + | ==== AI(LF): Send booth materials to DebConf (Table cover and roll stand). ==== |
| - | * CIP kernel team will focus both 4.4 and next CIP (4.20 or 5.0) | + | |
| - | * CIP kernel team will structured with | + | |
| - | * 1 mentor (Ben H.) | + | |
| - | * 2 maintainers for CIP kernel (Iwamatsu-san), 1 maintainer for CIP-RT (Daniel. W) | + | |
| - | * Other members from each company such as MOXA and Toshiba (Daniel S.) | + | |
| - | * AI(Kernel team members): Define milestone for next CIP kernel | + | |
| - | * Kernel configuration | + | |
| - | * Initial blacklist has already prepared by Ben | + | |
| - | * RT will be clarified by Daniel W. | + | |
| - | * Config vs. Board | + | |
| - | * To be discussed | + | |
| - | * AI(Wolfgang): Contact to Daniel W. to become next CIP-RT maintainer | + | |
| - | * AI(SZ): Ask to have weekly kernel team meeting at 5pm(JST) (Need to check time for other timezones) | + | |
| - | US-West US-East UK DE TW JP | + | |
| - | 01:00 04:00 09:00 10:00 16:00 17:00 | + | |
| ==== Kernel maintenance and testing ==== | ==== Kernel maintenance and testing ==== | ||
| Line 87: | Line 133: | ||
| === Kernel maintenance === | === Kernel maintenance === | ||
| - | * Nothing out of DebConf 2018 | + | * Latest ARM patchets reviewed and merged. |
| + | * V2 for some specific patches will need to be sent for review. | ||
| + | * | ||
| ==== CIP Testing ==== | ==== CIP Testing ==== | ||
| - | * Containerization of B@D in progress. | + | * Latest CIP kernel tested on BBB with B@D (limited) |
| + | * The work to move B@D away from VM and into containers has started. | ||
| + | * Older entries | ||
| + | * CIP decide to move to centralized environment | ||
| + | * Distributed LAVA server/lab status | ||
| + | * Test case creation/contribution | ||
| + | * Next steps | ||
| + | * Setup KernelCI instance in centralized server | ||
| + | * Put test results to KernelCI | ||
| + | * Does any member already set up LAVA internally? | ||
| + | * Moxa has jenkins/ LAVA testing system internally, Moxa can share it when it’s stable enough. | ||
| + | * Renesas planning to setup a LAVA Lab to link to CIP LAVA master/KernelCI. | ||
| + | * | ||
| ==== EdgeX/CIP Core ==== | ==== EdgeX/CIP Core ==== | ||
| Line 97: | Line 157: | ||
| * Trying to run Docker on CIP Core. | * Trying to run Docker on CIP Core. | ||
| * (Yoshi) Toshiba has an experience to install it but not sure for me how to do it. ;( | * (Yoshi) Toshiba has an experience to install it but not sure for me how to do it. ;( | ||
| - | * Success to run Docker with CIP Core | ||
| - | * Next: Try to run EdgeX demo on the filesystem | ||
civilinfrastructureplatform/tsc-meetings/tsc_mm_jul232018.txt · Last modified: 2018/09/20 15:59 by yoshi
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
