12:01:45 <jki> #startmeeting CIP IRC weekly meeting
12:01:45 <collab-meetbot`> Meeting started Thu Dec 11 12:01:45 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:45 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:45 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:53 <jki> #topic AI review
12:02:04 <jki> list was empty again...
12:02:10 <jki> 5
12:02:12 <jki> 4
12:02:13 <jki> 3
12:02:15 <jki> 2
12:02:16 <jki> 1
12:02:18 <jki> #topic Kernel maintenance updates
12:02:25 <masami> This week reported 313 new CVEs and 18 updated CVEs.
12:02:32 <pave1> I was doing reviews: 6.1.61, and renesas stuff.
12:02:45 <pave1> And trying to figure out what to do with 4.19-rt (and 6.1-rt).
12:02:46 <jki> iwamatsu wrote: I reviewed 6.12.60.
12:03:43 <jki> anything to add?
12:03:54 <jki> 5
12:03:56 <jki> 4
12:03:57 <jki> 3
12:03:59 <jki> 2
12:04:00 <jki> 1
12:04:02 <jki> #topic Kernel release status
12:04:27 <jki> two are late, 5.10 should pick up soon
12:04:45 <pave1> 4.19-rt: I searched other branches to see if someone had to deal with the conflict, but was not successful.
12:05:30 <jki> is the issue somewhere visible? maybe my colleague Florian can help with looking around
12:05:39 <pave1> I believe the best way is to release -rt without the conflicting fix from 4.19-cip, document that, and search for solution after the release.
12:06:19 <pave1> We have commit 79f919a89c9d06816dbdbbd168fa41d27411a7f9 cgroup: split cgroup_destroy_wq into 3 workqueues
12:06:39 <pave1> Conflicting with commit 8990cf9c6a65d3d8937db69da5ecd6985c32aa52 cgroups: use simple wait in css_release()
12:07:22 <jki> looks not overly critical for production on first sight, indeed
12:07:29 <pave1> Basically -rt modified code to use different primitive, and -stable split the wq into 3 pieces.
12:08:29 <pave1> Yep, -stable commit actually has good explanation, it is cgrou + perf_event + net_prio.
12:08:47 <jki> + testsuite, de facto
12:08:55 <pave1> interaction.
12:09:29 <pave1> Yeah, testing whatever merged version would be an issue, too, as this seems to need quite specific environment.
12:09:56 <jki> then let's go for your proposal, I would say
12:10:03 <pave1> Good :-).
12:10:43 <jki> then - move on...
12:10:45 <pave1> 6.1-rt is soon, I may need to do 6.1-cip to get a match, but I guess that's okay with everyone.
12:11:48 <jki> in general yes, I would just let iwamatsu know as he is not here today
12:12:48 <pave1> Yep. Also 6.1-rt is month old at this point, if new one appears, that would be great.
12:13:43 <jki> 6.1-stable was late as well, like other stable kernels
12:13:57 <jki> there was wave of releases this weekend
12:14:03 <pave1> jki: There seems to be a trend.
12:14:14 <jki> we need to synchronize then
12:14:33 <pave1> jki: It looks like -stable team was busy, so they kept releasing 6.12-rt but ignored older ones.
12:14:57 <pave1> Now they synched up before merge window closing, as it is less busy period  for thm.
12:15:03 <pave1> I expect this to repeat in future.
12:15:43 <jki> ask them, then you know for sure :)
12:16:16 <jki> but, again, -rt can't release much news of -stable did not release either
12:16:26 <pave1> This is what happened in the past, too.
12:17:11 <jki> then let's synch now and hope it will hold for a while
12:17:25 <pave1> I believe there was -stable release available, but... I'll need to update, look at versions, and figure things out.
12:17:59 <jki> there was none in November for <6.6 IIRC
12:19:12 <jki> good - more on this?
12:19:30 <jki> 5
12:19:32 <jki> 4
12:19:34 <jki> 3
12:19:35 <jki> 2
12:19:37 <jki> 1
12:19:39 <jki> #topic Kernel testing
12:19:57 <jki> testing team is at dinner, I guess :)
12:20:03 <patersonc> Yep
12:20:14 <jki> oh!
12:20:22 <jki> enjoy
12:20:31 <patersonc> :)
12:20:34 <pave1> Thanks for 6.17 testing, btw! :-)
12:20:48 <patersonc> I remembered for once!
12:21:07 <patersonc> I'll report more testing updates next week
12:21:29 <jki> that's fine - thanks!
12:21:58 <jki> then let's move on
12:22:01 <jki> 5
12:22:03 <jki> 4
12:22:05 <jki> 3
12:22:07 <jki> 2
12:22:09 <jki> 1
12:22:11 <jki> #topic AOB
12:22:33 <jki> any other topic for today?
12:23:00 <jki> 5
12:23:02 <jki> 4
12:23:04 <jki> 3
12:23:06 <jki> 2
12:23:08 <jki> 1
12:23:09 <jki> #endmeeting