12:02:38 <pave1> #startmeeting CIP IRC weekly meeting
12:02:38 <collab-meetbot`> Meeting started Thu Aug  3 12:02:38 2023 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:02:38 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:02:38 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:02:52 <pave1> #topic AI review
12:03:01 <pave1> 1. create kernelci pipeline for buster images (arisut)
12:03:18 <pave1> Skip, as arisut is not here.
12:03:25 <pave1> 2. draft press release on 6.1 release (jan)
12:03:29 <pave1> Skip.
12:03:34 <pave1> Anything else?
12:03:49 <pave1> 3
12:03:52 <pave1> 2
12:03:52 <pave1> 1
12:04:04 <pave1> #topic Kernel maintenance updates
12:04:13 <uli> reviewing 6.1.39
12:04:21 <masami> This week reported 3 new CVEs and 10 updated CVEs.
12:04:31 <iwamatsu> I am reviewing 6.1.43.
12:04:32 <pave1> I'm reviewing 6.1.40, 42, 43.
12:05:31 <pave1> I'll be travelling next week.
12:05:47 <pave1> 3
12:05:48 <pave1> 2
12:05:50 <pave1> 1
12:06:05 <pave1> #topic Kernel release status
12:06:17 <pave1> -4.4
12:06:33 <uli> i'll fix up the missing bits and then it's ready to release
12:06:42 <uli> thanks for the reviews
12:06:54 <pave1> Good. I should do -rt, too.
12:07:01 <pave1> Thanks for the patches!
12:07:12 <pave1> -4.19
12:07:46 <iwamatsu> on track
12:08:17 <pave1> -rt is still on track, but should do release when we get a match
12:08:32 <pave1> -5.10
12:08:50 <iwamatsu> on track
12:08:50 <pave1> -rt is still on track
12:08:56 <pave1> -6.1
12:09:01 <pave1> on track
12:09:19 <iwamatsu> on track, lts and rt
12:09:25 <pave1> -rt is on track, too.
12:09:28 <pave1> good.
12:09:29 <pave1> 3
12:09:30 <pave1> 2
12:09:32 <pave1> 1
12:09:39 <pave1> #topic Kernel testing
12:09:45 <pave1> If someone from testing team is here, speak up.
12:10:15 <pave1> 3
12:10:16 <pave1> 2
12:10:16 <pave1> 1
12:10:23 <pave1> #topic AOB
12:10:35 <masami> I joined CIP security team meeting to talk about cip-kernel-sec. I got some feedback from them.
12:10:57 <masami> I think some requests were reported from the team in the last TSC meeting.
12:11:29 <pave1> I'll be travelling next week, but jki should be here to lead the meeting.
12:11:40 <pave1> masami: Yes, there was some discussion there.
12:11:50 <pave1> Thanks for doing this!
12:12:07 <pave1> Is there anything we should be changing soon?
12:13:02 <pave1> ...with respect to security?
12:13:05 <masami> pavel: It'd be nice to have document about patch back porting policy
12:13:45 <masami> Sometimes we ask TSC to not backport pactches such as meltdown/spectre bugs.
12:14:19 <pave1> masami: We are trying to follow -stable rules, but even those are poorly documented.
12:15:05 <pave1> We are basically using -stable as our upstream, so if -stable drops the patch, we don't even review it.
12:15:39 <pave1> Then we drop those that don't apply, unless it looks easy and critical.
12:15:47 <masami> pavel: yes. -stable rule is one of our rule.
12:17:29 <masami> One of important task would be polish document.
12:17:48 <pave1> I guess someone could periodically check the CVE database we maintain to see if we missed something "really bad"
12:18:16 <pave1> Yes, they'll want documentation and we don't have a good one.
12:18:46 <masami> cip-kernel-sec uses debian and ubuntu's security tracker to get CVE information
12:19:31 <masami> but I found some CVEs (CVE-2022-3533 and CVE-2022-3606 ) are not tracked them
12:19:44 <pave1> Fun :-(.
12:19:59 <masami> libbpf can be created from kernel source or libbpf's git repo.
12:20:12 <pave1> I guess we should discuss it on cip-dev so that jki sees the discussion?
12:20:30 <masami> yes. move to mailing list.
12:21:35 <pave1> Anything else?
12:21:37 <pave1> 5
12:21:40 <pave1> 4
12:21:41 <pave1> 3
12:21:42 <pave1> 2
12:21:42 <pave1> 1
12:21:47 <masami> I'll be absent next week
12:22:08 <pave1> Noted, thank you.
12:22:19 <pave1> I may or may not be able to make it.
12:22:29 <pave1> #endmeeting