Thursday, 2025-02-13

« Wednesday, 2025-02-12 Index Friday, 2025-02-14 »
*** thommey <thommey!thommey@lib.so> has quit IRC (Ping timeout: 252 seconds)05:12
*** thommey <thommey!thommey@lib.so> has joined #cip05:24
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:55
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)07:11
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Quit: Konversation terminated!)08:56
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has joined #cip08:57
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip11:50
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip12:53
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:2d88:722b:5ed5:5f48> has joined #cip12:56
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:2d88:722b:5ed5:5f48> has quit IRC (Client Quit)12:56
patersoncAfternoon13:01
pave1hi!13:01
masamihi13:01
arisuthi13:01
uli_hello13:02
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:2d88:722b:5ed5:5f48> has joined #cip13:03
iwamatsu__hello13:04
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Read error: Connection reset by peer)13:05
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip13:05
iwamatsu__has it started yet?13:05
arisutno13:05
pave1I don't think so.13:05
pave1seems jki is not around?13:06
iwamatsu__jki is not here.13:06
iwamatsu__ok, I will takeover today13:06
pave1thank you!13:07
iwamatsu__#startmeeting CIP IRC weekly meeting13:07
collab-meetbotMeeting started Thu Feb 13 13:07:24 2025 UTC and is due to finish in 60 minutes.  The chair is iwamatsu__. Information about MeetBot at http://wiki.debian.org/MeetBot.13:07
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:07
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:07
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:07
iwamatsu__#topic AI review13:07
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:07
iwamatsu__no AI on mail from jki.13:08
iwamatsu__anything missed?13:08
iwamatsu__513:08
iwamatsu__413:08
iwamatsu__313:08
iwamatsu__213:08
iwamatsu__113:08
iwamatsu__#topic Kernel maintenance updates13:08
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:08
pave1I was reviewing 6.1.129, now I'm working on autosel.13:08
uli_i did 4.4 and 4.1913:09
masamiThis week reported 20 new CVEs and 0 updated CVEs.13:09
uli_thanks for the reviews!13:09
iwamatsu__I am reviewing 6.1.129.13:09
pave1thanks for releases!13:09
iwamatsu__uli_: Thanks for release.13:09
*** jki <jki!~jki@95.157.49.24> has joined #cip13:10
jkihi - and sorry for the delay13:10
jkimeeting already started?13:10
iwamatsu__We already recieved some patch for 4.19.y13:10
iwamatsu__jki: Yes, I takeover.13:10
jkithanks!13:10
iwamatsu__nop13:11
iwamatsu__Do we need an announcement for 4.19.y?13:12
uli_didn't i send one?13:12
iwamatsu__https://lore.kernel.org/cip-dev/1733593115.596079.1739239912119@webmail.strato.de/T/#u13:13
iwamatsu__> This is the first 4.19 release maintained exclusively by CIP.13:14
uli_was that too subtle? :)13:14
iwamatsu__uli_: I see, OK.13:14
iwamatsu__sorry for this noise.13:15
iwamatsu__anything else?13:15
iwamatsu__513:15
iwamatsu__413:15
iwamatsu__313:15
iwamatsu__213:15
iwamatsu__113:15
iwamatsu__#topic Kernel release status13:15
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:15
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)13:16
pave1I'll do 6.1-cip and 6.1.128-rt. january was a little late so this catches it up.13:16
iwamatsu__pave1: thank you.13:16
iwamatsu__I am working for linux-5.10.y13:17
iwamatsu__linux-4.4.y-cip-rt is late.13:17
uli_4.4 and 4.19 are done13:17
pave1aha, ok, let me do 4.4-rt, too.13:17
iwamatsu__ok, thank you.13:18
iwamatsu__anything else?13:18
iwamatsu__513:18
iwamatsu__413:18
iwamatsu__313:18
iwamatsu__213:18
iwamatsu__113:18
iwamatsu__#topic Kernel testing13:18
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:18
patersoncHowdy13:19
arisutno updates from me. working on kci-dev bisections and KernelCI blog13:19
patersoncI started to look at the device that wasn't booting with 6.6 last week13:19
patersoncBut then it seems that it's working with 6.6 again now - so I guess something got fixed?13:19
pave1scary :-)13:20
iwamatsu__same version?13:20
patersoncFixed between rc2 and the final release13:20
patersoncI forget the exact version13:20
pave1But I guess if it went away we don't need to debug that.13:20
patersoncI certainly don't plan to :P13:21
iwamatsu__if we want to take a reason, we need to run bisect..., but it is not important.13:21
patersoncyep13:21
patersonciwamatsu__ did you get a chance to look into an LTP rootfs for the x86 / MCOM board?13:21
iwamatsu__patersonc: OK, I will take a look.13:22
patersoncThanks13:22
patersoncI guess nothing else from my side13:23
jkiI would have an RT testing topic13:23
jkidoes anyone already know this: https://github.com/Linutronix/RTC-Testbench?13:23
patersoncI didn't13:24
jkiI would have the proposal to build up end-to-end RT testing this way, first for x8613:24
jkilater for other archs/boards supporting XDP RT networking this way13:24
jki(and a bit of TSN)13:25
patersoncFun13:25
jkiwould stress both RT workloads (similar to cyclictest, though) AND RT I/O via network13:25
jkisetup is not totally straightforward, also because it will need two boxes obviously13:25
jkibut it could be rewarding for our RT testing13:26
patersoncSure13:26
pave1If it uncovers somethin, it will be 'fun' to debugg.13:26
jkiI'm not sure if KernelCI is already prepared to handle something like this as well, so I would start small in our domain first13:26
iwamatsu__I am interesting this.13:26
pave1but yes, more testing is needed for rt.13:27
iwamatsu__+113:27
jkiregarding RT testing: have you seen this backport of my colleague? https://lore.kernel.org/stable/20250129153226.818485-1-florian.bezdeka@siemens.com/13:27
patersoncw.r.t kernelCI perhaps open an issue in their github about it?13:27
jkiI was able to trigger that (harmless) warning withing no time by booting a plain debian-rt 6.1 kernel in a VM13:27
jkiit is not just that our setup is improveable...13:28
jkishould we open the kernelci issue already now, or better try out first in our lab?13:29
arisuthttps://lore.kernel.org/all/20250211090511.xeFJVnH_@linutronix.de/13:30
arisut PREEMPT_RT testing on kernelci13:30
jkiarisut: thanks for the pointer13:31
jkilet me read...13:31
iwamatsu__anything missed?13:31
iwamatsu__513:32
iwamatsu__413:32
iwamatsu__313:32
iwamatsu__213:32
iwamatsu__113:32
iwamatsu__#topic AOB13:32
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:32
paulbarkerHi folks, I have two questions - the first is about the cip-kernel-config repo, from the point-of-view of backporting support for Renesas SoCs13:32
paulbarkerWhen a CIP release is tagged in linux-cip, there is no corresponding tag in cip-kernel-config so it can be difficult to match up the two repositories when looking at an old CIP release.13:32
paulbarkerIs there anything we can do to improve that? My preference would be to move the CIP kernel configs in to the appropriate branches of linux-cip so they are always aligned with the rest of the tree.13:32
arisuttldr KernelCI is starting to implement preempt_rt testing but still on the implementation phase13:33
pave1we normally don't update configs when kernel changes13:33
pave1I see renesas backports will need that.13:33
jkiwe have some kind of lock-stepping in isar-cip-core13:34
paulbarkerpave1: We need to update the config when we backport a new driver which has a new Kconfig option13:34
jkias we have both the configs and the kernel referenced there by versions13:34
pave1latest config should work on the corresponding -cip branch.13:34
pave1but yes, we should probably use same tags we do on kernel there.13:35
jkibut how often will that actually happen?13:36
pave1(and if change in config breaks something on older -cip kernels, we should be extra careful. Does that happen?)13:36
jkiis this case a one-off or can it really repeat more often in the future?13:36
paulbarkerpave1: cip-kernel-config may have newer config symbols enabled which don't exist in Kconfig files in older releases13:36
pave1suggestion would be only put tag into configs when it needs to change, after corresponding release.13:36
pave1paul: yes, that's expected. But that won't cause any real problems, right?13:37
pave1warning at oldconfig time or something... we can live with that.13:37
pave1just warn us if you rename a symbol or something...13:38
paulbarkerOk, let's think about it, may come back to it next week13:38
paulbarkerSecond question, I have a CVE fix to backport to 4.4 & 4.19, should I be targeting the -cip or -st branches?13:38
pave1-st.13:39
iwamatsu__-st13:39
paulbarkerThanks, I'll try to do the backport tomorrow13:39
pave1thank you :-)13:39
jkiI have some CVE-related thing as well13:40
iwamatsu__paulbarker: thank you13:40
iwamatsu__jki: please13:40
jkilearned that my CERT colleagues are happily consuming our CVE yaml files :)13:40
jkithey just asked (so far) if we could easily also write down the cip-kernel versions that received fixes, not only the commit shas13:41
jkino idea how much effort that would be, though13:41
pave1git can do that.13:41
jkiyeah, we know13:41
jkibut that is another step that downstream has to script then13:41
jki(i gave the same answer initially)13:42
pave1yes and it may slow things down a bit.13:42
masamiAdded fixed version in yaml files may be easy to users.13:42
pave1but it seems like reasonable request.13:43
masamiI'll create sample yaml file which contains version informaion.13:44
jkiwould that be something to automate in the end?13:44
masamiyes. it has to be automated.13:45
jkimasami: thanks in advance!13:45
masamijki: np :)13:45
iwamatsu__anything else?13:45
iwamatsu__513:46
iwamatsu__413:46
iwamatsu__313:46
iwamatsu__213:46
iwamatsu__113:46
iwamatsu__#endmeeting13:46
collab-meetbotMeeting ended Thu Feb 13 13:46:23 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:46
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-13-13.07.html13:46
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-13-13.07.txt13:46
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-13-13.07.log.html13:46
*** 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 13: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/"13:46
iwamatsu__Thank you13:46
masamithank you13:46
pave1Thank you!13:46
jkithanks all - and thanks for jumping in, iwamatsu :)13:46
uli_thanks13:46
iwamatsu__jki: :-)13:47
arisutthx13:47
paulbarkerThanks!13:47
patersoncttfn13:49
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:2d88:722b:5ed5:5f48> has quit IRC (Quit: Client closed)13:49
*** jki <jki!~jki@95.157.49.24> has quit IRC (Quit: Leaving)13:49
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:58
« Wednesday, 2025-02-12 Index Friday, 2025-02-14 »

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