Thursday, 2025-04-17

*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:38
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)05:43
*** rajm <rajm!~robert@host-92-15-180-94.as13285.net> has quit IRC (Remote host closed the connection)06:21
*** rajm <rajm!~robert@host-92-15-180-94.as13285.net> has joined #cip06:55
*** tmerciai <tmerciai!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has joined #cip07:30
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip10:23
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)12:34
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip12:35
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has joined #cip12:36
*** tmerciai <tmerciai!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has quit IRC (Ping timeout: 252 seconds)12:40
*** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has joined #cip12:57
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip12:58
*** jki <jki!~jki@95.157.49.24> has joined #cip13:00
jkihi all13:00
uli_hello13:00
masamihi13:00
pave1hi!13:00
iwamatsu__hi13:01
jkiok, let's go13:01
jki#startmeeting CIP IRC weekly meeting13:01
collab-meetbotMeeting started Thu Apr 17 13:01:49 2025 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- check release scripts/procedures shared by iwamatsu-san [pavel]13:02
pave1I took a look. They'd need a bit of docs and quite a lot of documenting prerequisites.13:02
pave1Plus, trying to modify someone else's shell code ... is not easy.13:03
iwamatsu__pave1: OK, I will create a document.13:04
pave1Mainly directory tree it expects to work in would be useful.13:04
jkiok, then there is clear next step13:06
jkifurther concrete wisches/feedback may also help writing the doc ;)13:06
jkiother AIs?13:06
jki513:07
jki413:07
jki313:07
jki213:07
jki113:07
jki#topic Kernel maintenance updates13:07
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:07
masamiThis week reported 128 new CVEs and 40 updated CVEs.13:07
uli_i'm working on 4.413:07
pave1I was reviewing 6.1.134 with a bit of .132 and AUTOSEL.13:07
pave1uli: That gcc crash looks like a lot of fun.13:07
pave1uli: My guess would be that something in headers changed and now trips the compiler bug.13:07
uli_and i absolutely cannot reproduce it, even with the same compiler version.13:08
iwamatsu__I reviewed 6.1.134 and reviewing .13213:08
uli_any suggestions on how to proceed with that? the builds that succeed also work...13:09
pave1uli: It probably counts as a security issue in gcc... so fun. May depend on CPU architecture, for example.13:09
uli_iirc it only happens on arm.13:09
pave1uli: So it works locally but breaks on gitlab?13:09
uli_yes. some configs don't build, some do.13:10
uli_those that build also pass the tests13:10
pave1Easist thing would be to find out what change trips that gcc bug and just not apply that one...13:11
jkithen let's first try to update the compile stable release in the breaking environment13:11
uli_+1. that's a lot less work, too...13:11
jkiwho can do that?13:12
uli_patersonc, i would assume.13:12
jkiask him via the list - but he might be on vacation these weeks13:13
uli_will do.13:13
jkisome fun from the -rt corner, in case you didn't read this yet:13:14
jkihttps://lore.kernel.org/all/20250409120746.635476-1-ziqianlu@bytedance.com/13:14
jkihigh latency for non-rt, RCU stalls for -rt (all versions)13:15
jkionce the series is finished, we will also ask for backports - but < 6.12 is... different13:15
jkiit's one of those "don't use container features on RT" pavel warned about :)13:17
jkianything else?13:17
jki513:17
pave1Yeah. RT is hard. Containers are hard.13:17
jki413:17
jki313:18
jki213:18
jki113:18
jki#topic Kernel release status13:18
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:18
jkiall on track13:18
jkibut some are due very soon13:18
jkiany blockers in sight?13:18
pave1Yep, 4.4-rt.13:18
pave1Nothing unusual.13:19
iwamatsu__I am going to  release 5.10 and 6.1 tomorrow.13:19
jkiperfect13:19
jkithen let's move on13:19
jki513:19
jki413:19
jki313:19
jki213:19
jki113:19
jki#topic Kernel testing13:19
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:19
jkiprobably not much news here today...13:19
arisutcurrently testing config that I'm moving to KernelCI13:20
arisutwith kci_build kernelci internal command13:21
arisutthat's all13:22
jkiok, thanks13:22
jkianyone anything to add?13:23
jki513:23
jki413:23
jki313:23
jki213:23
jki113:23
jki#topic AOB13:23
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:23
pave1 813:23
jkiyes?13:24
jkifurther topics for today?13:25
pave1No, sorry. Stray typo.13:25
jki513:25
jki413:25
jki313:25
jki213:25
jki113:25
jki#endmeeting13:25
collab-meetbotMeeting ended Thu Apr 17 13:25:58 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:25
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/04/cip.2025-04-17-13.01.html13:25
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/04/cip.2025-04-17-13.01.txt13:25
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/04/cip.2025-04-17-13.01.log.html13:25
*** 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:25
jkithank you!13:26
uli_thanks13:26
pave1Thank you!13:26
iwamatsu__thank you13:26
masamithank you13:26
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed)13:26
arisutthx13:26
*** jki <jki!~jki@95.157.49.24> has quit IRC (Quit: Leaving)13:26
*** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:27
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)17:08
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has quit IRC (Ping timeout: 252 seconds)19:45

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