Thursday, 2024-04-11

« Wednesday, 2024-04-10 Index Friday, 2024-04-12 »
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:49
*** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has joined #cip05:59
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)06:10
*** frieder <frieder!~frieder@67-179-142-46.pool.kielnet.net> has joined #cip07:46
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has quit IRC (Quit: Konversation terminated!)11:30
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has joined #cip11:31
*** hannah_k <hannah_k!~hannah@d8D87D23B.access.telenet.be> has joined #cip11:54
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has joined #cip12:57
*** jki <jki!~jki@46.128.88.20> has joined #cip12:58
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:691e:defb:9d5f:613b> has joined #cip12:59
jkihi all!13:00
pave1hi!13:00
masamihi13:00
iwamatsu__hi13:00
arisuthi13:00
ulihello13:01
patersonchi13:01
jkiok, let's go13:01
jki#startmeeting CIP IRC weekly meeting13:01
collab-meetbotMeeting started Thu Apr 11 13:01:52 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:01
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:01
jki#topic AI review13:01
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:01
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:02
jkino update (vacation...)13:02
jkianything else from past meetings?13:02
jki513:02
jki413:02
jki313:02
jki213:02
jki113:02
jki#topic Kernel maintenance updates13:02
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:02
pave1I'm doing reviews on 6.1.84..8613:03
ulii released 4.4, now reviewing 6.1.8313:03
masamiThis week reported 82 new CVEs and 16 updated CVEs.13:03
iwamatsu__I reviewed 6.1.84.13:03
pave1There's "Intel Atom" vulnerability -- not fixed in 4.19.13:04
jkimasami: do you also track later on rejected CVEs in the stats?13:04
masamijki: not yet but I'll13:04
pave1It is again speculative execution kind, so it will not matter for people not running untrusted code.13:04
jkipavel: 5.10 got a fix?13:05
pave1Yes.13:05
jkiwould backporting be complex?13:05
jkinot suggesting that we try, just to get a cost feeling13:05
pave1Not sure. It touches low level kernel entry/exit, so testing might be tricky.13:06
jkiwell, unless that is rarely used entry/exit code, practical coverage might be still high13:07
jkibut it would also need a reproducer to validate to mitigation13:07
pave1And affected system to run it on.13:07
jkibut there is no lower hw limited, is there?13:08
pave1I believe there is...13:08
pave1I'll make a note to take closer look?13:08
jkiwe should highlight this at the next TSC13:08
jkiyes, please13:08
jkianything else?13:09
jki513:10
jki413:10
jki313:10
jki213:10
jki113:10
jki#topic Kernel release status13:10
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:10
jki5.10-rt is late IIRC13:10
jkiwaiting for upstream release?13:10
pave1Yep. v5.10.214-rt106-rc1 is out there, so hopefully wait won't be too long.13:11
jkiok13:13
jkimoving on...13:13
jki513:13
jki413:13
jki313:13
jki213:13
jki113:13
jki#topic Kernel testing13:13
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:13
patersoncHello all13:13
arisuthi patersonc13:13
patersoncApologies for missing the E-TSC yesterday13:13
patersoncDid I miss anything exciting? (I'll review the video once it's out)13:14
patersoncWe've had some issues with the auto-scaling gitlab runners this week, which I think I've resolved now. Our runner-man is on holiday so they can double check things when they return13:15
arisutno idea but I see you at the KernelCI TSC13:15
patersoncPlease let me know if you spot any issues with the runners13:15
patersoncarisut: Yea I try to attend the monthly ones just so I'm half-in the loop13:15
jkipatersonc: yes, my latest pipelines passed13:15
patersoncGreat13:15
arisutI thought maybe we could try to deploy our own KernelCI instance13:16
patersoncpave1: Today's stable-rcs have all gone through as well13:16
pave1Umm. No, I had to retry.13:17
patersoncYes, but they have gone through now13:17
pave1But this time it was test, not compile phase, so there may be changes there.13:17
pave1Aha, yes. After enough retries it usually works :-).13:17
arisutstill I think that the next set is to work on the tool for sending command to the main instance (like kernel builds and test executions)13:18
arisutset/step13:18
patersoncarisut: Yea. We should have a chat about what to try next.13:19
arisutalso send results to the CIP results analyzer tool that now I struggle to rember the name13:19
patersoncYes, otherwise most of the testing done in kernelci is being ignored atm. Need to get that sorted13:20
arisutthanks13:21
jkiwhat is now the state of consolidating kernel configs to reduce builds (and costs...)?13:22
iwamatsu__As for x86, I have  been able to confirm the boot.13:24
jkiok, good13:25
jkiwhat is missing to finalize x86?13:25
jkibesides probably also patches to isar-cip-core13:25
iwamatsu__I think the .config needs to be reviewed next.13:26
jkiby whom all?13:26
jkiI just found the diff for the ipc227e - that's on us, ok13:27
iwamatsu__However, this is a merge of two .config files (OBS and IPC), so it may not be necessary.13:27
jkiCONFIG_NO_HZ on or off, CONFIG_PREEMPT_? - these are likely generic decisions13:27
iwamatsu__jki: yes, please review.13:28
jkiwhich of those we would like to focus on13:28
jkifor testing13:28
pave1I'd say CONFIG_NO_HZ=y.13:28
pave1As NO_HZ is more complex/risky then the other.13:28
jkiack13:29
pave1CONFIG_PREEMPT... I feel PREEMPT_NONE is not sexy so may get less testing... Might be worth testing both but that goes against the goals.13:29
jkiwell, we also have CONFIG_PREEMPT_RT(_FULL) in a different stream, I suppose13:30
pave1Yep. If we are testing other PREEMPT options elsewhere, we might as well test NONE here.13:31
jkimaybe PREEMPT_VOLUNTARY? or majority vote of known configs13:31
iwamatsu__Yes, we need to discuss them. However, the current diff has many items...13:31
jkiI'm seeing quite a view config switches now being off13:32
patersoncAnother option is to start building multiple configs in the same build environment. I assume a lot of files wouldn't need to be recompiled each time. At the moment we're very inefficient with a completely clean build env for each config13:32
jkithat should be changed unless there conflicts13:32
iwamatsu__I extract the main features (CONFIG_) from the diff.13:32
pave1I feel that we should have PREEMPT_VOLUNTARY in some config and PREEMPT_NONE in some other.13:32
jkiwe still have different archs anyway and could use that to vary some generic switches13:33
pave1Yes, that's what I meant.13:33
jkiok, I will try to review the ipc thing, but it would be good to have more eyes/opinions13:35
iwamatsu__Thank you.13:35
jkiand then maybe we just start with some version and ask for patches against it13:35
jkinothing is set in stone by that13:35
jkithe key is to switch the mode and, thus, force to work with that central config13:36
jkigood - more testing topics?13:37
patersoncsome version could = the defconfig for each arch13:37
patersoncjki: I've nothing else13:37
jki513:38
jki413:38
jki313:38
jki213:38
jki113:38
jki#topic AOB13:39
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:39
jkiI suppose I won't see anyone of you in Seattle next week, right?13:39
patersoncNot me, unless you want to take a photo with you13:40
arisutnot me13:40
pave1No plans on my side.13:40
iwamatsu__Not me.13:40
masaminot me13:40
jkijust checked: I may oversleep our irc meeting next week (6am PST)13:40
jkiin that case, someone else should please take over13:41
jkiany other topics?13:41
jki513:43
jki413:43
jki313:43
jki213:43
jki113:43
jki#endmeeting13:43
collab-meetbotMeeting ended Thu Apr 11 13:43:21 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:43
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/04/cip.2024-04-11-13.01.html13:43
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/04/cip.2024-04-11-13.01.txt13:43
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/04/cip.2024-04-11-13.01.log.html13: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 13: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/"13:43
jkithank you!13:43
pave1Thank you!13:43
ulithanks13:43
masamithanks13:43
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:43
patersoncHave a nice trip next week jki13:43
iwamatsu__Thank you13:43
arisutthanks you13:43
*** jki <jki!~jki@46.128.88.20> has quit IRC (Ping timeout: 246 seconds)14:04
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has quit IRC (Read error: Connection reset by peer)14:38
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has joined #cip14:39
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip14:41
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)14:52
*** hannah_k <hannah_k!~hannah@d8D87D23B.access.telenet.be> has quit IRC (Quit: Konversation terminated!)17:54
*** hannah_k <hannah_k!~hannah@d8D87D23B.access.telenet.be> has joined #cip18:22
*** hannah_k <hannah_k!~hannah@d8D87D23B.access.telenet.be> has quit IRC (Client Quit)18:22
*** hannah_k <hannah_k!~hannah@d8D87D23B.access.telenet.be> has joined #cip18:32
*** frieder <frieder!~frieder@67-179-142-46.pool.kielnet.net> has quit IRC (Remote host closed the connection)18:36
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:691e:defb:9d5f:613b> has quit IRC (Quit: Client closed)19:40
*** hannah_k <hannah_k!~hannah@d8D87D23B.access.telenet.be> has quit IRC (Quit: Konversation terminated!)19:49
« Wednesday, 2024-04-10 Index Friday, 2024-04-12 »

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