12:01:04 <jki_> #startmeeting CIP IRC weekly meeting
12:01:04 <collab-meetbot`> Meeting started Thu Apr 14 12:01:04 2022 UTC and is due to finish in 60 minutes.  The chair is jki_. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:04 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:04 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:04 <brlogger> Meeting started Thu Apr 14 12:01:04 2022 UTC and is due to finish in 60 minutes.  The chair is jki_. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:04 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:04 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:08 <jki_> Hi all!
12:01:30 <uli> hello
12:01:34 <alicef_> Hi
12:01:35 <masami> hi!
12:02:17 <pave1> hi!
12:06:09 <jki_> hmm, hope shifting didn't cause confusion now...
12:06:21 <jki_> let's start nevertheless
12:06:28 <jki_> #topic AI review
12:06:40 <jki_> 1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm
12:07:19 <alicef_> No updates from me
12:07:51 <jki_> ok
12:07:56 <jki_> were there any other AIs I oversaw?
12:08:12 <pave1> I believe that's all.
12:08:19 <jki_> #topic Kernel maintenance updates
12:08:33 <pave1> I am reviewing 5.10.110 and .111.
12:08:40 <uli> reviewing 5.10.110
12:08:42 <masami> This week 9 new CVEs and 9 updated CVEs. No notable new CVEs.
12:08:48 <masami> stable/4.9 has been added Spectre-BHB patches.
12:09:57 <jki_> for x86? or just arm64?
12:10:13 <masami> jki_: for arm64
12:10:24 <iwamatsu> hi, all
12:10:31 <jki_> so that would not be of interest for us
12:11:44 <iwamatsu> I am reviewing 5.10.110, and I released v5.10.109-cip5 and v4.19.237-cip71.
12:12:31 <masami> It may be useful if we backport Spectre-BHB patches to 4.4-st. I think.
12:13:26 <iwamatsu> +1
12:13:27 <jki_> how would we test?
12:13:36 <pave1> I guess it depends on effort neccessary. If they apply cleanly, it would be actually more work to exclude them.
12:13:39 <jki_> kernelci?
12:14:33 <pave1> jki: That's common problem with obscure security issues like this :-). kernelci will tell us if we broke the boot, but testing if we closed the holes would be tricky.
12:14:42 <alicef_> Kernelci does spectre meltdown check test
12:15:02 <jki_> also for bhb already?
12:15:25 <alicef_> Not sure about that need to check
12:16:18 <alicef_> I recently updated it to latest smc versoion but could be that still need new updates
12:16:48 <jki_> the signal could be bad if we do that "fixing" blindly
12:17:25 <pave1> jki: -stable is basically all fixing blindly :-(.
12:17:50 <alicef_> Looks like they updated smc it few days ago
12:18:02 <alicef_> I will send a update
12:18:56 <alicef_> "An intermediary release with preparatory work needed to integrate support for new vulns BHI and intra-mode BTI (Spectre V2-like), along with other changes that were in the pipe in the last few months"
12:20:46 <jki_> alicef_: so, you will look into enable kernelci for those, and then we also have basic test coverage for newer kernels, right?
12:21:01 <alicef_> Yes
12:21:15 <jki_> great!
12:23:41 <jki_> ok, anything else on this?
12:23:57 <pave1> I'll have to leave early, sorry. Nothing else from me.
12:24:21 <jki_> then let's move on
12:24:25 <jki_> 3
12:24:26 <jki_> 2
12:24:28 <jki_> 1
12:24:30 <jki_> #topic Kernel testing
12:25:18 <jki_> we still have quota issues on gitlab.com...
12:25:29 <alicef_> My pr for enabling rt preempt rt test on cip rt as been merged on KernelCI
12:25:58 <alicef_> This is one example https://staging.kernelci.org/test/plan/id/6246b8ade748c32a8b05f4c4/
12:26:18 <alicef_> For v5.10.104-cip3-rt3
12:28:27 <jki_> smoke tests, I assume (given the number of cycles)
12:28:41 <alicef_> Where is getting results from preempt rt cyclic test and such data could be useful for keep an eye on next release differences
12:28:43 <jki_> 300 s - yeah
12:30:06 <jki_> "ARTIFACTORIAL_TOKEN is empty! File uploading skipped." - discussed that with a colleague yesterday
12:30:26 <jki_> we need client-originated uploads in the future
12:30:30 <jki_> not target
12:30:55 <jki_> alicef_: do you know the status of related activities?
12:31:29 <alicef_> Sorry, activities on what?
12:31:51 <alicef_> My preempt rt patch for KernelCI?
12:31:53 <jki_> to enhance LAVA that the client can fetch and push measurement results from the DUT
12:32:29 <jki_> then we can store more than a single number and do more sophisticated evaluations
12:33:11 <jki_> anyway, this is definitely already a valuable improvement
12:34:12 <alicef_> I don't think this come out in any KernelCI recent discussion afaik
12:34:48 <alicef_> Feel free to open a issue/request about this on KernelCI
12:35:33 <alicef_> Looks like such improvement would benefit also KernelCI
12:37:02 <jki_> anything else regarding testing?
12:37:22 <alicef_> No more updates from me
12:37:45 <jki_> then let's move on...
12:37:49 <jki_> #topic AOB
12:39:00 <jki_> anchor the meeting time on European DST in the future?
12:39:43 <jki_> would mean shifting start time in other time zones, and probably also some mess for US (different DST switching dates)
12:42:29 <alicef_> Either works for me
12:42:37 <uli> same here
12:42:45 <alicef_> There is no dst here
12:43:32 <jki_> for our meeting, there would be then if we follow ours in Europe...
12:43:36 <iwamatsu> I have no problem with DST.
12:44:03 <alicef_> No problem for me
12:44:34 <jki_> then keep that in mind, and we can still discuss again in Autumn if issues arrise
12:44:40 <jki_> anything else?
12:45:39 <jki_> 3
12:45:41 <jki_> 2
12:45:43 <jki_> 1
12:45:45 <jki_> #endmeeting