13:02:38 <jki> #startmeeting CIP IRC weekly meeting
13:02:38 <collab-meetbot> Meeting started Thu May  2 13:02:38 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:38 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:38 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:43 <jki> #topic AI review
13:02:48 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:03:05 <jki> [re-]started, but I was too optimistic. so: ongoing
13:03:32 <jki> I don't think we have more AI, so
13:03:35 <jki> 5
13:03:37 <jki> 4
13:03:39 <jki> 3
13:03:40 <jki> 2
13:03:42 <jki> 1
13:03:43 <jki> #topic Kernel maintenance updates
13:03:54 <pave1> I did reviews, 6.1.88 and .90
13:04:09 <pave1> Yesterday was holiday here, May 8th will be another one.
13:06:01 <jki> ok
13:06:17 <jki> how about the 4.19-rt?
13:06:51 <pave1> I'll take a look.
13:07:08 <jki> thanks
13:08:17 <jki> "This week reported 207 new CVEs and 10 updated CVEs." - going up again
13:08:47 <jki> pavel: thanks for summarizing the HW CVEs on the list
13:08:50 <pave1> Yep. And the titles are still copy-pasted so they make no sense in CVE context.
13:09:06 <pave1> jki: No problem, but I did not exactly get a response there.
13:09:29 <jki> at least we warned, no one can complain
13:10:05 <pave1> Yes. There's no way to fix that, anyway. We are just piling workarounds, but underlying bugs are not fixable.
13:10:19 <patersonc> Last week was OSS-NA, so only a few CVEs reported. This week...
13:10:58 <jki> are the CVEs documented as unfixed in our affected kernels?
13:10:59 <uli> hi
13:11:23 <uli> sorry for being late. i'm preparing the next 4.4
13:11:55 <pave1> No, we should probably fix that.
13:12:11 <jki> KNOWN-BUGS is only in 4.4 so far, right?
13:12:23 <pave1> But this whole thing is a bit of mess w.r.t. CVEs.
13:12:32 <jki> well, yes
13:12:51 <jki> but we could at least use that manually for the major CVEs
13:13:21 <pave1> The CVEs should be against the CPUs... but we have CVEs for bug workarounds...
13:13:45 <jki> CVEs are CVEs
13:13:54 <pave1> Well.. These days CVEs are spam.
13:13:56 <pave1> :-(
13:14:25 <pave1> I'll look at KNOWN-BUGS for 4.19/5.10.
13:14:33 <jki> the HW CVEs are unique and properly described, and if we add them to our kernels that do not even have mitigation attempts, that should be clear
13:15:30 <jki> ok - anything else on maintenance?
13:15:38 <pave1> Yes. But my observation is that CVEs start to have "tree structure" in the case of CPU bugs.
13:15:48 <pave1> Intel CPU leaks secrets.
13:16:13 <pave1> Then we have kernel not doing proper workarounds for Intel bug.
13:16:40 <pave1> Plus we know many of the workarounds are just incomplete, they are just patching the exploits at this point.
13:16:51 <pave1> Ok, lets continue.
13:17:07 <jki> 5
13:17:09 <jki> 4
13:17:11 <jki> 3
13:17:12 <jki> 2
13:17:14 <jki> 1
13:17:17 <jki> #topic Kernel release status
13:17:26 <jki> just 4.19-rt is late, we already discussed
13:17:40 <jki> 5
13:17:42 <jki> 4
13:17:44 <jki> 3
13:17:46 <jki> 2
13:17:48 <jki> 1
13:17:49 <jki> #topic Kernel testing
13:19:09 <jki> patersonc: anything from you?
13:19:17 <patersonc> Not really!
13:20:06 <jki> our lab is still in reconstruction, hope to have that fixed "soon"
13:20:18 <patersonc> Thanks, I meant to ask
13:20:55 <jki> on Tuesday, the network socket was without network yet...
13:20:59 <jki> ok
13:21:05 <patersonc> :)
13:21:18 <jki> moving on...
13:21:20 <jki> 5
13:21:21 <jki> 4
13:21:23 <jki> 3
13:21:25 <jki> 2
13:21:27 <jki> 1
13:21:30 <jki> #topic AOB
13:21:56 <jki> the 9th is public holiday here (and possibly also elsewhere)
13:22:02 <jki> I'm out for next week
13:23:11 <pave1> Do we cancel the meeting, or do I just take over it?
13:23:29 <jki> if you can take over, we don't need to cancel
13:23:42 <pave1> Ok, I believe I can do that.
13:23:47 <jki> I suspect, Japan will be back, and if no one else is on leave...
13:23:49 <jki> thanks!
13:24:50 <jki> anything else for today?
13:25:00 <jki> 5
13:25:02 <jki> 4
13:25:03 <jki> 3
13:25:05 <jki> 2
13:25:07 <jki> 1
13:25:08 <jki> #endmeeting