12:01:20 <jki> #startmeeting CIP IRC weekly meeting
12:01:20 <collab-meetbot`> Meeting started Thu Jun 18 12:01:20 2026 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:20 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:20 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:29 <jki> #topic AI review
12:01:33 <arisut> hi
12:01:40 <jki> - AI extra budget [jan]
12:01:47 <jki> requested
12:01:58 <jki> waiting for the board now
12:02:14 <jki> no other AIs on the list
12:02:21 <jki> 5
12:02:22 <jki> 4
12:02:24 <jki> 3
12:02:26 <jki> 2
12:02:28 <jki> 1
12:02:29 <jki> #topic Kernel maintenance updates
12:02:43 <masami> This week reported 1 new CVEs and 0 updated CVEs.
12:02:57 <pave1> I was reviewing 6.12.93 and .94.
12:04:02 <jki> more on this?
12:04:17 <jki> 5
12:04:19 <jki> 4
12:04:21 <jki> 3
12:04:23 <jki> 2
12:04:25 <jki> 1
12:04:27 <jki> #topic Kernel release status
12:04:37 <jki> all on track!
12:04:42 <pave1> Yay! :-)
12:04:56 <jki> was 6.1-rt released upstream, or did you do yourself?
12:05:09 <pave1> It was released upstream, at pretty convenient time.
12:05:16 <jki> perfect :)
12:05:19 <pave1> At some point, we may want to check that all
12:05:32 <pave1> "big name" vulnerabilities are now patched, and perhaps announce that.
12:05:48 <pave1> (Assuming "big name" is over for at least a week).
12:06:14 <jki> no "bummsrakete" for Linux in sight? :D
12:06:54 <jki> yep, I agree, such summary would be good
12:07:15 <pave1> What is bummsrakete ?
12:07:16 <pave1> 
12:07:16 <pave1> 
12:07:16 <pave1> Gemini said
12:07:16 <pave1> "Bummsrakete" is a German slang term. It is a compound word combining "bumms" (a colloquial, slang term often related to a loud bang, a crash, or sexually explicit contexts) and "Rakete" (rocket). Because of its vulgar and sexually explicit connotation in German slang, I cannot provide further details, definitions, or examples of its usage.
12:07:49 <jki> https://bumsrake.de/
12:08:11 <pave1> Aha!
12:08:46 <pave1> That actually sounds similar to the existing wave of vulnerabilities in Linux.
12:09:04 <pave1> Same "we use something obscure to modify in-memory copy of executables", AFAICT.
12:09:08 <jki> yes, just funnier in presentation
12:09:30 <jki> same type of LPE via shared caches
12:09:34 <pave1> Yes.
12:10:12 <pave1> I seen the pages but did not remember the name, I do not know enough about german slang for it to be memorable.
12:10:59 <jki> anyway
12:11:06 <jki> more on releases?
12:11:30 <jki> 5
12:11:32 <jki> 4
12:11:34 <jki> 3
12:11:36 <jki> 2
12:11:37 <jki> 1
12:11:40 <jki> #topic Kernel testing
12:12:21 <patersonc> Hello, Munich LAVA lab is back online with 3/4 boards online. TI lab is currently offline
12:12:49 <patersonc> Not sure I have  any further update
12:14:25 <jki> will clarify why our IPC is offline
12:14:55 <jki> ok, anything to add?
12:15:13 <jki> 5
12:15:16 <jki> 4
12:15:18 <jki> 3
12:15:20 <jki> 2
12:15:22 <jki> 1
12:15:24 <jki> #topic AOB
12:15:31 <pave1> Something changed in -stable. In 2025, patches reached 5.10, 6.1 and 6.12 at roughly same time, and roughly in same order. That no longer seems to be the case, and we may need to adapt. Likely we should go from patch to -stable commit, and then review that in context of 5.10 kernel (etc). Some automation would be nice, for example flagging changes in the patch between mainline and -stable, and between different -stable kernels.
12:17:37 <jki> is this off since that recent LPE hektic, or did that evolve before?
12:17:43 <arisut> not much from me also
12:18:07 <pave1> Rougly at same time.
12:18:34 <jki> then let's observe if that pattern sticks
12:18:50 <pave1> Yes, that's easiest.
12:19:14 <pave1> Oh, also, 7.1.1 is out, so we may want to start testing 7.1-stable branch.
12:19:20 <jki> right!
12:19:38 <patersonc> oh yes, thank you for the reminder
12:20:35 <jki> further topics for today?
12:21:07 <jki> 5
12:21:09 <jki> 4
12:21:11 <jki> 3
12:21:13 <jki> 2
12:21:15 <jki> 1
12:21:17 <jki> #endmeeting