12:03:22 <jki> #startmeeting CIP IRC weekly meeting
12:03:22 <collab-meetbot`> Meeting started Thu Nov 24 12:03:22 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:03:22 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:03:22 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:03:32 <jki> #topic AI review
12:03:40 <jki> 1. Add qemu-riscv to cip-kernel-config - patersonc
12:03:53 <patersonc[m]> no updates
12:04:01 <jki> 2. Create MR for disabling smc test in qemu - alicef
12:04:13 <alicef> sent pr waiting for review
12:04:19 <alicef> https://github.com/kernelci/kernelci-core/pull/1516
12:04:35 <jki> perfect, thanks!
12:04:42 <jki> other AI-related topics?
12:04:46 <alicef> np
12:05:09 <jki> 3
12:05:11 <jki> 2
12:05:13 <jki> 1
12:05:15 <jki> #topic Kernel maintenance updates
12:05:44 <pave1> I did reviews on 5.10.156, and 4.4 work, to be discussed in next section :-).
12:05:47 <uli> reviewed 4.4-st
12:05:56 <masami> This week reported 5 new CVEs and 3 updated CVEs. No critical issues in stable kernels.
12:05:58 <iwamatsu> I am reviewing 5.10.156-rc.
12:07:47 <masami> FYI: Retbleed bug(CVE-2022-23816, CVE-2022-29900, CVE-2022-29901) was fixed in 4.19.
12:09:05 <pave1> I'd preffer saying "worked around" or "partly worked around" when talking about retbleed.
12:09:38 <pave1> AFAICT right tool to fix it is electron microscope, and practical solution is "switch to RISC-V".
12:11:00 <masami> I see. we don't have good regression test tool for it :(
12:11:59 <pave1> Yes and we don't have a fix for it, either. We can stop some practical exploits for the kernel, but the issue is in the silicon and may be exploitable elsewhere.
12:13:15 <masami> that's true.
12:15:23 <jki> anything else to discuss?
12:15:51 <pave1> Waiting for next section for more discussion :-).
12:15:57 <jki> 3
12:16:02 <jki> 2
12:16:04 <jki> 1
12:16:07 <jki> #topic Kernel release status
12:16:23 <jki> 4.4
12:16:39 <pave1> So.. 4.4-cip should be ready for release. Iwamatsu-san was doing those, can I ask for one?
12:17:31 <iwamatsu> Yes, I will do it.
12:17:37 <pave1> I took a look at 4.4-rt, too, and this time there are rt-specific changes.
12:17:39 <pave1> Thank you!
12:18:02 <pave1> Fortunately the rt-specific changes in 4.9 seem to be backport to put it better in sync with mainline.
12:18:27 <pave1> So I suggest to first do 4.4-rt release without them, and then evaluate what to do next.
12:19:31 <jki> so, those changes are not related to regular LTS changes, rather fixes or small improvements?
12:20:35 <pave1> Well, not sure I'd call them small. But they are not related to LTS change, so 4.4-rt should work as well as before w/o them.
12:20:51 <pave1> They change locking in workqueue code, so it is mildly scary stuff.
12:21:08 <jki> ok
12:21:40 <jki> good - then we should have 4.4 refreshments within the next days, right?
12:21:46 <patersonc[m]> Sorry all, I have to head off for another appointment. I don't have anything to report on the testing side of things
12:22:00 <pave1> Yes, that's the plan.
12:22:07 <jki> patersonc[m]: thanks!
12:22:16 <alicef> patersonc[m]: see you, thanks
12:22:21 <jki> then move on
12:22:24 <jki> 4.19
12:22:40 <iwamatsu> I am preparing for tomorrow's release.
12:23:03 <jki> RT is not due yet IIRC
12:23:17 <pave1> jki: that's my understanding, too.
12:23:53 <jki> 0.5 per month, next one in January
12:23:56 <jki> 5.10
12:24:07 <iwamatsu> same as 4.19.
12:24:31 <iwamatsu> and RT is same status with 4.19.
12:24:48 <pave1> -rt should be due in December.
12:24:53 <jki> exactly
12:24:56 <jki> good
12:25:24 <jki> #topic Kernel testing
12:25:40 <jki> nothing from chris - anything from anyone else?
12:26:11 <alicef> nothing other than the pr
12:26:46 <alicef> I asked for been reviewed
12:27:36 <alicef> and show to fbezdeka how we track cip pr on kernelci
12:27:47 <fbezdeka> Thanks!
12:28:01 <alicef> for reference: all CIP related issues are tracked by https://github.com/orgs/kernelci/projects/11 as per CIP instance documentation https://kernelci.org/docs/instances/cip/
12:28:25 <alicef> fbezdeka: no problem
12:29:27 <alicef> also both PR and Issue about CIP need to be labeled as cip
12:31:42 <fbezdeka> With disablement of smc test we should move one step closer to "no reportings for 4.4"
12:35:11 <jki> anything else?
12:35:24 <jki> on testing
12:35:58 <jki> 3
12:36:00 <jki> 2
12:36:01 <jki> 1
12:36:06 <jki> #topic AOB
12:38:12 <jki> nothing from my side - anyone anything?
12:39:27 <jki> 3
12:39:29 <jki> 2
12:39:32 <jki> 1
12:39:38 <jki> #endmeeting