13:02:29 <jki> #startmeeting CIP IRC weekly meeting
13:02:29 <collab-meetbot> Meeting started Thu Apr 25 13:02:29 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:29 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:29 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:33 <jki> #topic AI review
13:02:39 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:02:59 <jki> after traveling and then moving, I will now start working on this :)
13:03:08 <jki> promised
13:03:17 <jki> other AIs from the last week?
13:03:27 <jki> 5
13:03:29 <jki> 4
13:03:30 <jki> 3
13:03:32 <jki> 2
13:03:33 <jki> 1
13:03:36 <jki> #topic Kernel maintenance updates
13:03:57 <masami> This week reported 10 new CVEs and 6 updated CVEs.
13:03:58 <uli> i've been reviewing autosel patches
13:04:20 <pave1> Reviewing 6.1.88 and investigating Spectre - related CVEs.
13:05:04 <pave1> There's actually three of them, one is unfixed in mainline, one is fixed in stable-5.10 and one is fixed in stable-6.1.
13:05:27 <pave1> Backporting either does not seem particulary easy.
13:05:41 <pave1> I'll send email with details on cip-dev...?
13:07:04 <jki> sounds good to me, yes
13:07:57 <jki> FYI: I chatted with someone maintaining kernels at AWS during EOSS, and he really liked our CVE tracking, it would be very valuable to him
13:09:03 <masami> jki: i'm happy to hear that!
13:09:56 <jki> we asked him for free EC2 time in return ;) - but it seems there is even an official way to request that as OSS project, Neal is on that
13:10:31 <pave1> BTW... how much time are we using in EC2.
13:10:54 <pave1> Is that approximately equivalent to... say 16core running 24/7?
13:11:32 <jki> patersonc: may have details
13:11:37 <patersonc> I don't have the numbers right now
13:11:58 <pave1> Ok.
13:12:04 <patersonc> But more than that.
13:12:28 <jki> and it comes in bursts, not permanent workload
13:12:40 <patersonc> Say, in Feb we had about 560 hours of EC2 for building kernels/cip core over the month
13:13:21 <pave1> So that's less than one machine, right? I see bursts are problem.
13:14:41 <jki> ok, other maintenance topics?
13:15:01 <jki> 5
13:15:02 <jki> 4
13:15:04 <jki> 3
13:15:05 <jki> 2
13:15:07 <jki> 1
13:15:09 <jki> #topic Kernel release status
13:15:26 <jki> with the last 4.19 release, we are all good now
13:15:45 <jki> any problems in sight?
13:16:19 <jki> if not, moving on...
13:16:21 <jki> 5
13:16:23 <jki> 4
13:16:25 <jki> 3
13:16:27 <jki> 2
13:16:29 <jki> 1
13:16:31 <jki> #topic Kernel testing
13:17:50 <arisut> no update from me
13:18:23 <arisut> patersonc: any update on the merge with kernelci?
13:18:48 <jki> seitze had to move to different topics, you likely heard already
13:18:50 <patersonc> arisut: None, sorry
13:19:49 <patersonc> I've been looking (with Michael) into some gitlab-runner issues that were causing EC2 instances to keep running longer than they should be.
13:19:59 <patersonc> And reviewing some cip-core testing MRs
13:20:35 <patersonc> No updates on anything else really, other than what jki said
13:21:55 <jki> good - moving on...
13:22:00 <jki> 5
13:22:02 <jki> 4
13:22:04 <jki> 3
13:22:07 <jki> 2
13:22:09 <jki> 1
13:22:11 <jki> #topic AOB
13:23:19 <jki> anything else?
13:23:33 <jki> 5
13:23:35 <jki> 4
13:23:37 <jki> 3
13:23:39 <jki> 2
13:23:41 <jki> 1
13:23:43 <jki> #endmeeting