13:03:41 <jki> #startmeeting CIP IRC weekly meeting 13:03:41 <brlogger> Meeting started Thu Nov 4 13:03:41 2021 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:03:41 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:03:41 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting' 13:03:51 <jki> Hi everyone! 13:03:56 <alicef> o/ 13:03:57 <uli> hello 13:04:02 <masami> hi 13:04:08 <josiah> Hi 13:04:29 <patersonc[m]> Hi 13:04:32 <iwamatsu> hi 13:05:53 <jki> just pavel missing, but let's get started already 13:05:56 <jki> #topic AI review 13:06:03 <jki> 1. Combine root filesystem with kselftest binary - iwamatsu & alicef 13:07:00 <alicef> I updated the isar-cip-core pull request and now I'm creating core-image-kernelci images 13:07:27 <alicef> core-image-kernelci image are image made ad-hoc for kernelci from isar-cip-core 13:07:46 <jki> uh, PR on gitlab? I'm not following that channel apparently 13:07:55 <alicef> the login worked correctly without password 13:08:34 <alicef> PR not yet sended as I'm finishing to add the last changes for making it compatible with KernelCI 13:08:40 <jki> ah, ok 13:08:45 <alicef> but I will send it today or tomorrow 13:09:17 <alicef> here there is a example of the image working with lava with same settings of kernelci https://lava.ciplatform.org/scheduler/job/507389 n 13:09:38 <alicef> and here is where the image are pushed to https://storage.staging.kernelci.org/images/rootfs/cip/ 13:10:11 <alicef> the name is "cip-core-image-kernelci-cip-core-buster-qemu-<arch>-initrd.img.gz" 13:10:41 <jki> great! is kselftest in that image already executed? 13:10:46 <alicef> the code is here https://gitlab.com/cip-project/cip-core/isar-cip-core/-/tree/alicef/kernelci_image/recipes-core 13:10:57 <alicef> if anyone is interested 13:11:16 <alicef> Kselftest is not yet implemented 13:11:41 <alicef> I didn't test it yet with kselftest 13:11:46 <jki> fine, one after the other 13:12:16 <alicef> that's all from me 13:13:11 <jki> good. please send the patches ideally via the ML, to stay consistent with other contributions 13:13:29 <alicef> I'm now working on the script reading dmesg that kernelci is using 13:13:43 <alicef> ok 13:14:38 <jki> 2. Look into S3 artifact upload issues - patersonc 13:15:07 <patersonc[m]> No updates 13:15:25 <jki> 3. Update 5.10-cip branch - iwamatsu & pavel 13:15:48 <iwamatsu> I updated 5.10-cip branch 13:16:05 <jki> perfect 13:16:19 <jki> 4. Propose review coordination workflow with gitlab snippets - iwamatsu 13:16:26 <jki> na, wrong 13:16:28 <iwamatsu> Currentry, this branch had been merged with 5.10.75. 13:16:39 <jki> 4. Propose review coordination workflow via wiki - iwamatsu 13:17:17 <iwamatsu> OK, I invistigated about this. 13:17:36 <iwamatsu> We can create wikis via API as well as snippets. 13:18:02 <iwamatsu> We can create it on linux-cip's wiki, and we can specify the kernel version for the name of the wiki. 13:18:05 <iwamatsu> https://gitlab.com/-/snippets/2200569 13:18:26 <iwamatsu> We can also use namespaces for wiki, so we can create hierarchies such as 5.10.y/v5.10.77. 13:18:39 <iwamatsu> e.g. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/wikis/5.10.y/v5.10.77 13:19:08 <iwamatsu> These data are managed in one Git repository. 13:19:41 <iwamatsu> For example, linux-cip's wiki can clone following command: 13:19:44 <iwamatsu> git clone git@gitlab.com:cip-project/cip-kernel/linux-cip.wiki.git 13:19:59 <iwamatsu> and can push. 13:20:20 <iwamatsu> I think the wiki easier to use than the snippet. 13:20:38 <iwamatsu> that's all from me. 13:21:38 <jki> so the wiki pages would be filled with the commits first - likely automatable - and then CIP devs would put their names behind commits they plan to review? 13:22:20 <iwamatsu> yes 13:23:13 <jki> anyone any concerns about such a process? 13:23:20 <uli> sounds good to me 13:23:59 <iwamatsu> We can also automate to mark commits in other trees. 13:25:05 <jki> iwamatsu: could you drop an email to the list, briefly describing this, so that pavel can comment on it as well? 13:25:10 <iwamatsu> The review method will be the same as it is now, I think. Only a small change in repository and format. 13:25:36 <iwamatsu> jki: sure. 13:25:55 <jki> TIA! 13:26:15 <jki> good, anything else regarding AIs? 13:26:34 <jki> 3 13:26:37 <jki> 2 13:26:39 <jki> 1 13:26:42 <jki> #topic Kernel maintenance updates 13:26:58 <uli> i'm reviewing 5.10.77 13:27:13 <iwamatsu> I am reviewing 5.10.77. 13:27:17 <masami> There is 4 new CVEs this week. 13:27:20 <masami> CVE-2021-3892 causes a DoS attack. It seems that hasn't been not fixed in any tree. 13:27:38 <masami> Other CVEs are already fixed. 13:29:05 <masami> I have a question. 13:29:21 <jki> go ahead 13:29:39 <masami> We got a new issue on cip-kernel-sec repo. https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec/-/issues/9 13:30:20 <masami> AOSP android-3.18 branch has been deprecated since this November so we don't have to track it 13:30:53 <masami> This issue has link a patch to remove the branch to track. 13:31:05 <masami> May I pick up the patch and merge it? 13:31:12 <iwamatsu> yeah, please apply this MR. 13:31:37 <masami> iwamath: thanks! I'll apply it. 13:32:02 <jki> that is a cip-external contributor, right? just out of curiosity 13:32:17 <masami> iwamatsu: thanks. 13:32:48 <masami> jki: I think so. 13:33:30 <jki> nice to see folks following us that closely, and suggesting improvements 13:33:51 <jki> anything else for this topic? 13:33:52 <patersonc[m]> Should MRs be enabled? 13:34:14 <masami> jki: yeah! it is good thing. 13:34:33 <jki> hmm, shouldn't we do patch-based reviews in general? maybe state this somewhere? 13:34:42 <iwamatsu> And we need to drop AOSP from conf/remotes.yml 13:34:58 <patersonc[m]> Or use a newer version of AOSP? 13:35:50 <iwamatsu> That is also good. 13:36:48 <masami> tracking 4.19 instead of 3.18? 13:37:40 <iwamatsu> That is also good./ 13:37:47 <iwamatsu> android-4.x-p ? 13:38:32 <iwamatsu> android 12 uses 5.10 (android12-5.10-lts) 13:38:51 <iwamatsu> https://android.googlesource.com/kernel/common.git/+refs 13:40:24 <masami> How about add android-4.4-p, android-4.19-q, and android12-5.10. 13:40:53 <iwamatsu> Or other Android trees use LTS kernel, so it may not make much sense. 13:42:09 <masami> I see 13:42:54 <iwamatsu> and these android tree managed by Greg. 13:43:21 <iwamatsu> s/managed/ are managing/ 13:45:10 <iwamatsu> I think the Android tree syncs regularly so I don't think we need to check it. 13:45:48 <masami> iwamatsu: I got it 13:46:57 <jki> how to continue with that? further discussion? AI for iwamatsu to propose a patch? 13:48:31 <iwamatsu> OK, I will create a patch 13:48:59 <jki> thanks! 13:49:10 <jki> anything else? 13:49:20 <jki> 3 13:49:23 <jki> 2 13:49:25 <jki> 1 13:49:29 <jki> #topic Kernel testing 13:49:39 <patersonc[m]> o/ 13:49:48 <patersonc[m]> The LAVA master had a wobble over the weekend 13:49:54 <patersonc[m]> All up and running again now though 13:49:57 <patersonc[m]> Sorry for the downtime 13:50:10 <jki> daylight saving issue? ;) 13:50:13 <patersonc[m]> Ha 13:50:44 <patersonc[m]> I think it ran out of storage, which killed LAVA. But when I logged on there was plenty of available storage... 13:51:04 <alicef> patersonc[m]: thanks :) 13:51:26 <patersonc[m]> That's pretty much all I have this week 13:51:34 <patersonc[m]> Anything else from you alicef-san? 13:52:11 <alicef> I'm also ok. I already exausted all my topics for this week 13:52:30 <patersonc[m]> Happy days 13:52:40 <alicef> you too! 13:53:13 <jki> then move on? 13:53:15 <jki> 3 13:53:18 <jki> 2 13:53:20 <jki> 1 13:53:23 <jki> #topic AOB 13:53:58 <jki> anyone anything? 13:54:35 <jki> 3 13:54:38 <jki> 2 13:54:41 <jki> 1 13:54:44 <jki> #endmeeting