| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 09:25 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 09:35 | |
| *** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip | 12:54 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:36cb:fffc:80c:f0f> has joined #cip | 12:59 | |
| *** jki_ <jki_!~jki@62.156.206.54> has joined #cip | 13:00 | |
| jki_ | hi all | 13:00 |
|---|---|---|
| uli_ | hello | 13:00 |
| masami | hello | 13:00 |
| pave1 | Hi! | 13:01 |
| arisut | hi | 13:01 |
| jki_ | let's start | 13:01 |
| iwamatsu__ | hello | 13:01 |
| jki_ | #startmeeting CIP IRC weekly meeting | 13:01 |
| collab-meetbot | Meeting started Thu Feb 20 13:01:37 2025 UTC and is due to finish in 60 minutes. The chair is jki_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:01 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:01 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki_ | #topic AI review | 13:01 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki_ | none recorded | 13:01 |
| jki_ | 5 | 13:02 |
| jki_ | 4 | 13:02 |
| jki_ | 3 | 13:02 |
| jki_ | 2 | 13:02 |
| jki_ | 1 | 13:02 |
| jki_ | #topic Kernel maintenance updates | 13:02 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| uli_ | no updates from me this week | 13:02 |
| pave1 | I was reviewing 6.1.129. | 13:02 |
| masami | This week reported 20 new CVEs and 2 updated CVEs. | 13:02 |
| iwamatsu__ | I am reviewing 6.1.129. | 13:02 |
| masami | I am currently implementing a process to extract version information for commits such as "fixed-by". | 13:02 |
| jki_ | as already written in the invitation, this is relevant for our old RT kernels: | 13:04 |
| jki_ | https://lore.kernel.org/stable-rt/CAMLffL-PTp+Y-rXsTFaC5cUJyMMiXk-Gjx59WiQvcTe46rXFrw@mail.gmail.com/T/#m67dce3408cac40318ae3dbe1c713b13621ac66c9 | 13:04 |
| jki_ | should also come via stable-rt at some point, but as that channel already lost it (partially) | 13:04 |
| pave1 | Ok, let me take a look. | 13:06 |
| jki_ | anything else? | 13:07 |
| jki_ | 5 | 13:07 |
| jki_ | 4 | 13:07 |
| jki_ | 3 | 13:07 |
| jki_ | 2 | 13:07 |
| jki_ | 1 | 13:07 |
| jki_ | #topic Kernel release status | 13:07 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:07 | |
| jki_ | was all green today - good :) | 13:08 |
| pave1 | Good :-). | 13:08 |
| jki_ | then let's move on | 13:09 |
| jki_ | 5 | 13:09 |
| jki_ | 4 | 13:09 |
| jki_ | 3 | 13:09 |
| jki_ | 2 | 13:09 |
| jki_ | 1 | 13:09 |
| jki_ | #topic Kernel testing | 13:09 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:09 | |
| patersonc | Hey, sorry I'm late | 13:09 |
| patersonc | I don't think I have any updates this week anyway | 13:09 |
| arisut | Relesed kci-dev v0.1.3 with some fixes for bisection command and results | 13:09 |
| arisut | https://kci.dev/ | 13:10 |
| arisut | this is now the link of kci-dev documentation | 13:10 |
| jki_ | I'd like to bring the testing topic of RT up again (this week) | 13:13 |
| jki_ | the issue cited above was visible with the right nft settings and lockdep | 13:13 |
| jki_ | is RT, ours or upstream, also running with lockdep on? | 13:14 |
| jki_ | in kernelci or our lab? | 13:14 |
| jki_ | yes, it still needs code paths to be run, but if lockdep is even off... | 13:15 |
| patersonc | Is that a kernel config thing? | 13:15 |
| jki_ | also | 13:15 |
| jki_ | but lockdep is (hopefully) not found in any contributed member production configs | 13:15 |
| jki_ | it's rather a "testing overlay" | 13:16 |
| patersonc | We can check what KernelCI does - I know they run more tests then we do | 13:16 |
| arisut | yes, but I don't remember if lockdep is enabled | 13:17 |
| arisut | we should check it | 13:17 |
| pave1 | Yep so... people should not be running lockdep in production. | 13:17 |
| jki_ | would be good to understand what was missing to let this commit slip through | 13:17 |
| pave1 | And I would not be surprised if lockdep increased latencies somewhere. | 13:17 |
| jki_ | yes, but people should run it during QA | 13:17 |
| jki_ | for correctness checking | 13:17 |
| pave1 | Yes; we likely want lockdep on to see if it find anything, and then lockdep off to see what the real latencies are :-(. | 13:18 |
| jki_ | the commit-triggered Xenomai pipelines run will almost all debug switches enabled, always | 13:18 |
| jki_ | exactly | 13:18 |
| jki_ | functional vs. non-functional testing | 13:18 |
| jki_ | just that the funcitonal tests luckily rarely need to run for days ;) | 13:19 |
| jki_ | who could have a look in kernelci? | 13:19 |
| jki_ | and we can already rule out that our lab has that enabled, right? | 13:20 |
| patersonc | Yea, CIP doesn't | 13:20 |
| arisut | jki_, KernelCI looks like is using CONFIG_PROVE_LOCKING | 13:21 |
| jki_ | that's what I was looking for, yes | 13:22 |
| arisut | with CONFIG_LOCKDEP | 13:22 |
| arisut | https://github.com/kernelci/kernelci-core/blob/2b4433eeb8ae18274e43c4c806350f1efe4d3a5b/config/core/build-configs.yaml#L495 | 13:22 |
| jki_ | then we were "only" missing the code path that the patch above is touching | 13:22 |
| jki_ | and that kcidebug is surely applied on all input kernels? just to double-check the logic | 13:23 |
| arisut | only machine that allow defconfig+kcidebug | 13:25 |
| pave1 | Well, its netfilter. That is not going to be easy to test. Plus I really hope people are not expecting realtime performance on network routing, because I'm pretty sure we can't do that :-). | 13:25 |
| jki_ | no, "just" correctness when having such a firewall rule on an some edge device with container & co + RT | 13:26 |
| jki_ | "normal" setup... | 13:26 |
| jki_ | we are currently trying to reproduce the case artificially | 13:27 |
| jki_ | lockdep was triggering immediately, though - with the right nftable settings | 13:27 |
| arisut | not sure about what is currently running with kcidebug | 13:27 |
| jki_ | we don't need to clarify now | 13:28 |
| jki_ | but it would be important that some pipeline with the CIP RT kernels would also have lock validation enabled | 13:28 |
| pave1 | +1 | 13:28 |
| jki_ | for now at least | 13:28 |
| jki_ | good | 13:28 |
| jki_ | let's check offline and revisit next time | 13:29 |
| pave1 | But please don't mix containers + realtime + expectations it will work together flawlessly :-). | 13:29 |
| jki_ | too late :) | 13:29 |
| pave1 | It still not too late to adjust the expectations :-)_ | 13:29 |
| jki_ | more testing topics for today? | 13:30 |
| jki_ | 5 | 13:32 |
| jki_ | 4 | 13:32 |
| jki_ | 3 | 13:32 |
| jki_ | 2 | 13:32 |
| jki_ | 1 | 13:32 |
| jki_ | #topic AOB | 13:32 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:32 | |
| jki_ | anything for today? | 13:34 |
| jki_ | 5 | 13:34 |
| jki_ | 4 | 13:34 |
| jki_ | 3 | 13:34 |
| jki_ | 2 | 13:34 |
| jki_ | 1 | 13:34 |
| jki_ | #endmeeting | 13:35 |
| collab-meetbot | Meeting ended Thu Feb 20 13:35:01 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:35 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-20-13.01.html | 13:35 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-20-13.01.txt | 13:35 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-20-13.01.log.html | 13:35 |
| *** 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:35 | |
| jki_ | thanks, folks! | 13:35 |
| uli_ | thanks | 13:35 |
| iwamatsu__ | Thank you | 13:35 |
| masami | thank you | 13:35 |
| pave1 | Thank you! | 13:35 |
| *** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:35 | |
| arisut | thanks | 13:35 |
| *** jki_ <jki_!~jki@62.156.206.54> has quit IRC (Ping timeout: 248 seconds) | 14:32 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:36cb:fffc:80c:f0f> has quit IRC (Quit: Client closed) | 15:08 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Ping timeout: 244 seconds) | 20:46 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!