13:02:10 <jki> #startmeeting CIP IRC weekly meeting 13:02:10 <brlogger_> Meeting started Thu Sep 9 13:02:10 2021 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:10 <brlogger_> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:10 <brlogger_> The meeting name has been set to 'cip_irc_weekly_meeting' 13:02:22 <jki> #topic rollcall 13:02:26 <pave1> hi 13:02:27 <jki> hi everyone 13:02:30 <uli> hi 13:02:31 <alicef> o/ 13:02:33 <masami> hi 13:02:35 <josiah|2> Hi 13:03:00 <jki> great, almost full-house 13:03:11 <jki> is chris going to join? 13:03:16 <patersonc[m]> hi 13:03:33 <jki> perfect 13:03:48 <jki> anyone missing? 13:04:09 <jki> iwamatsu 13:05:44 <jki> well, let's start nevertheless I would say 13:05:50 <pave1> Yep :-). 13:05:51 <jki> #topic AI review 13:06:08 <jki> 1. Combine root filesystem with kselftest binary - iwamatsu & alicef 13:06:13 <jki> any news? 13:06:31 <patersonc[m]> I don't think so 13:06:38 <alicef> Investigating on how to expand the cip-core for make kselftest work on the user space 13:07:15 <alicef> expand cip-core space 13:07:20 <jki> ok - i know it's being used already, I suppose you saw the recipe 13:07:30 <alicef> yes 13:07:47 <jki> but I don't have details either -> maybe contact our mentor colleagues 13:08:02 <jki> e.g. via isar ML 13:08:13 <alicef> yes 13:08:44 <jki> good 13:08:58 <jki> any new AIs? 13:09:52 <jki> I think I forgot one from last week: 13:09:58 <jki> Add lava URLs to wiki page 13:10:47 <jki> patersonc: think you wanted to check that, right? 13:12:14 <patersonc[m]> I can't remember the details for this 13:13:02 <jki> kernelci.ciplatform.org and cip.kernelci.org: add to wiki once ready 13:13:26 <alicef> jki: cip.kernelci.org is already ready 13:13:43 <patersonc[m]> Ah okay 13:13:44 <patersonc[m]> Thanks 13:13:44 <patersonc[m]> I'll get that done 13:14:00 <jki> TIA! 13:14:07 <jki> other AIs? 13:14:19 <jki> 3 13:14:23 <jki> 2 13:14:28 <jki> 1 13:14:41 <jki> #topic Kernel maintenance updates 13:15:07 <pave1> I have reviewed patches queued for 5.10.62/63/64. 13:15:19 <uli> fixed a couple of minor issues in the scripts in cip-kernel-config and lts-commit-list 13:15:32 <masami> There is 3 new CVEs in this week. 13:15:40 <masami> CVE-2021-3715, CVE-2021-3759, CVE-2021-40490 are new CVEs. 13:15:45 <masami> These CVEs have been fixed in the mainline and some stable kernels. 13:16:52 <masami> CVE-2021-3739, CVE-2021-3743, CVE-2021-3753, CVE-2021-38198, CVE-2021-3444, CVE-2021-3600 have updated. 13:16:57 <masami> They have been fixed in the mainline and some stable kernels. 13:18:11 <jki> also for all our CIP kernel versions? 13:18:33 <jki> or how do those report map on our kernels generally? 13:19:15 <masami> jki: not all cip kernels are fixed. 13:19:42 <pave1> jki: We don't have to do anything this week. 13:19:47 <jki> ok 13:20:03 <pave1> jki: CVE-2021-3759: is missing cgroup accounting -- DoS only if you have shell. 13:20:04 <jki> still learning the meanings ;) 13:20:17 <masami> jik: This report is based on mainline and stable kernels. 13:21:02 <pave1> CVE-2021-38198: is KVM nastyness. It is unclear if we want to track this one. Anyway someone backported it to 4.14, so things are improving. 13:21:59 <jki> ok - move on? 13:22:20 <pave1> 3 13:22:21 <pave1> 2 13:22:22 <pave1> 1 13:22:23 <pave1> :-) 13:22:25 <jki> #topic Kernel testing 13:23:06 <alicef> cip KernelCI production can now be seen at https://cip.kernelci.org 13:23:14 <patersonc[m]> We've been working on various topics for the KernelCI kackfest 13:23:15 <patersonc[m]> hackfest 13:23:18 <alicef> smc (spectre meltdown check) 13:23:20 <alicef> got merged and is now working on production 13:23:23 <alicef> example: https://linux.kernelci.org/test/plan/id/6138e379ab9d472d1ad596a8/ 13:23:37 <alicef> currently some cip configuration are used on staging kernelci (currently only for qemu arm and x86-64) 13:23:38 <alicef> configuration are from https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/ 13:24:27 <alicef> patersonc[m] and I are currently fixing the kernelci pages links about and reference about CIP 13:25:22 <alicef> like https://static.staging.kernelci.org/docs/org/tsc/#cip-instance and https://static.staging.kernelci.org/docs/instances/ 13:25:40 <jki> nice 13:26:03 <alicef> currently I'm working with the help of patersonc[m] on making kernelci work with the isar-cip-core images 13:26:38 <alicef> also I'm adding iec-security-tests as kernelci test 13:26:38 <jki> ok - i think / hope the preconditions are fulfilled 13:26:59 <jki> like being able to generate to right images (tarballs etc.) 13:27:13 <alicef> that is what I'm working on yes 13:27:49 <jki> if something should be missing, we have other isar layers generating for lava, e.g. https://gitlab.denx.de/Xenomai/xenomai-images 13:28:08 <alicef> mmm ? 13:28:36 <alicef> if something is missing we cannot just add it to the isar-cip-core ? 13:28:51 <jki> yes, sure 13:29:08 <jki> that link was just another source of inspiration 13:29:13 <alicef> I didn't know about xenomai-core 13:29:32 <jki> or ask on the list, we could help so that you don't need to learn isar first 13:29:39 <jki> and isar-cip-core 13:29:52 <alicef> currently I'm making the script for deploying the images to kernelci fileserver 13:29:59 <alicef> using the kernelci api 13:30:18 <jki> ok, that is surely specific 13:30:21 <alicef> jki: thanks that would be helpful 13:31:01 <jki> drop an email with question, my colleague Quirin can likely help as well (he did that for xenomai) 13:31:29 <alicef> creating tarball ? 13:31:48 <jki> including that, yes 13:32:08 <alicef> yes ok 13:32:39 <jki> kas[-container] build ...:kas/opt/targz-img.yml 13:32:57 <alicef> there are no other updates for me 13:33:06 <alicef> yes 13:33:21 <jki> ok - anything else for this topic? 13:33:26 <alicef> on isar just need to be enabled from .gitlab-ci 13:33:35 <alicef> not at the moment 13:33:49 <jki> #topic AOB 13:34:03 <uli> one thing 13:34:16 <uli> i'm a "developer" member of all projects on gitlab now, but the master branches of cip-kernel-config and lts-commit-list are set to "protected" 13:34:25 <uli> apparently that means i need extra-special permissions to push there 13:34:32 <uli> who do i bother about that? 13:34:48 <pave1> You definitely need permissons for lts-commit-list. 13:35:47 <jki> handling that 13:35:56 <uli> ok, thanks 13:36:03 <jki> how is cip-kernel-config maintained so far? 13:36:12 <jki> multi-maintainer? MRs? 13:36:15 <pave1> iwamatsu is marked a 13:36:18 <pave1> as a maintainer. 13:36:31 <jki> so he will merge to master? 13:36:58 <pave1> I believe I have committed directly to it, but he's the one responsible... 13:37:54 <jki> then let's clarify this with him 13:38:03 <jki> maybe write him an email, uli? 13:38:09 <uli> can do 13:38:43 <pave1> I believe Ulrich should get access there (same as lts-commit-list), but in this case it might be polite to ask before commiting. 13:39:01 <jki> right 13:39:12 <jki> lts-commit-list already done now 13:39:19 <uli> thx 13:39:30 <jki> good, any other access issues to clarify? 13:39:37 <uli> not from me 13:40:04 <jki> or other AOBs? 13:40:07 <pave1> We should probably create shared whiteboard somewhere to coordinate patch reviews. 13:40:31 <pave1> Not sure if git is suitable for that... 13:40:48 <pave1> Ideally something that can be easily scripted... 13:41:09 <pave1> If someone has quick idea, speak now, otherwise I'll write email to the list. 13:41:14 <jki> would issue tracking work (with email feeding)? 13:41:31 <pave1> I think I'd avoid email for this. 13:42:06 <pave1> I was thinking more like wiki page. We don't really need history, we just need shared place where people can write to easily. 13:42:44 <jki> wiki is generally with history... 13:43:07 <pave1> jki: I know. I guess we can live with history but don't need it. 13:43:33 <jki> ...and is actually in git, if using one from gitlab.com 13:43:48 <jki> but maybe start with describing the workflows you have in mind 13:43:59 <pave1> Ok, lets do that over email? 13:44:04 <jki> fine for me 13:44:49 <jki> anything else for today? 13:45:24 <jki> 3 13:45:27 <jki> 2 13:45:30 <jki> 1 13:45:41 <jki> thank you all, have a nice day! 13:45:47 <jki> #endmeeting