IRC logs for #cip for Thursday, 2022-04-14

« Wednesday, 2022-04-13 Index Friday, 2022-04-15 »
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip05:41
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC05:52
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip05:56
*** monstr <monstr!~monstr@2a02:768:2307:40d6:f44b:4166:f09c:e722> has joined #cip08:03
*** alicef_ <alicef_!~none@gentoo/developer/alicef> has joined #cip08:20
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC08:22
*** toscalix <toscalix!~toscalix@213.red-79-144-153.dynamicip.rima-tde.net> has joined #cip09:14
*** uli <uli!~uli@55d43d5e.access.ecotel.net> has joined #cip10:10
*** masami <masami!~masami@FL1-119-240-125-62.tky.mesh.ad.jp> has joined #cip11:24
*** jki <jki!~jki@88.215.102.122> has joined #cip11:55
*** pave1 <pave1!~pavel@88.103.226.33> has joined #cip11:59
*** jki_ <jki_!~jki@165.225.26.246> has joined #cip12:00
jki_#startmeeting CIP IRC weekly meeting12:01
brloggerMeeting 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
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'12:01
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:01
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
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:01
jki_Hi all!12:01
ulihello12:01
alicef_Hi12:01
masamihi!12:01
pave1hi!12:02
*** jki <jki!~jki@88.215.102.122> has quit IRC12:04
jki_hmm, hope shifting didn't cause confusion now...12:06
jki_let's start nevertheless12:06
jki_#topic AI review12:06
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:06
jki_1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm12:06
alicef_No updates from me12:07
jki_ok12:07
jki_were there any other AIs I oversaw?12:07
pave1I believe that's all.12:08
jki_#topic Kernel maintenance updates12:08
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:08
pave1I am reviewing 5.10.110 and .111.12:08
ulireviewing 5.10.11012:08
masamiThis week 9 new CVEs and 9 updated CVEs. No notable new CVEs.12:08
masamistable/4.9 has been added Spectre-BHB patches.12:08
jki_for x86? or just arm64?12:09
masamijki_: for arm6412:10
iwamatsuhi, all12:10
jki_so that would not be of interest for us12:10
iwamatsuI am reviewing 5.10.110, and I released v5.10.109-cip5 and v4.19.237-cip71.12:11
masamiIt may be useful if we backport Spectre-BHB patches to 4.4-st. I think.12:12
iwamatsu+112:13
jki_how would we test?12:13
pave1I guess it depends on effort neccessary. If they apply cleanly, it would be actually more work to exclude them.12:13
jki_kernelci?12:13
pave1jki: 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
alicef_Kernelci does spectre meltdown check test12:14
jki_also for bhb already?12:15
alicef_Not sure about that need to check12:15
alicef_I recently updated it to latest smc versoion but could be that still need new updates12:16
jki_the signal could be bad if we do that "fixing" blindly12:16
pave1jki: -stable is basically all fixing blindly :-(.12:17
alicef_Looks like they updated smc it few days ago12:17
alicef_I will send a update12:18
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:18
jki_alicef_: so, you will look into enable kernelci for those, and then we also have basic test coverage for newer kernels, right?12:20
alicef_Yes12:21
jki_great!12:21
jki_ok, anything else on this?12:23
pave1I'll have to leave early, sorry. Nothing else from me.12:23
jki_then let's move on12:24
jki_312:24
jki_212:24
jki_112:24
jki_#topic Kernel testing12:24
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:24
*** pave1 <pave1!~pavel@88.103.226.33> has quit IRC12:24
jki_we still have quota issues on gitlab.com...12:25
alicef_My pr for enabling rt preempt rt test on cip rt as been merged on KernelCI12:25
alicef_This is one example https://staging.kernelci.org/test/plan/id/6246b8ade748c32a8b05f4c4/12:25
alicef_For v5.10.104-cip3-rt312:26
jki_smoke tests, I assume (given the number of cycles)12:28
alicef_Where is getting results from preempt rt cyclic test and such data could be useful for keep an eye on next release differences12:28
jki_300 s - yeah12:28
jki_"ARTIFACTORIAL_TOKEN is empty! File uploading skipped." - discussed that with a colleague yesterday12:30
jki_we need client-originated uploads in the future12:30
jki_not target12:30
jki_alicef_: do you know the status of related activities?12:30
alicef_Sorry, activities on what?12:31
alicef_My preempt rt patch for KernelCI?12:31
jki_to enhance LAVA that the client can fetch and push measurement results from the DUT12:31
jki_then we can store more than a single number and do more sophisticated evaluations12:32
jki_anyway, this is definitely already a valuable improvement12:33
alicef_I don't think this come out in any KernelCI recent discussion afaik12:34
alicef_Feel free to open a issue/request about this on KernelCI12:34
alicef_Looks like such improvement would benefit also KernelCI12:35
jki_anything else regarding testing?12:37
alicef_No more updates from me12:37
jki_then let's move on...12:37
jki_#topic AOB12:37
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:37
jki_anchor the meeting time on European DST in the future?12:39
jki_would mean shifting start time in other time zones, and probably also some mess for US (different DST switching dates)12:39
alicef_Either works for me12:42
ulisame here12:42
alicef_There is no dst here12:42
jki_for our meeting, there would be then if we follow ours in Europe...12:43
iwamatsuI have no problem with DST.12:43
alicef_No problem for me12:44
jki_then keep that in mind, and we can still discuss again in Autumn if issues arrise12:44
jki_anything else?12:44
jki_312:45
jki_212:45
jki_112:45
jki_#endmeeting12:45
brloggerMeeting ended Thu Apr 14 12:45:45 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:45
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2022/04/cip.2022-04-14-12.01.html12:45
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2022/04/cip.2022-04-14-12.01.txt12:45
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2022/04/cip.2022-04-14-12.01.log.html12:45
*** brlogger 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 13:00 UTC | Find the meeting logs at https://irclogs.baserock.org/cip/""12:45
collab-meetbot`Meeting ended Thu Apr 14 12:45:45 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:45
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/04/cip.2022-04-14-12.01.html12:45
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/04/cip.2022-04-14-12.01.txt12:45
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/04/cip.2022-04-14-12.01.log.html12:45
jki_thank you all!12:45
ulithanks12:46
masamithank you12:46
iwamatsuthank you!12:46
alicef_Thanks12:46
jki_bye!12:46
*** jki_ <jki_!~jki@165.225.26.246> has quit IRC12:46
*** toscalix <toscalix!~toscalix@213.red-79-144-153.dynamicip.rima-tde.net> has quit IRC14:15
*** monstr <monstr!~monstr@2a02:768:2307:40d6:f44b:4166:f09c:e722> has quit IRC17:04
*** iwamatsu` <iwamatsu`!~iwamatsu@www1015ue.sakura.ne.jp> has joined #cip17:32
*** masami <masami!~masami@FL1-119-240-125-62.tky.mesh.ad.jp> has quit IRC17:33
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has quit IRC17:33
*** masami <masami!~masami@FL1-119-240-125-62.tky.mesh.ad.jp> has joined #cip17:37
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC21:43
*** masami <masami!~masami@FL1-119-240-125-62.tky.mesh.ad.jp> has quit IRC21:51
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip21:51
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC21:58
« Wednesday, 2022-04-13 Index Friday, 2022-04-15 »

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