12:00:54 #startmeeting CIP IRC weekly meeting 12:00:54 Meeting started Thu Nov 5 12:00:54 2026 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:00:54 The meeting name has been set to 'cip_irc_weekly_meeting' 12:00:59 #topic AI review 12:01:29 there is actually one: draft of improved patch review process 12:01:38 any news on that? 12:01:59 Yep, I need to find a time to write it down. But I'm starting to have ideas :-) 12:02:10 ok 12:02:19 nothing else otherwise 12:02:24 5 12:02:26 4 12:02:27 3 12:02:29 2 12:02:30 1 12:02:33 #topic Kernel maintenance updates 12:02:47 i'm working on 4.4 12:02:50 This week reported 44 new CVEs and 1383 updated CVEs. 12:03:05 I was reviewing 6.12.115... and CVE-2026-98432, CVE-2026-99999. 12:03:06 I was on vacation until Tuesday, so I have not been reviewing patches. 12:03:38 ok - more news? 12:03:49 5 12:03:51 4 12:03:52 3 12:03:54 2 12:03:56 1 12:03:58 #topic Kernel release status 12:04:06 so, 4.4 is WIP 12:04:11 what about 4.19? 12:04:16 4.19 is under review atm 12:04:21 by whom? 12:04:24 pave1: 12:04:31 pavel: status? 12:04:47 lot's of patches, right? 12:04:53 I'm looking at it. 12:04:58 90 of them, yes. 12:05:25 this obviously has prio 12:05:50 Ok. 12:06:14 The pm_runtime_resume_and_get()... as we already have two users in 4.19 (but no function) 12:06:25 it might make sense to just provide pm_runtime_resume_and_get(). 12:06:36 It may even be easier than teaching AI not to backport that. 12:07:22 i don't particularly like that, but i think you might have a point there... 12:08:30 Yeah, neither solution is great. 12:09:14 I'm working on 5.10.272-cip79-rt35. (Early, because of CVEs and availability of matching -cip and -rt). 12:09:30 good 12:09:35 There's real conflict there, I may need to get Renesas to help/review the result. 12:09:48 already ping'ed them? 12:10:16 Not yet. Still more work to do on my side. 12:10:55 anything else about releases? 12:11:08 5 12:11:10 4 12:11:12 3 12:11:14 2 12:11:16 1 12:11:17 #topic Kernel testing 12:11:34 Hello 12:11:37 Not much news from me 12:12:01 any open issues around testing? 12:12:36 5 12:12:37 I had "7.3-stable testing is failing" on my list, but that one seemed to solve itself in the meantime. 12:12:58 4 12:12:59 It was waiting for a cip-kernel-config MR 12:13:12 Aha. Great that one is solved. 12:13:37 3 12:13:39 2 12:13:42 1 12:13:44 #topic AOB 12:13:56 security.my: what's next? 12:14:08 anything still open? 12:14:54 It feels wrong to have two files describing what to do with security bugs in the tree, and giving different advice. 12:16:01 they are referencing and explaining their relationship 12:16:15 not much from me either 12:16:30 ...in v2 12:16:55 but I asked for better concrete proposal, might have missed them 12:17:44 Need to take second look, sorry. 12:18:16 good, TIA 12:18:20 further topics? 12:18:31 aristu: IIRC topic for #cip still says wrong time for the meeting. Can that be fixed? 12:19:16 ? 12:19:51 Right now, topic is "AOB (Meeting topic: CIP IRC weekly meeting)". 12:20:12 But I believe it will get longer (and wrong) after we end the meeting. 12:20:21 And I don't believe I have rights to fix that. 12:21:00 still no idea what you mean - this is like it always was 12:21:27 I guess I talk to arisut after the meeting. I believe he has the permissions. 12:21:34 Two more things: 12:21:39 TSC is in about 40 minutes? 12:21:52 yes, exceptionally 12:22:17 yes can be fixed 12:22:27 Can we agree that whoever sees "bad" CVE sends separate mail to cip-dev with CVE-XX-YY in the subject? 12:23:02 just like we can agree on announcing kernel releases the same way? ;) 12:23:49 but we can try this, of course 12:24:17 Currently it is "[ANNOUNCE] v1.2.3-cip4-rt5", let me know if you want different one. I'll try to keep it stable. 12:24:35 just compare the announcement emails 12:25:02 (hint: yours are different) 12:25:11 Point was not in particular format, CVE-2026-98432 was announced on the list, but I learned about CVE-2026-99999 from the irc 12:25:31 so that few days later than I'd like. 12:26:17 does the -99999 have real number by now? 12:26:52 yes 12:27:01 PwnEscape 12:27:06 will be fun to find once counting reaches it 12:27:09 that's not a number :) 12:27:22 yes, it was a placeholder 12:28:55 I did not realize number was not real. We'll get to that number soon. 12:29:08 exactly 12:30:57 Did quick searches, and you seem to want [ANNOUNCE] v1.2.3 => [ANNOUNCE] Release v1.2.3 . I can do that :-) 12:32:01 hmm, it is actually that number: https://lore.kernel.org/linux-cve-announce/2026101533-CVE-2026-99999-beee@gregkh/ 12:33:03 was from the reserved pool, thus not contiguous 12:33:08 anyway 12:33:17 pavel: TIA! 12:33:26 further topics for today? 12:34:07 5 12:34:09 4 12:34:11 3 12:34:13 2 12:34:16 1 12:34:17 #endmeeting