Thursday, 2022-06-02

« Wednesday, 2022-06-01 Index Friday, 2022-06-03 »
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:02
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo)07:45
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip07:46
*** ChanServ sets mode: +o alicef07:46
*** toscalix <toscalix!~toscalix@253.red-81-37-17.dynamicip.rima-tde.net> has joined #cip07:48
*** uli <uli!~uli@55d4e144.access.ecotel.net> has joined #cip09:07
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip09:38
*** masami <masami!~masami@FL1-220-144-160-220.tky.mesh.ad.jp> has joined #cip11:23
*** jki <jki!~jki@165.225.27.18> has joined #cip12:00
jki#startmeeting CIP IRC weekly meeting12:00
collab-meetbotMeeting 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
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:00
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:00
jkihi all!12:00
alicefmHello12:00
iwamatsuhi12:00
ulihello12:00
masamihi12:00
pave1hi12:00
*** josiah <josiah!~kvirc@pool-100-16-207-123.bltmmd.fios.verizon.net> has joined #cip12:01
jkigood, let's get started12:03
jki#topic AI review12:04
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:04
jki1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm12:04
jkiI suspect I already know the status ;)12:04
alicefmSorry didn’t check yet12:04
jkiany other AIs I missed?12:05
jki312:05
jki212:05
jki112:05
jki#topic Kernel maintenance updates12:05
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:05
alicefmCould you please also add to the ai patersonc task of checking cip devices on kernelci old pull request?12:05
alicefmSent by me as some of that got closed for inactivity12:06
ulino updates, i was out this week. will continue with 4.4 reviews.12:06
jkialicefm: will do12:06
masamiThere was 6 new CVEs and 3 updated CVEs.12:06
masamiCVE-2022-1882,CVE-2022-1966, and CVE-2022-1462 aren't fixed in the mainline yet.12:06
iwamatsuI did not work for patch review in this week.12:08
pave1I was reviewing 5.10.118 and 11912:08
pave1.119 is scary -- rewrite of /dev/random without really good reasons for stable.12:08
jkiyet unpublished security issue?12:09
pave1I dont think so. More like 'sounds vaguely security related, lets merge 100 patch series'.12:10
iwamatsuI didn't see the content of the patch, but I was surprised to see the patch list.12:10
pave1It is not queued for 4.19, so it should not be real security.12:11
jkiis 5.15 getting this as well?12:12
iwamatsuyes12:13
iwamatsuincluded in 5.15.44.12:13
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 reason12:15
jkithat's the top of the queue, not sure if the rest is truly a precondition12:16
pave1Well -- that one could be done with12:18
pave1one line... but Greg sometimes does stuff like this.12:19
pave1And there's not much that can be done to fix that.12:20
jkiask him for more background of this?12:20
jkispecifically if not all stable trees have this yet12:20
pave1Tried asking, and Im not the only one wondering.12:21
pave1Best explanation so far is that new code is compliant with some FIPS spec.12:21
jkistill suspicious to me, specifically as I've seen such arguments before as cover-up12:23
pave1Hmm. Time will tell I guess. If there's NDA they will not be able to tell.12:24
jkiyep12:25
jkimore topics?12:25
jki312:26
jki212:26
jki112:26
jki#topic Kernel testing12:26
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:26
alicefmNothing from me12:27
pave15.10.119 testing failed, but I could not figured out12:27
pave1if it is real failure or test failure.12:28
pave1Probably test failure as we are only ones seeing it, but if someone could12:28
pave1double check, it would be nice.12:28
alicefmOn what hw?12:29
pave1It was two or three boards.12:29
alicefmOn gitlab or KernelCI?12:30
pave1I'll send an email, ok?12:30
pave1gitlab.12:30
iwamatsuhttps://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/549589225 ?12:30
jkithat's all green - or are we missing failure reports in gitlab?12:34
jkior https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/2514246181 e.g.?12:35
iwamatsuThere is no problem with the LAVA test running in the test. https://lava.ciplatform.org/scheduler/job/68758112:37
pave1Weird. I believe  549589225 pipeline was failing before.12:37
iwamatsuProbably a timeout of Lava Master or GitLab CI?12:37
pave1Aha, I missed the emails. Chris solved it in the meantime and re-ran the tests.12:38
pave1Sorry for the noise.12:38
jkiok, all fine12:38
iwamatsu:-)12:38
jkigood, tests are running - anything else?12:39
jki312:39
jki212:39
jki112:39
jki#topic AOB12:39
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:39
jkiI'm going to have a chat with RT-preempt folks next week (high altitude rt workshop)12:40
jkiany topic I should take with me?12:40
pave1I don't know about anything specific.12:42
jkiok12:42
jkiany other topic?12:42
jki312:43
jki212:43
jki112:43
jki#endmeeting12:43
collab-meetbotMeeting ended Thu Jun  2 12:43:55 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:43
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/06/cip.2022-06-02-12.00.html12:43
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/06/cip.2022-06-02-12.00.txt12:43
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/06/cip.2022-06-02-12.00.log.html12:43
*** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/""12:43
jkithanks all!12:44
pave1Thank you, stay safe!12:44
ulithanks12:44
iwamatsuthank you12:44
jkiyou too!12:44
masamithank you12:44
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving)12:44
*** josiah <josiah!~kvirc@pool-100-16-207-123.bltmmd.fios.verizon.net> has quit IRC (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/)12:44
alicefthanks you12:45
*** jki <jki!~jki@165.225.27.18> has quit IRC (Quit: Leaving)12:45
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC (Ping timeout: 260 seconds)12:45
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip12:58
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC (Remote host closed the connection)14:35
*** toscalix <toscalix!~toscalix@253.red-81-37-17.dynamicip.rima-tde.net> has quit IRC (Remote host closed the connection)16:58
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 255 seconds)21:33
« Wednesday, 2022-06-01 Index Friday, 2022-06-03 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!