| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:26 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has joined #cip | 11:02 | |
| *** masami <masami!~masami@fl1-122-133-108-128.tky.mesh.ad.jp> has joined #cip | 12:02 | |
| *** josiah|2 <josiah|2!~kvirc@pool-71-179-201-175.bltmmd.fios.verizon.net> has joined #cip | 12:50 | |
| *** jki <jki!~jki@88.215.84.132> has joined #cip | 12:54 | |
| *** iwamatsu_ <iwamatsu_!~iwamatsu@2405:6581:5360:1800:bf52:1f8e:88d2:6ec> has joined #cip | 12:56 | |
| *** uli <uli!~uli@55d434d5.access.ecotel.net> has joined #cip | 13:01 | |
| jki | #startmeeting CIP IRC weekly meeting | 13:01 |
|---|---|---|
| brlogger | Meeting started Thu Sep 16 13:01:37 2021 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:01 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:01 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | #topic rollcall | 13:01 |
| *** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | hi all! | 13:01 |
| iwamatsu_ | hi! | 13:01 |
| uli | hi | 13:02 |
| alicef | hi | 13:02 |
| masami | hi | 13:02 |
| josiah|2 | hi | 13:02 |
| jki | so, pavel is on the road - chris is missing? | 13:03 |
| jki | but let's start nevertheless | 13:04 |
| jki | #topic AI review | 13:04 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:04 | |
| jki | 1. Combine root filesystem with kselftest binary - iwamatsu & alicef | 13:04 |
| alicef | no updates | 13:04 |
| iwamatsu_ | no update from me. | 13:04 |
| jki | keep it as AI? | 13:05 |
| alicef | ? | 13:05 |
| alicef | you mean merge this in the IA topic ? | 13:06 |
| alicef | AI | 13:06 |
| jki | i mean does this remain an AI for us, just one that will take more time? | 13:06 |
| alicef | what is AI ? | 13:07 |
| jki | Action Item | 13:07 |
| jki | and something we should revisit on every meeting - at least my understanding of this | 13:07 |
| alicef | yes last week was KernelCI hackfest and I worked at the merge of CIP testing with KernelCI | 13:08 |
| jki | then we actually have news here, great | 13:08 |
| alicef | that's why there are no updates on the this | 13:08 |
| jki | ah, ok, this will build on top | 13:08 |
| jki | ok, next | 13:09 |
| jki | 2. Document new LAVA domains in wiki - patersonc | 13:09 |
| alicef | sorry I got a regression on upstream kernels and I have to keep a eye also there | 13:10 |
| jki | no problem! | 13:10 |
| jki | ok, wiki not yet updated | 13:10 |
| jki | any new AIs we should add here? | 13:11 |
| jki | 3 | 13:12 |
| jki | 2 | 13:12 |
| jki | 1 | 13:12 |
| jki | #topic Kernel maintenance updates | 13:12 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:12 | |
| iwamatsu_ | I reviewed 4.4.284-rc, 5.10.64 and 65. | 13:12 |
| uli | reviewing for 5.10.65 | 13:13 |
| masami | I have CVE summary. There is 4 new CVEs in this week. | 13:13 |
| masami | CVE-2021-3744, CVE-2021-3764, CVE-2021-3752, CVE-2021-38300 are new CVEs. | 13:13 |
| jki | question for my understanding: when you review and do not find anything, is that recorded somewhere as well? | 13:14 |
| iwamatsu_ | We managed it to lts-commit-list repo. | 13:16 |
| iwamatsu_ | https://gitlab.com/cip-project/cip-kernel/lts-commit-list | 13:16 |
| jki | so, upstream lts does not take extra review-by tags, does it? | 13:16 |
| iwamatsu_ | That is not done for each commit. | 13:17 |
| jki | ok, but we have at least our records, good | 13:18 |
| iwamatsu_ | If there is a problem, we will comment on the patch. For example, this requires additional patches. | 13:19 |
| jki | sure, that I expected - provided you are fast enough for Greg | 13:19 |
| jki | anything else for this topic block? | 13:20 |
| jki | 3 | 13:21 |
| jki | 2 | 13:21 |
| jki | 1 | 13:21 |
| jki | #topic Kernel testing | 13:21 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:21 | |
| jki | according to Chris (just found his email), no news here | 13:21 |
| alicef | sorry I'm masking gentoo kernels for a posix cpu regression | 13:21 |
| alicef | anyway we had hackfest kernelci last week | 13:22 |
| jki | ok | 13:22 |
| alicef | I think we had updates on the CIP tsc about it from chris | 13:22 |
| jki | right | 13:22 |
| jki | that was what he meant | 13:22 |
| alicef | we recently had merged the cip configurations pull request on kernelci | 13:22 |
| alicef | is working only for 4.19 at the moment and in qemu | 13:23 |
| alicef | not yet filtered it to each board | 13:24 |
| alicef | but still we have something working with the cip configurations | 13:24 |
| jki | that's good, indeed | 13:24 |
| alicef | the efforts on the iec cybersecurity test and cip core are going on | 13:25 |
| alicef | This is one example https://staging.kernelci.org/build/id/6137240c428e1b1b5136a8f5/ | 13:26 |
| alicef | working with cip://4.19.y-cip/arm64/qemu_arm64_defconfig | 13:26 |
| alicef | that is a configurtion taken from https://gitlab.com/cip-project/cip-kernel/cip-kernel-config | 13:26 |
| jki | that was built by kernelci, not via isar-cip-core, right? | 13:27 |
| alicef | affermative | 13:27 |
| alicef | we are pushing cip-core to the kernelci fileserver | 13:27 |
| alicef | by the kernelci api | 13:28 |
| alicef | but we are not yet using it | 13:28 |
| alicef | I'm fixing kernelci for make it work with cip-core tarball | 13:28 |
| alicef | you can get it from here https://storage.staging.kernelci.org/images/rootfs/cip/ | 13:28 |
| alicef | https://storage.staging.kernelci.org/images/rootfs/cip/20210910/ | 13:29 |
| jki | ok | 13:29 |
| alicef | sorry need to go back masking gentoo kernels packages | 13:30 |
| alicef | that's all for me | 13:30 |
| jki | thanks a lot! | 13:30 |
| jki | then let's move on | 13:30 |
| jki | #topic AOB | 13:30 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:30 | |
| jki | I have one: will be OOO the next two weeks | 13:31 |
| alicef | ah one thing | 13:31 |
| jki | can anyone take over? | 13:31 |
| alicef | sorry | 13:31 |
| jki | go ahead | 13:32 |
| alicef | kernelci is writing the blog about the hackfest #2 https://static.staging.kernelci.org/blog/posts/2021/hackfests/ | 13:32 |
| alicef | if someone is interested on the work done during KernelCI hackfest and it also reference to CIP | 13:32 |
| jki | that's nice | 13:33 |
| jki | Chris should drop a note on that on next TSC call as well | 13:33 |
| alicef | sorry for the interruption please go on | 13:33 |
| jki | ok, I need a deputy to run the next two irc meetings | 13:34 |
| iwamatsu_ | OK, I can takeover. | 13:35 |
| jki | that would be great - TIA! | 13:36 |
| iwamatsu_ | but I do not know how to use meeting tool. | 13:36 |
| jki | I can drop you the notes kudo-san shared with me | 13:36 |
| iwamatsu_ | ok, thanks! | 13:37 |
| jki | it's just a few magic markers to feed the logging bot | 13:37 |
| jki | anything else for AOB? | 13:38 |
| jki | everyone with sufficient access by now? | 13:38 |
| masami | I have one | 13:38 |
| jki | go ahead | 13:38 |
| masami | ok. I was asked about CVSS score last week | 13:38 |
| masami | so, is it helpful if CVSS score is in the CVE report? to know CVE's severity | 13:38 |
| jki | I suppose we would have two consumer groups here: us as kernel maintainers and then our users | 13:39 |
| jki | who do you have in mind to benifit from this score? | 13:40 |
| masami | jki: cip kernel users will have benefit | 13:41 |
| masami | it easy to understand CVE's impact | 13:41 |
| jki | ok. how much extra effort this would mean when adding it? | 13:42 |
| masami | it needs a bit extra work. but easy task. | 13:44 |
| jki | just initially extra work, or also on each CVE? | 13:45 |
| masami | I think adding CVSS score to weekly report, so usually initially extra work. | 13:47 |
| jki | otherwise, it sounds like a good proposal to me at least | 13:47 |
| jki | other thoughts on this? | 13:47 |
| masami | thanks! | 13:48 |
| jki | thanks for your initiative! | 13:49 |
| jki | anything else for today? | 13:49 |
| jki | 3 | 13:50 |
| jki | 2 | 13:50 |
| jki | 1 | 13:50 |
| jki | thank you all, and enjoy the rest of today! | 13:50 |
| jki | #endmeeting | 13:50 |
| brlogger | Meeting ended Thu Sep 16 13:50:39 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:50 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2021/09/cip.2021-09-16-13.01.html | 13:50 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/09/cip.2021-09-16-13.01.txt | 13:50 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2021/09/cip.2021-09-16-13.01.log.html | 13:50 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 13:50 | |
| masami | bye! | 13:51 |
| uli | bye | 13:51 |
| iwamatsu_ | Thank you! | 13:51 |
| jki | bye! | 13:51 |
| alicef | bye | 13:56 |
| *** uli <uli!~uli@55d434d5.access.ecotel.net> has left #cip | 13:57 | |
| *** jki <jki!~jki@88.215.84.132> has quit IRC | 14:04 | |
| *** josiah|2 <josiah|2!~kvirc@pool-71-179-201-175.bltmmd.fios.verizon.net> has quit IRC | 15:08 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has quit IRC | 18:01 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 21:59 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!