Thursday, 2022-11-24

*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip05:53
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:7ff:3d8:8a6f:4103> has joined #cip07:08
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip07:31
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Read error: Connection reset by peer)09:49
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip09:58
*** uli <uli!~uli@175.176.15.148> has joined #cip10:03
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip11:48
pave1Hi!12:00
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip12:00
iwamatsuhi12:00
ulihello12:00
masamihi12:00
alicefmhi12:00
fbezdekahi12:00
patersonc[m]Hello12:01
*** jki <jki!~jki@195.145.170.174> has joined #cip12:01
jkihi all!12:01
masamihi12:02
iwamatsuhi12:02
pave1Hi! We also have uli, alicefm, fbezdeka, patersonc.12:02
jkiah, great12:03
jkithen we can start12:03
jki#startmeeting CIP IRC weekly meeting12:03
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
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:03
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:03
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:03
jki#topic AI review12:03
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:03
jki1. Add qemu-riscv to cip-kernel-config - patersonc12:03
patersonc[m]no updates12:03
jki2. Create MR for disabling smc test in qemu - alicef12:04
alicefsent pr waiting for review12:04
alicefhttps://github.com/kernelci/kernelci-core/pull/151612:04
jkiperfect, thanks!12:04
jkiother AI-related topics?12:04
alicefnp12:04
jki312:05
jki212:05
jki112:05
jki#topic Kernel maintenance updates12:05
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:05
pave1I did reviews on 5.10.156, and 4.4 work, to be discussed in next section :-).12:05
ulireviewed 4.4-st12:05
masamiThis week reported 5 new CVEs and 3 updated CVEs. No critical issues in stable kernels.12:05
iwamatsuI am reviewing 5.10.156-rc.12:05
masamiFYI: Retbleed bug(CVE-2022-23816, CVE-2022-29900, CVE-2022-29901) was fixed in 4.19.12:07
pave1I'd preffer saying "worked around" or "partly worked around" when talking about retbleed.12:09
pave1AFAICT right tool to fix it is electron microscope, and practical solution is "switch to RISC-V".12:09
masamiI see. we don't have good regression test tool for it :(12:11
pave1Yes 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:11
masamithat's true.12:13
jkianything else to discuss?12:15
pave1Waiting for next section for more discussion :-).12:15
jki312:15
jki212:16
jki112:16
jki#topic Kernel release status12:16
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:16
jki4.412:16
pave1So.. 4.4-cip should be ready for release. Iwamatsu-san was doing those, can I ask for one?12:16
iwamatsuYes, I will do it.12:17
pave1I took a look at 4.4-rt, too, and this time there are rt-specific changes.12:17
pave1Thank you!12:17
pave1Fortunately the rt-specific changes in 4.9 seem to be backport to put it better in sync with mainline.12:18
pave1So I suggest to first do 4.4-rt release without them, and then evaluate what to do next.12:18
jkiso, those changes are not related to regular LTS changes, rather fixes or small improvements?12:19
pave1Well, 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
pave1They change locking in workqueue code, so it is mildly scary stuff.12:20
jkiok12:21
jkigood - then we should have 4.4 refreshments within the next days, right?12:21
patersonc[m]Sorry all, I have to head off for another appointment. I don't have anything to report on the testing side of things12:21
pave1Yes, that's the plan.12:22
jkipatersonc[m]: thanks!12:22
alicefpatersonc[m]: see you, thanks12:22
jkithen move on12:22
jki4.1912:22
iwamatsuI am preparing for tomorrow's release.12:22
jkiRT is not due yet IIRC12:23
pave1jki: that's my understanding, too.12:23
jki0.5 per month, next one in January12:23
jki5.1012:23
iwamatsusame as 4.19.12:24
iwamatsuand RT is same status with 4.19.12:24
pave1-rt should be due in December.12:24
jkiexactly12:24
jkigood12:24
jki#topic Kernel testing12:25
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:25
jkinothing from chris - anything from anyone else?12:25
alicefnothing other than the pr12:26
alicefI asked for been reviewed12:26
alicefand show to fbezdeka how we track cip pr on kernelci12:27
fbezdekaThanks!12:27
aliceffor 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
aliceffbezdeka: no problem12:28
alicefalso both PR and Issue about CIP need to be labeled as cip12:29
fbezdekaWith disablement of smc test we should move one step closer to "no reportings for 4.4"12:31
jkianything else?12:35
jkion testing12:35
jki312:35
jki212:36
jki112:36
jki#topic AOB12:36
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:36
jkinothing from my side - anyone anything?12:38
jki312:39
jki212:39
jki112:39
jki#endmeeting12:39
collab-meetbot`Meeting ended Thu Nov 24 12:39:38 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:39
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-24-12.03.html12:39
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-24-12.03.txt12:39
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-24-12.03.log.html12:39
*** collab-meetbot` changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/""12:39
pave1Thank you!12:39
iwamatsuThank you12:39
ulithanks12:39
jkithank you all! have a nice day12:39
masamithank you12:39
fbezdekaThanks!12:39
alicefthanks you12:40
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving)12:43
*** jki <jki!~jki@195.145.170.174> has quit IRC (Quit: Leaving)12:47
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip12:47
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:7ff:3d8:8a6f:4103> has quit IRC (Remote host closed the connection)13:29
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:6d94:ade4:eb23:667b> has joined #cip13:30
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:6d94:ade4:eb23:667b> has quit IRC (Client Quit)13:35
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:35
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 260 seconds)19:14
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip19:46
patersonc[m]Hi all, just to let you know, lab-cip-denx has been offline today, and will be at least until tomorrow due to a power outage.21:41
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)22:21
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 256 seconds)23:01

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!