12:01:38 <jki> #startmeeting CIP IRC weekly meeting
12:01:38 <collab-meetbot> Meeting started Thu Jul 23 12:01:38 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:38 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:38 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:44 <jki> #topic AI review
12:01:50 <jki> - start blogpost draft [iwamatsu-san]
12:02:15 <jki> was started, and I also started with leaving some comments
12:02:35 <jki> a general one was missing: structure looks good to me!
12:03:20 <jki> anything to add?
12:03:45 <iwamatsu> jki: thanks! I will check your comments.
12:04:41 <jki> no other AIs on the list, so...
12:04:46 <jki> 5
12:04:49 <jki> 4
12:04:51 <jki> 3
12:04:52 <jki> 2
12:04:54 <jki> 1
12:04:57 <jki> #topic Kernel maintenance updates
12:05:15 <uli> i pushed 4.4, now working on 4.19
12:05:15 <pave1> I am reviewing 6.12.96, .97
12:05:19 <masami> This week reported 442 new CVEs and 5 updated CVEs.
12:05:43 <iwamatsu> I reviewed  6.12.94, and I am reviewing .95
12:06:06 <masami> notable CVE is CVE-2026-64600 that called RefluXFS.
12:06:08 <jki> 442 is not really a new record, but it apparently still made a lot of people unhappy again
12:06:32 <jki> CVE-2026-64600 is another LPE?
12:06:41 <masami> yes.
12:06:43 <masami> https://www.openwall.com/lists/oss-security/2026/07/22/14
12:06:56 <jki> boring :D
12:07:36 <pave1> Well, most of them don't have severity estimation and most are not real.
12:09:37 <jki> RefluXFS is >=4.11... do we have XFS in 4.19 configs? Or will the backport be rather simple?
12:09:55 <uli> xfs is enabled as a module in 4.19 configs
12:10:22 <jki> then we need to look closer
12:10:53 <pave1> ... and we should probably work on getting it disabled :-)
12:11:04 <uli> i'll have a look, i'm dealing with 4.19 now anyway
12:11:27 <jki> good
12:11:55 <jki> more on maintenance?
12:12:14 <jki> 5
12:12:16 <jki> 4
12:12:17 <jki> 3
12:12:19 <jki> 2
12:12:21 <jki> 1
12:12:24 <jki> #topic Kernel release status
12:12:39 <jki> with the 4.19-rt release of today, all green
12:12:46 <jki> any issues ahead?
12:13:08 <jki> 5
12:13:10 <jki> 4
12:13:12 <jki> 3
12:13:13 <pave1> yep. Probably should do next 4.19rt
12:13:14 <jki> 2
12:13:27 <pave1> early to sync.
12:13:46 <jki> earlier than this time, or what do you mean?
12:14:11 <pave1> Yep.
12:14:37 <pave1> Doing it a week before 4.19-cip is not
12:14:41 <pave1> optimal.
12:15:00 <jki> yeah
12:15:37 <jki> should we sync here, or will you bilaterally?
12:15:58 <pave1> I will try to remember.
12:17:23 <jki> ok - I could also try to look at the upcoming schedule and ask you both
12:17:44 <pave1> Reminder in 6 weeks would not be bad.
12:17:59 <jki> let's see :)
12:18:18 <jki> okay, then let's move on
12:18:23 <jki> 3
12:18:25 <jki> 2
12:18:27 <jki> 1
12:18:29 <jki> #topic Kernel testing
12:19:48 <arisut> Not much from me, working on next kci-dev release and Linux plumbers testing and dependability micro conf
12:20:20 <jki> ok, good
12:20:40 <jki> then moving on...
12:20:42 <jki> 5
12:20:45 <jki> 4
12:20:47 <jki> 3
12:20:49 <jki> 2
12:20:51 <jki> 1
12:20:52 <jki> #topic AOB
12:21:13 <jki> quick update on the AI setup: Uli shared details, please have a look if they work for you
12:21:26 <jki> pavel and iwamatsu
12:21:47 <iwamatsu> OK
12:21:56 <pave1> Yep. I mailed ssh key
12:22:04 <jki> performance tuning is a topic in parallel, should not make it unusable
12:22:31 <jki> more topcis for today?
12:22:59 <jki> 5
12:23:01 <jki> 4
12:23:04 <jki> 3
12:23:05 <jki> 2
12:23:07 <jki> 1
12:23:10 <jki> #endmeeting