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