| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 06:00 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 258 seconds) | 06:06 | |
| *** frieder <frieder!~frieder@88.130.219.68> has joined #cip | 06:29 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 257 seconds) | 07:00 | |
| *** 092AACNJW <092AACNJW!~tmerciai@188.217.49.6> has joined #cip | 07:01 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.49.6> has joined #cip | 07:33 | |
| *** 092AACNJW <092AACNJW!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 260 seconds) | 07:35 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.49.6> has quit IRC (Read error: Connection reset by peer) | 07:57 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.49.6> has joined #cip | 07:58 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 253 seconds) | 08:04 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.49.6> has joined #cip | 08:04 | |
| *** frieder <frieder!~frieder@88.130.219.68> has quit IRC (Ping timeout: 260 seconds) | 08:15 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 260 seconds) | 08:17 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.49.6> has joined #cip | 08:18 | |
| *** frieder <frieder!~frieder@88.130.219.84> has joined #cip | 08:28 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.49.6> has quit IRC (Read error: Connection reset by peer) | 08:33 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.49.6> has joined #cip | 08:34 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 09:07 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 267 seconds) | 09:14 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.49.6> has joined #cip | 09:15 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.49.6> has joined #cip | 09:46 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.49.6> has quit IRC (Read error: Connection reset by peer) | 09:46 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 268 seconds) | 10:04 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.49.6> has joined #cip | 10:04 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 257 seconds) | 10:12 | |
| *** noctux <noctux!~noctux@user/noctux> has quit IRC (Read error: Connection reset by peer) | 11:05 | |
| *** noctux <noctux!~noctux@user/noctux> has joined #cip | 11:07 | |
| *** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has joined #cip | 11:51 | |
| *** jki <jki!~jki@195.145.170.149> has joined #cip | 11:55 | |
| jki | hi! | 11:59 |
|---|---|---|
| pave1 | Hi! | 11:59 |
| iwamatsu | Hello | 11:59 |
| masami | hello | 11:59 |
| patersonc | Hey | 12:00 |
| jki | #startmeeting CIP IRC weekly meeting | 12:00 |
| collab-meetbot` | Meeting started Thu Sep 17 12:00:42 2026 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:00 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:00 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:00 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:00 | |
| jki | #topic AI review | 12:00 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:00 | |
| jki | none (I had an AI, but it's already done) | 12:01 |
| jki | 5 | 12:01 |
| jki | 4 | 12:01 |
| jki | 3 | 12:01 |
| jki | 2 | 12:01 |
| jki | 1 | 12:01 |
| jki | #topic Kernel maintenance updates | 12:01 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| masami | This week reported 706 new CVEs and 71 updated CVEs. | 12:01 |
| pave1 | I was doing reviews. 6.12.109, 110. .110 is huge. | 12:01 |
| iwamatsu | I reviewed 6.12.102 and 103 | 12:02 |
| jki | sounds like it es getting harder and harder to keep up with that pace | 12:03 |
| pave1 | Yep :-(. | 12:04 |
| jki | do we need more reviewers earlier? | 12:04 |
| jki | topic for the CIP MiniSummit? | 12:04 |
| jki | are there stats if our reviews also find more? | 12:04 |
| jki | relatively or absolutely? | 12:04 |
| pave1 | I'd say so. And we need infrastructure to coordinate reviews better, as patches arrive for different versions at different times. | 12:05 |
| jki | did you do any upfront coordination so far, or was that basically this slot here? | 12:05 |
| pave1 | No such stats :-(. | 12:06 |
| pave1 | We had git to coordinate with uli, but it did not work too well. | 12:06 |
| patersonc | I saw that 7.2.6 had over 1800 patches, on an rc release on Sat morning. Not sure how that was ever expected to have a manual review before the release on Monday... | 12:06 |
| jki | hmm... | 12:07 |
| pave1 | Ideally, we would track changes by their upstream id, with some support to flag how it was reviewed for different versions. | 12:07 |
| jki | in git? | 12:08 |
| jki | or where? | 12:08 |
| pave1 | ...and warnings if patch is actually different from what is in the upstream. | 12:08 |
| pave1 | ...and notes about LLM reviews and such. | 12:08 |
| pave1 | Dunno. Git is good for offline work, web interface would also make a sense. | 12:08 |
| pave1 | I guess we have CIP minisummit topic. | 12:09 |
| jki | you need to operate it, so you should tell | 12:09 |
| jki | but I will record that for discussions in Prague | 12:10 |
| pave1 | Someone needs to design and implement that, too :-). | 12:10 |
| *** arisut <arisut!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo) | 12:10 | |
| pave1 | It might make sense to allow outside contributions, too. | 12:10 |
| jki | also AI? :) | 12:10 |
| iwamatsu | It is true that there are no good tools available right now. | 12:11 |
| *** arisut <arisut!~none@gentoo/developer/alicef> has joined #cip | 12:11 | |
| *** ChanServ sets mode: +o arisut | 12:11 | |
| pave1 | I guess this is a place where LLM would fit, yes. | 12:11 |
| jki | would indeed be a nice chance for more contributors to the CIP kernel | 12:12 |
| jki | but we need to be able to express requirements on it | 12:12 |
| jki | good... | 12:12 |
| pave1 | And outside human contributors. (Or perhaps contributions from CIP members.) | 12:12 |
| jki | more on maintenance? | 12:12 |
| jki | sure | 12:13 |
| jki | let's move on | 12:13 |
| jki | 5 | 12:13 |
| jki | 4 | 12:13 |
| jki | 3 | 12:13 |
| jki | 2 | 12:13 |
| jki | 1 | 12:13 |
| jki | #topic Kernel release status | 12:13 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:13 | |
| jki | all green now - thanks pavel | 12:14 |
| jki | upcoming releases: 4.4 and 6.12 | 12:14 |
| jki | (based on due dates) | 12:14 |
| pave1 | :-). 5.10-rt has very regular releases, which helps. | 12:14 |
| *** arisut <arisut!~none@gentoo/developer/alicef> has quit IRC (Client Quit) | 12:15 | |
| jki | 5 | 12:15 |
| jki | 4 | 12:15 |
| jki | 3 | 12:15 |
| jki | 2 | 12:15 |
| jki | 1 | 12:15 |
| jki | #topic Kernel testing | 12:15 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:15 | |
| patersonc | Hi | 12:15 |
| patersonc | Still seeing some issues with some qemu jobs in the stable-rc testing | 12:16 |
| *** arisut <arisut!~none@gentoo/developer/alicef> has joined #cip | 12:16 | |
| *** ChanServ sets mode: +o arisut | 12:16 | |
| patersonc | Not got to the bottom of it yet | 12:16 |
| pave1 | Yep. I retried old -rt kernel, and it still failed, so I decided failures on new -rt kernels are spurious and released anyway. | 12:17 |
| jki | qemu issues due to long delays caused by an overloaded host? | 12:19 |
| jki | or functional, deterministic problems? | 12:19 |
| patersonc | I doubt it's due to an overloaded host tbh | 12:20 |
| patersonc | Seems to be a lava issue more than anything, but no idea why | 12:20 |
| patersonc | e.g. https://lava.ciplatform.org/scheduler/job/1509187 | 12:20 |
| jki | "/lava-1509187/environment: No such file or directory" - infrastructure, no? | 12:21 |
| jki | always on the same qemu device, or in the same lab? | 12:21 |
| patersonc | I don't think it's a specific lab - but need to run more tests to work it out for sure | 12:23 |
| iwamatsu | same issue has on siemens-muc https://lava.ciplatform.org/scheduler/job/1509925 | 12:23 |
| jki | mount: /lava-1509187: special device /dev/disk/by-uuid/b6a7ee8d-e0f5-46ba-9e18-286229ea2076 does not exist. | 12:23 |
| jki | missing /dev/disk/...? missing kernel features? missing disk? | 12:24 |
| jki | someone needs to try that out manually, I guess | 12:24 |
| jki | but if older kernels failed the same way, config can likely be excluded | 12:25 |
| patersonc | yea | 12:25 |
| patersonc | Could be related to the qemu version upgrade we did recently | 12:25 |
| jki | if it only popped up recently - could be | 12:28 |
| jki | but the muc lab was not updated yet IIRC | 12:28 |
| iwamatsu | It looks like a file system issue. ext2 might be the problem. | 12:29 |
| iwamatsu | https://lava.ciplatform.org/scheduler/job/1509925#L1010 | 12:29 |
| jki | but it says it does not find the block device | 12:30 |
| jki | not "unknown / unsupported fs" | 12:30 |
| jki | the muc lab is definitely still old QEMU, just confirmed | 12:31 |
| jki | but we might be missing that extra disk in the qemu command line - for whatever reason | 12:31 |
| jki | that would also explain the missing blockdev | 12:31 |
| jki | welllll - debug volunteers? | 12:32 |
| iwamatsu | I see. | 12:32 |
| jki | otherwise, ask the AI ;) | 12:34 |
| jki | more on testing? | 12:34 |
| arisut | About AI and testing this is the guide for using kci-dev with KernelCI mcp server https://kernelci.org/blog/2026/09/12/talk-to-kernelci-kci-dev-now-speaks-mcp/ | 12:34 |
| patersonc | Should git in nicely with some LLM driven regression testing :) | 12:35 |
| jki | indeed | 12:35 |
| jki | nice article, just distributed | 12:36 |
| jki | we need someone with time to see if we can safe time this way, I guess ;) | 12:37 |
| jki | more testing topics? | 12:38 |
| jki | 5 | 12:38 |
| jki | 4 | 12:38 |
| jki | 3 | 12:38 |
| jki | 2 | 12:38 |
| jki | 1 | 12:38 |
| jki | #topic AOB | 12:38 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:38 | |
| jki | SECURITY.md - did you see my patch? | 12:39 |
| jki | https://lore.kernel.org/cip-dev/a1cfc8d4-5fb7-4f75-9600-92ebd7dbbeda@siemens.com/ | 12:39 |
| jki | unless someone has a better idea, we likely need to place that into every active CIP kernel | 12:40 |
| pave1 | There already is Documentation/admin-guide/security-bugs.rst . | 12:40 |
| jki | LF asked us | 12:40 |
| jki | that is not CIP related | 12:40 |
| jki | this is not the upstream kernel, it is the CIP kernel, and it is differently managed | 12:41 |
| pave1 | Yep, well, but we don't want to give our users two conflicting documents. | 12:41 |
| jki | we could, of course, also augment that file, likely in addition | 12:41 |
| jki | the kernel's file is very hard to find, at least for humans | 12:42 |
| pave1 | I'd say that for 6.12-cip, most security bugs will be in -stable, not in -cip code. | 12:42 |
| iwamatsu | How about using a clear file name for the CIP document? | 12:42 |
| jki | pavel: please read my text | 12:42 |
| pave1 | You can do ln -s Documentation/admin-guide/security-bugs.rst SECURITY.md | 12:43 |
| jki | actually, I'm currently pointing to that security.rst already, but via kernel.org | 12:44 |
| jki | so, we could replace it, and that link would still work | 12:44 |
| jki | or we augment it with a sentence that repeats bits of what I wrote in "Security Context" | 12:45 |
| jki | does that section make sense to you, BTW? | 12:45 |
| jki | anything missing or unclear? | 12:45 |
| jki | also the rest of that file - please re-read and comment on the patch | 12:46 |
| pave1 | Ok, lets do that over email? | 12:46 |
| jki | fine for me | 12:48 |
| jki | should just not take forever, reporting obligations are in place now | 12:48 |
| jki | (for CIP with LF as steward) | 12:48 |
| jki | good | 12:49 |
| pave1 | well... my first impression is not good. | 12:49 |
| pave1 | LF is not willing to list name or gpg key for the steward. | 12:49 |
| pave1 | That seems to be doing ... bare minimum, not a real security. | 12:49 |
| jki | kernel list does not either | 12:49 |
| jki | we don't have a shared GPG key for our list as well | 12:50 |
| jki | and on gitlab (or github), the platform is always a reader | 12:50 |
| pave1 | I was under impression that security@kernel.org had key published, but I could be wrong. | 12:50 |
| jki | I didn't find anything in their docs, but please check again | 12:51 |
| jki | keys are tricky when you have multiple readers | 12:51 |
| pave1 | security is tricky. | 12:51 |
| jki | of course | 12:52 |
| jki | so - as uli is not here, no support on llm review topics possible | 12:52 |
| jki | but anything new to share about that? | 12:52 |
| jki | if not, any other topcis for today? | 12:54 |
| jki | 5 | 12:54 |
| jki | 4 | 12:54 |
| jki | 3 | 12:54 |
| jki | 2 | 12:54 |
| jki | 1 | 12:54 |
| jki | #endmeeting | 12:54 |
| collab-meetbot` | Meeting ended Thu Sep 17 12:54:42 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:54 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/09/cip.2026-09-17-12.00.html | 12:54 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/09/cip.2026-09-17-12.00.txt | 12:54 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/09/cip.2026-09-17-12.00.log.html | 12:54 |
| *** 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/" | 12:54 | |
| jki | thanks all! | 12:54 |
| pave1 | Thank you! | 12:54 |
| iwamatsu | Thank you. | 12:54 |
| masami | thank you | 12:54 |
| *** jki <jki!~jki@195.145.170.149> has quit IRC (Quit: Leaving) | 12:55 | |
| *** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:55 | |
| *** sskartheekadivi3 <sskartheekadivi3!~sskarthee@user/sskartheekadivi> has quit IRC (Ping timeout: 252 seconds) | 14:40 | |
| *** sskartheekadivi3 <sskartheekadivi3!~sskarthee@user/sskartheekadivi> has joined #cip | 15:07 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 241 seconds) | 15:17 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.49.6> has joined #cip | 15:17 | |
| *** frieder <frieder!~frieder@88.130.219.84> has quit IRC (Remote host closed the connection) | 16:04 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 260 seconds) | 16:42 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.49.6> has joined #cip | 16:43 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.49.6> has quit IRC (Ping timeout: 268 seconds) | 17:22 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.49.6> has joined #cip | 17:23 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!