09:00:19 <masashi910> #startmeeting CIP IRC weekly meeting
09:00:19 <brlogger`> Meeting started Thu Jun 18 09:00:19 2020 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:19 <brlogger`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:19 <brlogger`> The meeting name has been set to 'cip_irc_weekly_meeting'
09:00:27 <masashi910> #topic rollcall
09:00:37 <masashi910> please say hi if you're around
09:00:46 <patersonc> Hello
09:00:59 <fujita3> hi
09:01:00 <suzuki> hi
09:01:09 <paveltest> HI
09:01:13 <masashi910> #topic AI review
09:01:19 <masashi910> 1. Combine root filesystem with kselftest binary - iwamatsu
09:01:26 <masashi910> Quote from Iwamatsu-san "No update."
09:01:30 <wens> hi
09:01:33 <masashi910> 2. Post LTP results to KernelCI - patersonc
09:01:53 <patersonc> Probably won't get to this for a few weeks
09:02:32 <masashi910> patersonc: OK. Do you think we can keep this AI for the time being?
09:03:22 <patersonc> I don't mind. I've got it tracked elsewhere anyway
09:03:41 <masashi910> patersonc: OK. Then I will keep it.
09:03:45 <masashi910> 3. Ask board owners to review reference platform configs to optimize backporting - masashi910
09:03:54 <masashi910> I sent the following email to cip-dev. Due date is June 25th.
09:04:00 <masashi910> https://lore.kernel.org/cip-dev/TY2PR01MB497253E7217AED2CA0952E47A0850@TY2PR01MB4972.jpnprd01.prod.outlook.com/
09:04:08 <masashi910> 4. Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - iwamatsu
09:04:14 <masashi910> Quote from Iwamatsu-san "No update. No update/work can be seen even in Upstream etc."
09:04:21 <masashi910> 5. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu
09:04:51 <masashi910> Regarding this, I didn't receive his update.
09:04:57 <masashi910> any other topics?
09:05:04 <masashi910> 3
09:05:07 <masashi910> 2
09:05:08 <masashi910> 1
09:05:10 <masashi910> #topic Kernel maintenance updates
09:05:16 <masashi910> Quote from Iwamatsu-san "I reviewed LTS-rc. I send a comment."
09:05:25 <wens> I reviewed MRs from bwh and did a round of updates for cip-kernel-sec: new CVE-2020-10773 fixed in all branches, and the three new Spectre related CVEs, CVE-2020-1076[678], are now fixed in mainline
09:05:35 <paveltest> I have reviewed patches queued for 4.19.129.
09:06:18 <masashi910> wens, paveltest: Thanks for your updates.
09:06:27 <masashi910> any other topics?
09:06:44 <masashi910> 3
09:06:48 <masashi910> 2
09:06:52 <masashi910> 1
09:06:55 <masashi910> #topic Kernel testing
09:07:01 <masashi910> patersonc: the floor is yours.
09:07:12 <patersonc> info: Started to link up KernelCI with CIP's LAVA setup. We've tested it with staging.kernelci.org and it works.
09:07:20 <patersonc> info: This means that KernelCI can submit test jobs to the CIP reference platforms for mainline/stable Kernels etc.
09:07:21 <patersonc> e.g. https://staging.kernelci.org/test/job/kernelci/branch/staging.kernelci.org/kernel/staging-20200615.2/plan/baseline/
09:07:28 <patersonc> Hopefully it'll all be merged before ELC-NA.
09:07:49 <patersonc> Next step is to look into LTP and other test integration etc.
09:08:04 <patersonc> That's about it from me this week, unless there are any queries?
09:09:13 <masashi910> patersonc: Please let me clarify this.
09:09:48 <masashi910> I thought CIP testing team posts test results to KernelCI.
09:10:07 <patersonc> That's part of the next step
09:10:24 <masashi910> But your thought is for KernelCI to submit test jobs to CIP reference platforms at first.
09:10:48 <patersonc> We need to update KCI to work with our CI setup, as the build jobs won't be triggered by KernelCI.
09:11:30 <patersonc> So there are 2 approaches. 1) KernelCI builds the kernel and submits test jobs to our LAVA labs. 2) CIP builds kernels, tests them and submit the results to KCI. I'm planning to support both methods
09:11:52 <patersonc> Option 1) is easy and quick to do, so we're doing that first in time for ELC-NA
09:12:07 <patersonc> 2) will be done over the coming weeks (I hope)
09:12:44 <masashi910> patersonc: I see. Option 1 is not using CIP kernel, but it will be a basis for the next step.
09:13:00 <masashi910> patersonc: Thanks for your works!
09:13:12 <masashi910> are there any other topics?
09:13:21 <masashi910> or queries?
09:13:22 <patersonc> Yes. And the debate is still ongoing as to whether KernelCI would be willing to build/test the SLTS Kernels as part of kernelci.org or not
09:13:51 <masashi910> patersonc: I see. Thanks for this clarification.
09:14:06 <masashi910> any other topics or queries?
09:14:22 <masashi910> 3
09:14:25 <masashi910> 2
09:14:28 <masashi910> 1
09:14:31 <masashi910> #topic Software update
09:14:37 <suzuki> Hello
09:14:38 <masashi910> suzuki: the floor is yours.
09:14:49 <suzuki> Sorry, I don't have any updates this week.
09:14:58 <suzuki> I still work on the task which is to add a safe update demo to cip-sw-updates-demo repository: https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/4
09:15:03 <suzuki> That's it from me.
09:15:20 <masashi910> suzuki: Thanks for your report.
09:15:33 <masashi910> are their any other topics or queries?
09:15:44 <masashi910> 3
09:15:47 <masashi910> 2
09:15:50 <masashi910> 1
09:15:53 <masashi910> #topic CIP Security
09:16:17 <masashi910> Dinesh-san, are you going to report on behalf of Yoshida-san?
09:17:29 <masashi910> Or can I skip this part?
09:17:44 <masashi910> 3
09:17:49 <masashi910> 2
09:17:54 <masashi910> 1
09:17:57 <masashi910> #topic AOB
09:18:04 <masashi910> Are there any business matters to discuss?
09:18:18 <masashi910> 3
09:18:23 <masashi910> 2
09:18:26 <masashi910> 1
09:18:29 <masashi910> #endmeeting