12:00:32 <jki> #startmeeting CIP IRC weekly meeting
12:00:33 <collab-meetbot> Meeting started Thu Jun  2 12:00:32 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:33 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:00:33 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:00:37 <jki> hi all!
12:00:38 <alicefm> Hello
12:00:39 <iwamatsu> hi
12:00:39 <uli> hello
12:00:41 <masami> hi
12:00:53 <pave1> hi
12:03:57 <jki> good, let's get started
12:04:00 <jki> #topic AI review
12:04:05 <jki> 1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm
12:04:32 <jki> I suspect I already know the status ;)
12:04:42 <alicefm> Sorry didn’t check yet
12:05:23 <jki> any other AIs I missed?
12:05:32 <jki> 3
12:05:35 <jki> 2
12:05:37 <jki> 1
12:05:40 <jki> #topic Kernel maintenance updates
12:05:55 <alicefm> Could you please also add to the ai patersonc task of checking cip devices on kernelci old pull request?
12:06:25 <alicefm> Sent by me as some of that got closed for inactivity
12:06:26 <uli> no updates, i was out this week. will continue with 4.4 reviews.
12:06:47 <jki> alicefm: will do
12:06:49 <masami> There was 6 new CVEs and 3 updated CVEs.
12:06:52 <masami> CVE-2022-1882,CVE-2022-1966, and CVE-2022-1462 aren't fixed in the mainline yet.
12:08:03 <iwamatsu> I did not work for patch review in this week.
12:08:04 <pave1> I was reviewing 5.10.118 and 119
12:08:34 <pave1> .119 is scary -- rewrite of /dev/random without really good reasons for stable.
12:09:28 <jki> yet unpublished security issue?
12:10:20 <pave1> I dont think so. More like 'sounds vaguely security related, lets merge 100 patch series'.
12:10:27 <iwamatsu> I didn't see the content of the patch, but I was surprised to see the patch list.
12:11:35 <pave1> It is not queued for 4.19, so it should not be real security.
12:12:11 <jki> is 5.15 getting this as well?
12:13:03 <iwamatsu> yes
12:13:49 <iwamatsu> included in 5.15.44.
12:15:33 <jki> "Before this patch, massive writes to /dev/urandom would tie up the process for an extremely long time and make it unterminatable." - kind of local DoS, maybe that's the reason
12:16:11 <jki> that's the top of the queue, not sure if the rest is truly a precondition
12:18:51 <pave1> Well -- that one could be done with
12:19:17 <pave1> one line... but Greg sometimes does stuff like this.
12:20:01 <pave1> And there's not much that can be done to fix that.
12:20:12 <jki> ask him for more background of this?
12:20:27 <jki> specifically if not all stable trees have this yet
12:21:22 <pave1> Tried asking, and Im not the only one wondering.
12:21:51 <pave1> Best explanation so far is that new code is compliant with some FIPS spec.
12:23:10 <jki> still suspicious to me, specifically as I've seen such arguments before as cover-up
12:24:47 <pave1> Hmm. Time will tell I guess. If there's NDA they will not be able to tell.
12:25:36 <jki> yep
12:25:48 <jki> more topics?
12:26:34 <jki> 3
12:26:38 <jki> 2
12:26:42 <jki> 1
12:26:46 <jki> #topic Kernel testing
12:27:08 <alicefm> Nothing from me
12:27:48 <pave1> 5.10.119 testing failed, but I could not figured out
12:28:00 <pave1> if it is real failure or test failure.
12:28:24 <pave1> Probably test failure as we are only ones seeing it, but if someone could
12:28:33 <pave1> double check, it would be nice.
12:29:05 <alicefm> On what hw?
12:29:46 <pave1> It was two or three boards.
12:30:19 <alicefm> On gitlab or KernelCI?
12:30:31 <pave1> I'll send an email, ok?
12:30:35 <pave1> gitlab.
12:30:36 <iwamatsu> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/549589225 ?
12:34:51 <jki> that's all green - or are we missing failure reports in gitlab?
12:35:20 <jki> or https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/2514246181 e.g.?
12:37:06 <iwamatsu> There is no problem with the LAVA test running in the test. https://lava.ciplatform.org/scheduler/job/687581
12:37:41 <pave1> Weird. I believe  549589225 pipeline was failing before.
12:37:55 <iwamatsu> Probably a timeout of Lava Master or GitLab CI?
12:38:33 <pave1> Aha, I missed the emails. Chris solved it in the meantime and re-ran the tests.
12:38:43 <pave1> Sorry for the noise.
12:38:46 <jki> ok, all fine
12:38:49 <iwamatsu> :-)
12:39:13 <jki> good, tests are running - anything else?
12:39:33 <jki> 3
12:39:35 <jki> 2
12:39:36 <jki> 1
12:39:40 <jki> #topic AOB
12:40:25 <jki> I'm going to have a chat with RT-preempt folks next week (high altitude rt workshop)
12:40:34 <jki> any topic I should take with me?
12:42:05 <pave1> I don't know about anything specific.
12:42:47 <jki> ok
12:42:53 <jki> any other topic?
12:43:47 <jki> 3
12:43:49 <jki> 2
12:43:52 <jki> 1
12:43:55 <jki> #endmeeting