IRC logs for #cip for Thursday, 2022-03-10

*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC00:18
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip00:53
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:57
*** helmut <helmut!helmut@subdivi.de> has quit IRC08:08
*** helmut <helmut!helmut@subdivi.de> has joined #cip08:12
*** toscalix <toscalix!~toscalix@73.pool90-167-218.static.orange.es> has joined #cip09:21
*** uli <uli!~uli@55d483ee.access.ecotel.net> has joined #cip11:09
*** fbezdeka <fbezdeka!~flo@2a02:810d:82c0:38fc:30d6:ec3a:bc18:37f5> has joined #cip11:58
*** toscalix <toscalix!~toscalix@73.pool90-167-218.static.orange.es> has quit IRC12:40
*** toscalix <toscalix!~toscalix@73.pool90-167-218.static.orange.es> has joined #cip12:40
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip12:48
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip12:57
*** jki <jki!~jki@165.225.27.7> has joined #cip12:59
*** pave1 <pave1!~pavel@88.103.226.136> has joined #cip13:00
jki#startmeeting CIP IRC weekly meeting13:00
brlogger`Meeting started Thu Mar 10 13:00:57 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
brlogger`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
brlogger`The meeting name has been set to 'cip_irc_weekly_meeting'13:00
*** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:00
collab-meetbotMeeting started Thu Mar 10 13:00:57 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:00
jkihi!13:01
ulihello13:01
iwamatsuhi13:01
masamihello13:01
pave1hi!13:01
josiahHi13:03
patersonc[m]Hello13:04
jkiok, let's go13:04
jki#topic AI review13:05
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:05
jki1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm13:05
patersonc[m]Sorry, nothing done yet13:06
jki2. Add 4.9-stable-rc to testing - patersonc13:06
patersonc[m]I started this13:06
patersonc[m]We're missing three configs from cip-kernel-config for 4.913:07
patersonc[m]Other then that things are working13:07
pave1 ...and it gave first results. Thanks!13:07
patersonc[m]Do we know if any more boards are supported natively in 4.9 compared to 4.4?13:07
patersonc[m]iwamatsu: Ah I've just seen your email about the configs. Thank you13:08
jkiso this topic can be considered done?13:09
iwamatsupatersonc: sorry about it.13:09
patersonc[m]I need to merge, but essentially all is in place13:09
jkiperfect13:09
jkianything else before moving on?13:10
jki313:10
jki213:10
jki113:10
jki#topic Kernel maintenance updates13:10
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:10
pave1I did some reviews on 5.10.104 and 105. Working on scripts for self-maintainance.13:11
ulireviewing 5.10.10413:11
masamiThis week reported 12 new CVEs and 3 updated CVEs.13:11
masamiDirty Pipe and BHI (Spectre-BHB) are notable issues.13:11
iwamatsuI could not kernel review work this week.13:12
jkiSpectre-BHB is arm64, right? what about that AMD spectre issue?13:13
masamiintel and amd cpus are affected13:14
pave1If there's good summary of the spectre issues, I'd like to know.13:14
iwamatsuDo we need to release 5.10.Y-cip for fixing those CVEs?13:14
jkimore than likely13:14
jkiI have more and more user with "apps" on their machines, thus not only with fully trusted code13:15
patersonc[m]pave1: There are some links to summaries on here: https://lwn.net/Articles/887326/13:15
pave1patersonc: Thank you!13:16
masamiPoC is on the github https://github.com/vusec/bhi-spectre-bhb13:16
jkithis is really limited to eBPF?13:16
jkihmm, the exploit PoC does not look like bpf13:19
masamiIt looks like eBPF is one of the methods to abuse this bug.13:19
pave1jki: The FAQ at https://www.vusec.net/projects/bhi-spectre-bhb/ says eBPF makes it easier, but should not really be a requirement.13:20
jkiok (or not) - then we should better fix soon13:20
pave1jki: Well, well well. I'll get you a hammer and you can smash all the affected CPUs? :-)13:21
jkineed to have a long shaft ;)13:21
pave1jki: I mean, we can't really _fix_ that. Those CPUs are broken. We can apply workarounds but bug will re-surface.13:21
jkilikely13:21
pave1:-(.13:22
jkibut this isssue is also one of those with high public attention13:22
pave1We can hand out more hammers :-).13:22
pave1I guess we should make a release once 5.10.105 is out?13:22
patersonc[m]Doesn't affect RISC-V :)13:23
jkilet's see when that will change ;)13:23
iwamatsu+113:23
pave1patersonc: There are few high-performance RISC-V CPUs. So that may not really be good news for RISC-V.13:23
jkiso, 5.10.105 will be the first to have these "workarounds"?13:23
jkipavel: exactly...13:24
patersonc[m]pave1: :)13:24
pave1dirty pipe is fixed in 5.10.103 or so. Speculation workarounds are being reveiewed for 5.10.105-rc1.13:24
fbezdekaAccording to the -rc candidate Greg posted earlier today 5.10.105 will hold such "workarounds"13:24
jkiare we ready to release quickly after upstream?13:25
jkior should we better move forward to clean the dirty pipe?13:25
jkigranted, that one is easy to fix locally if users are in a hurry13:26
pave15.10.105 can be expected this Friday or next Monday, I'd say.13:27
fbezdeka"Responses should be made by Fri, 11 Mar 2022 15:58:48 +0000."13:27
jkiso, what are the opinions?13:29
iwamatsuI think that local fixes mean a fork, so it is not a good way.13:30
pave1I believe one release based on 5.10.105 should be enough.13:31
iwamatsuI would like to wait for 5.10.105.13:31
masami+1 to wait for 5.10.10513:31
jkiok, but then let's communicate this to the list13:32
pave1iwamatsu: You have script modifying wiki when new -rc is out? Could that be suspended for now?13:33
pave1I'll simply manually update it when uli tells us that he's about to run out of work.13:34
iwamatsupave1: ok, I will suspend it.13:34
pave1Thank you!13:34
iwamatsususpended now.13:36
pave1Wow, that was quick. Thanks!13:37
pave1...mov on?13:40
jkibtw, someone read https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec/-/blob/master/issues/CVE-2022-0847.yml and was confused that 4.19 was not in the ignore list13:40
masamijki: 4.19 had uninitialized bug too.13:42
masamiso, 4.19 is in fixed-by list.13:43
jkibut not the CVE13:43
jkiok, anyway, I explained this (more than once)13:43
masamiah, yes.13:43
jkithen let's move on13:44
masamiI will update it.13:44
jkithanks!13:44
jki#topic Kernel testing13:44
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:44
patersonc[m]As you know I looked at 4.9.y-rc testing13:45
patersonc[m]Other then that not much to report13:45
jkiok - anything else on testing by others?13:46
jki313:47
jki213:47
jki113:47
jki#topic AOB13:47
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:47
jkilooks like LF actually changed the directory layout of the logger for us!13:47
patersonc[m]Are we aiming for a new 4.19-rt release any time soon? Someone pointed out to me that it's been 3 months since the last one13:47
pave1patersonc: in february, we did not get matching 4.19-cip and 4.19-rt releases. We should get that in March.13:48
jkiI think we need to reconsider this13:48
jkiwhen the gap becomes so large and, thus, unpredictable13:49
jkipavel: did you try in the past to rebase rt queues?13:49
patersonc[m]Can we try and base the cip releases on what is available from rt-stable?13:49
pave1jki: I tried at some point, and it did not work well.13:50
jki4.4 or 4.19?13:50
jkior both?13:50
pave1jki: it is quite possible it would work other times.13:50
jkiyes, I would assume so as well13:51
jkialternative: release (extra) CIP kernels that match13:51
pave1alternative: Adjust -cip releases to match -rt releases.13:52
jkibut waiting 3 months for that to happen by chance is not that optimal13:52
pave1Let me check 4.19-rt releases.13:53
pave1For 4.4-rt, we'll have to self-maintain, so .. that will be way more fun.13:53
jkisure - and no "excuses" ;)13:53
jkiif there is additional effort involved, let's discuss how to tackle it13:54
pave14.19-rt releases are happening about twice a month.13:54
pave1Last one is Linux 4.19.232-rt104  from Mar 4.13:54
pave1I believe we decided to do 4.190-rt once per two months?13:55
pave1Easy solution from my side would be to wait for 4.19-rt when releasing 4.19-cip, at least every other month, so we get match for easy release.13:56
jki...unless there are prominent CVEs pending13:57
jkiI would rather vote for having an extra regular -cip release when in doubt13:57
jkiprovided we are ready from review and testing perspective13:58
jkibut if we aren't we can't release a -rt either13:58
pave1Yes, we may want to speed up with CVEs.13:58
pave1Most of speculation fixes will _not_ be in 4.19.234. They should make it to the next one.13:59
pave1But with -rt releases in the picture, that becomes kind of gamble :-(.13:59
jkiCVE trumps -rt14:01
jkionce rt caught up, we could do another regular cip release and a corresponding -rt14:01
jkiif nothing urgent is in the queue, we try to sync both releases carefully14:02
pave1Yes, we can always solve problem with more -cip releases :-).14:02
pave1So the latest 4.19-rt is 4.19.232-rt104.14:02
jkiwhatever is optimal under speed AND effort constraints :)14:02
pave14.19.235 is likely to have speculation fixes.14:03
pave1I'd suggest to wait for next 4.19-rt and do both -cip and -rt releases...?14:04
*** toscalix <toscalix!~toscalix@73.pool90-167-218.static.orange.es> has quit IRC14:05
jkiwell, our beloved CVEs get resolved earlier, I would not delay the regular -cip release - but maybe we will be lucky this time14:06
pave1Right, if 4.19.235 is out with the fixes and -rt release is nowhere around, we may need to act, anyway.14:08
jkiok - anything else, on this or beyond?14:08
jkiif not...14:09
jki314:09
jki214:09
jki114:09
jki#endmeeting14:09
collab-meetbotMeeting ended Thu Mar 10 14:09:46 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:09
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-10-13.00.html14:09
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-10-13.00.txt14:09
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-10-13.00.log.html14:09
brlogger`Meeting ended Thu Mar 10 14:09:46 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:09
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-10-13.00.html14:09
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-10-13.00.txt14:09
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-10-13.00.log.html14:09
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"14:09
pave1Thank you... and stay safe!14:09
jkithanks for your time14:09
ulithanks14:09
jkibye!14:10
masamithank you14:10
iwamatsuthank you14:10
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC14:10
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC14:10
*** jki <jki!~jki@165.225.27.7> has quit IRC14:11
*** fbezdeka <fbezdeka!~flo@2a02:810d:82c0:38fc:30d6:ec3a:bc18:37f5> has left #cip14:11
*** pave1 <pave1!~pavel@88.103.226.136> has quit IRC14:36
*** toscalix <toscalix!~toscalix@1.pool90-167-219.static.orange.es> has joined #cip15:14
*** toscalix <toscalix!~toscalix@1.pool90-167-219.static.orange.es> has quit IRC15:14
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC22:02
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC23:08
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip23:37

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