*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 05: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 #cip | 06:55 | |
*** tmerciai <tmerciai!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has joined #cip | 07:30 | |
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 10: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 #cip | 12:35 | |
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has joined #cip | 12: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 #cip | 12:57 | |
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:58 | |
*** jki <jki!~jki@95.157.49.24> has joined #cip | 13:00 | |
jki | hi all | 13:00 |
---|---|---|
uli_ | hello | 13:00 |
masami | hi | 13:00 |
pave1 | hi! | 13:00 |
iwamatsu__ | hi | 13:01 |
jki | ok, let's go | 13:01 |
jki | #startmeeting CIP IRC weekly meeting | 13:01 |
collab-meetbot | Meeting 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-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
collab-meetbot | The 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 review | 13: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 |
pave1 | I took a look. They'd need a bit of docs and quite a lot of documenting prerequisites. | 13:02 |
pave1 | Plus, trying to modify someone else's shell code ... is not easy. | 13:03 |
iwamatsu__ | pave1: OK, I will create a document. | 13:04 |
pave1 | Mainly directory tree it expects to work in would be useful. | 13:04 |
jki | ok, then there is clear next step | 13:06 |
jki | further concrete wisches/feedback may also help writing the doc ;) | 13:06 |
jki | other AIs? | 13:06 |
jki | 5 | 13:07 |
jki | 4 | 13:07 |
jki | 3 | 13:07 |
jki | 2 | 13:07 |
jki | 1 | 13:07 |
jki | #topic Kernel maintenance updates | 13:07 |
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:07 | |
masami | This week reported 128 new CVEs and 40 updated CVEs. | 13:07 |
uli_ | i'm working on 4.4 | 13:07 |
pave1 | I was reviewing 6.1.134 with a bit of .132 and AUTOSEL. | 13:07 |
pave1 | uli: That gcc crash looks like a lot of fun. | 13:07 |
pave1 | uli: 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 .132 | 13:08 |
uli_ | any suggestions on how to proceed with that? the builds that succeed also work... | 13:09 |
pave1 | uli: 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 |
pave1 | uli: 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 tests | 13:10 |
pave1 | Easist thing would be to find out what change trips that gcc bug and just not apply that one... | 13:11 |
jki | then let's first try to update the compile stable release in the breaking environment | 13:11 |
uli_ | +1. that's a lot less work, too... | 13:11 |
jki | who can do that? | 13:12 |
uli_ | patersonc, i would assume. | 13:12 |
jki | ask him via the list - but he might be on vacation these weeks | 13:13 |
uli_ | will do. | 13:13 |
jki | some fun from the -rt corner, in case you didn't read this yet: | 13:14 |
jki | https://lore.kernel.org/all/20250409120746.635476-1-ziqianlu@bytedance.com/ | 13:14 |
jki | high latency for non-rt, RCU stalls for -rt (all versions) | 13:15 |
jki | once the series is finished, we will also ask for backports - but < 6.12 is... different | 13:15 |
jki | it's one of those "don't use container features on RT" pavel warned about :) | 13:17 |
jki | anything else? | 13:17 |
jki | 5 | 13:17 |
pave1 | Yeah. RT is hard. Containers are hard. | 13:17 |
jki | 4 | 13:17 |
jki | 3 | 13:18 |
jki | 2 | 13:18 |
jki | 1 | 13:18 |
jki | #topic Kernel release status | 13:18 |
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:18 | |
jki | all on track | 13:18 |
jki | but some are due very soon | 13:18 |
jki | any blockers in sight? | 13:18 |
pave1 | Yep, 4.4-rt. | 13:18 |
pave1 | Nothing unusual. | 13:19 |
iwamatsu__ | I am going to release 5.10 and 6.1 tomorrow. | 13:19 |
jki | perfect | 13:19 |
jki | then let's move on | 13:19 |
jki | 5 | 13:19 |
jki | 4 | 13:19 |
jki | 3 | 13:19 |
jki | 2 | 13:19 |
jki | 1 | 13:19 |
jki | #topic Kernel testing | 13:19 |
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:19 | |
jki | probably not much news here today... | 13:19 |
arisut | currently testing config that I'm moving to KernelCI | 13:20 |
arisut | with kci_build kernelci internal command | 13:21 |
arisut | that's all | 13:22 |
jki | ok, thanks | 13:22 |
jki | anyone anything to add? | 13:23 |
jki | 5 | 13:23 |
jki | 4 | 13:23 |
jki | 3 | 13:23 |
jki | 2 | 13:23 |
jki | 1 | 13:23 |
jki | #topic AOB | 13:23 |
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:23 | |
pave1 | 8 | 13:23 |
jki | yes? | 13:24 |
jki | further topics for today? | 13:25 |
pave1 | No, sorry. Stray typo. | 13:25 |
jki | 5 | 13:25 |
jki | 4 | 13:25 |
jki | 3 | 13:25 |
jki | 2 | 13:25 |
jki | 1 | 13:25 |
jki | #endmeeting | 13:25 |
collab-meetbot | Meeting 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-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/04/cip.2025-04-17-13.01.html | 13:25 |
collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/04/cip.2025-04-17-13.01.txt | 13:25 |
collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/04/cip.2025-04-17-13.01.log.html | 13: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 | |
jki | thank you! | 13:26 |
uli_ | thanks | 13:26 |
pave1 | Thank you! | 13:26 |
iwamatsu__ | thank you | 13:26 |
masami | thank you | 13:26 |
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 13:26 | |
arisut | thx | 13: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/!