12:01:08 <jki> #startmeeting CIP IRC weekly meeting
12:01:08 <collab-meetbot> Meeting started Thu Jan 29 12:01:08 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:08 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:08 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:13 <jki> #topic AI review
12:01:20 <jki> none on the list
12:01:25 <jki> 5
12:01:27 <jki> 4
12:01:28 <jki> 3
12:01:30 <jki> 2
12:01:32 <jki> 1
12:01:35 <jki> #topic Kernel maintenance updates
12:01:55 <uli> i pushed 4.19 today, 4.4 is next
12:01:58 <masami> This week reported 56 new CVEs and 2 updated CVEs.
12:02:30 <pave1> I'm doing reviews, 6.12.64, .67, .68.
12:02:34 <iwamatsu> I reviewed 6.12.66
12:04:08 <jki> anything to add?
12:04:37 <jki> 5
12:04:39 <jki> 4
12:04:40 <jki> 3
12:04:42 <jki> 2
12:04:43 <jki> 1
12:04:46 <jki> #topic Kernel release status
12:05:07 <pave1> 6.1-rt is still a problem.
12:05:17 <pave1> I sent email at
12:05:18 <jki> any feedback on any channel?
12:05:19 <pave1> Date: Thu, 22 Jan 2026 12:19:17 +0100
12:05:24 <pave1> Subject: Re: [ANNOUNCE] 6.1.157-rt57
12:05:31 <jki> not via the list, I saw this
12:05:51 <pave1> cc-ed to lists.
12:06:06 <jki> should we offer help to refresh the queue?
12:06:22 <jki> maybe you could try offline first to assess the complexity
12:06:45 <pave1> I'm scared :-). We don't really have good way to test realtime.
12:07:02 <jki> this is no reason to not update
12:07:20 <jki> we have kernelci tests, and we have some downstream users
12:07:22 <pave1> Okay, I can try; with some luck it will just be no conflict.
12:07:33 <jki> in the end, you already do that for 4.19 and 4.4
12:07:43 <jki> exactly
12:07:59 <pave1> Could we get CIP project to talk to Realtime project about expectations etc?
12:08:26 <jki> Clark's maintenance is not paid by the RT project
12:08:33 <jki> it's a RH contribution
12:08:35 <pave1> Maybe we should do 6.1 less often, or maybe we could talk realtime project to release more often or something.
12:08:39 <pave1> Aha.
12:08:52 <jki> but, as I sugested long ago, you could join their calls to sync
12:09:01 <jki> then you know more than what's on the list
12:09:16 <pave1> So I was there few times. It is wrong time at friday afternoon.
12:09:27 <jki> too late?
12:09:37 <jki> ok, that's unfortunate
12:10:15 <pave1> Could we get help from linuxfoundations realtime project here?
12:10:44 <jki> stable is not a direct work so far, only consulting to stable maintainers
12:11:23 <pave1> Ok, unfortunate.
12:11:47 <pave1> Let me take a look at the patches.
12:11:57 <jki> yeah, I may bring that up again on the next regular project meeting, but that is March or April
12:12:25 <jki> another topic - 4.19: regular and -rt releases are a bit out of sync
12:12:42 <pave1> Yes please. Likely update will be easy this iteration, but as likely we'll hit real problem one day.
12:13:19 <jki> can we align the 4.19 release again?
12:13:36 <pave1> jki: Yes. I guess we should eventually do 4.19-rt (and 4.4-rt) not on time-based schedule but simply every second 4.19-cip release.
12:13:50 <jki> e.g.
12:14:47 <pave1> 4.19-cip is out. Ok, I can make -rt release on top of that.
12:15:11 <jki> that would be great
12:15:54 <pave1> Ok, added to the todo list :-).
12:15:59 <jki> thanks!
12:16:08 <jki> anything else on releases?
12:16:35 <jki> 5
12:16:37 <jki> 4
12:16:39 <jki> 3
12:16:40 <jki> 2
12:16:42 <jki> 1
12:16:44 <jki> #topic Kernel testing
12:18:35 <patersonc> Hey
12:18:56 <patersonc> I've been adding beaglev-fire support to kernelci. It's working, just need to check another thing then get the MR merged
12:19:10 <patersonc> I also tried to add qemu-riscv64, but this hit some issues I still need to fix
12:19:59 <patersonc> I guess that's it from me
12:20:00 <pave1> 6.18-stable testing points qemu failures:
12:20:01 <pave1> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/2291978755
12:20:32 <pave1> Is that likely to be real failure or some testing problem?
12:21:05 <jki> iwamatsu: there are some open MRs on cip-kernel-config, please check, one affects the bv-fire
12:21:06 <patersonc> Seems to be unable to mount the file system.
12:21:52 <iwamatsu> jki: Yes I know.  I will check these.
12:22:04 <pave1> Thank you.
12:22:06 <patersonc> qemu issue happened on two different labs, and two different qemu types, so maybe it's not an infrastructure issue?
12:22:57 <jki> "EXT2-fs (vda): error: couldn't mount because of unsupported optional features (2c0)"
12:23:12 <jki> rootfs does not fit to kernel config?
12:23:18 <jki> https://lava.ciplatform.org/scheduler/job/1387035
12:24:37 <jki> maybe we lost a config option in the forward porting to 6.18
12:24:49 <patersonc> It looks like this has been failing on 6.18 stable for a while: https://lava.ciplatform.org/scheduler/alljobs?length=25&search=qemu_arm_defconfig_6.18&search=qemu_arm_defconfig_6.18&length=100#table
12:25:23 <jki> same issue for qemu-arm64
12:25:39 <jki> is that the merged-defconfig or something special?
12:26:15 <patersonc> It's qemu_arm_defconfig
12:26:32 <jki> then there is something missing that
12:27:08 <jki> check the effective ext4 options
12:30:17 <jki> anything else on testing?
12:30:43 <jki> 5
12:30:45 <jki> 4
12:30:47 <jki> 3
12:30:49 <jki> 2
12:30:50 <jki> 1
12:30:52 <jki> #topic AOB
12:30:58 <pave1> Renesas defconfig:
12:31:00 <pave1> https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/merge_requests/157
12:31:25 <pave1> Looks okay to me, but I guess that iwamatsu normally handles configs?
12:31:56 <jki> right
12:32:30 <iwamatsu> I will check it after this meeting.
12:32:35 <pave1> Thank you!
12:33:18 <arisut_> No updates from me
12:34:13 <jki> good - anything else?
12:34:21 <arisut_> Actually one, there is interest on having kci-dev sending results directly to KCIDB
12:35:07 <arisut_> By that kci-dev could be used on kernel maintainer building scripts
12:36:28 <arisut_> so that it can add results direct to kcidb and should solve issues related to kernelci overload
12:36:53 <arisut_> Some kernel maintainer are already interested
12:37:31 <arisut_> Maybe could be used also in the cip kernel maintenance work flow
12:37:35 <jki> is it used by cip maintainers now?
12:38:20 <iwamatsu__> not yet
12:38:23 <arisut_> Is not developed yet, we are working on it. Currently we got feedback from upstream kernel maintainer that could be useful
12:39:27 <arisut_> I actually just got such feedback few minutes ago directly
12:40:49 <jki> ok, great - and even better if cip could benefit from it as well
12:41:28 <arisut_> Yes, that would be nice to integrate on cip gitlab pipeline
12:41:59 <arisut_> Or any other cip building environment
12:43:04 <arisut_> Also we discussed me and Patersonc on what we are Missing on kernelci
12:43:43 <arisut_> About kernelci configuration, but other than some rt problems looks like we are good
12:44:52 <arisut_> That’s all from me
12:45:06 <jki> great, thanks!
12:45:35 <jki> so, done for today?
12:45:45 <arisut_> Yes
12:45:58 <jki> 5
12:46:00 <jki> 4
12:46:01 <jki> 3
12:46:03 <jki> 2
12:46:04 <jki> 1
12:46:06 <jki> #endmeeting