| *** dl9pf <dl9pf!sid395223@user/dl9pf> has quit IRC (Server closed connection) | 01:28 | |
| *** dl9pf <dl9pf!sid395223@user/dl9pf> has joined #cip | 01:28 | |
| *** zar <zar!~quassel@mail.nazaryev.ru> has quit IRC (Server closed connection) | 02:23 | |
| *** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip | 02:23 | |
| *** \x <\x!~user@user/x/x-2225033> has quit IRC (Server closed connection) | 05:46 | |
| *** \x <\x!~user@user/x/x-2225033> has joined #cip | 05:46 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.57.116> has joined #cip | 08:06 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.57.116> has quit IRC (Ping timeout: 241 seconds) | 08:12 | |
| *** 082AAAGBC <082AAAGBC!~tmerciai@188.217.57.116> has joined #cip | 08:12 | |
| *** frieder <frieder!~frieder@88.130.219.74> has joined #cip | 08:16 | |
| *** 082AAAGBC <082AAAGBC!~tmerciai@188.217.57.116> has quit IRC (Ping timeout: 240 seconds) | 08:20 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.57.116> has joined #cip | 08:20 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.57.116> has quit IRC (Remote host closed the connection) | 08:34 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.57.116> has joined #cip | 08:34 | |
| *** frieder <frieder!~frieder@88.130.219.74> has quit IRC (Remote host closed the connection) | 09:07 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.57.116> has quit IRC (Ping timeout: 244 seconds) | 09:27 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.57.116> has joined #cip | 09:27 | |
| *** tmerciai <tmerciai!~tmerciai@188.217.57.116> has quit IRC (Ping timeout: 245 seconds) | 09:35 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.57.116> has joined #cip | 09:36 | |
| *** tmerciai1 <tmerciai1!~tmerciai@188.217.57.116> has quit IRC (Read error: Connection reset by peer) | 09:41 | |
| *** frieder <frieder!~frieder@88.130.219.74> has joined #cip | 09:43 | |
| *** 082AAAHVR <082AAAHVR!~tmerciai@188.217.57.116> has joined #cip | 09:46 | |
| *** 082AAAHVR <082AAAHVR!~tmerciai@188.217.57.116> has quit IRC (Remote host closed the connection) | 10:21 | |
| *** patersonc <patersonc!uid614485@id-614485.hampstead.irccloud.com> has quit IRC (Server closed connection) | 10:22 | |
| *** patersonc <patersonc!uid614485@id-614485.hampstead.irccloud.com> has joined #cip | 10:23 | |
| *** jki <jki!~jki@137.31.33.79> has joined #cip | 11:56 | |
| *** masami <masami!~masami@FL1-125-195-179-69.tky.mesh.ad.jp> has joined #cip | 11:57 | |
| jki | hi all | 11:59 |
|---|---|---|
| masami | hello | 12:00 |
| uli | hallo | 12:00 |
| jki | #startmeeting CIP IRC weekly meeting | 12:00 |
| collab-meetbot | Meeting started Thu Nov 12 12:00:54 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:01 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | - draft of improved patch review process [all maintainers] | 12:01 |
| iwamatsu | hello | 12:01 |
| jki | pavel: I think you wanted to start with that | 12:01 |
| jki | if he is already around.. | 12:02 |
| jki | otherwise postpone that to AOB | 12:02 |
| jki | nothing else recorded | 12:02 |
| jki | 5 | 12:02 |
| jki | 4 | 12:02 |
| jki | 3 | 12:02 |
| jki | 2 | 12:02 |
| jki | 1 | 12:02 |
| jki | #topic Kernel maintenance updates | 12:02 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:02 | |
| masami | This week reported 21 new CVEs and 50 updated CVEs. | 12:03 |
| uli | 4.4 request for reviews is out, 63 patches | 12:03 |
| iwamatsu | I reviewed 6.12.110 and 111. | 12:03 |
| uli | pave1 has so far reviewed ~50/90 of 4.19 | 12:03 |
| jki | anything to add? | 12:05 |
| pave1 | Sorry for being late :-). | 12:05 |
| pave1 | Yep, I was reviewing 4.19. | 12:05 |
| pave1 | At same point, we should clarify if / how stable kernel rules apply to -cip. | 12:05 |
| jki | we have something in the wiki, intentionally vague - IIRC according to your wishes | 12:06 |
| jki | but maybe keep that topic in mind for AOB | 12:07 |
| pave1 | Yep. | 12:08 |
| jki | anything else on maintenance? | 12:08 |
| jki | 5 | 12:08 |
| jki | 4 | 12:08 |
| jki | 3 | 12:08 |
| jki | 2 | 12:08 |
| jki | 1 | 12:08 |
| jki | #topic Kernel release status | 12:08 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:08 | |
| jki | so, 4.4 and 4.19 are still waiting for the second reviews, right? | 12:09 |
| uli | correct | 12:09 |
| jki | what can be done to accelerate that? | 12:09 |
| iwamatsu | am also reviewing those patches, but since there are so many, it is taking some time... | 12:10 |
| pave1 | That's the aob topic... should we be doing complex backports? | 12:11 |
| pave1 | Stable rules say: - It must be obviously correct and tested. | 12:11 |
| pave1 | and - It cannot be bigger than 100 lines, with context. | 12:11 |
| jki | is 4.19 late because of complex feature backports? | 12:11 |
| jki | would be surprising | 12:11 |
| jki | or are the bug fixes too complex? | 12:11 |
| pave1 | Not feature backports, but bug fixes are getting complex. | 12:12 |
| uli | we don't backport any features. but some fixes get more complex the older the kernel gets | 12:12 |
| jki | but that is nothing new: fix or document as "known bug", no? | 12:12 |
| jki | was there a discussion on that choice for the current queue already? | 12:12 |
| pave1 | Well, rules are more than that. It also says "obviously correct", which, frankly, some really are not. | 12:13 |
| pave1 | They also say "tested", but we are backporting even patches we are not testing, because it seems like lesser evil. | 12:13 |
| uli | the problem is that some of the tricky fixes have rather high CVSS scores. if not, i would drop them anyway. | 12:14 |
| pave1 | And it gives limit of 100 lines we are not enforcing. | 12:14 |
| jki | so, problem is now missing bandwidth to perform and validate security fix backports | 12:14 |
| pave1 | Yes. | 12:15 |
| jki | that would mean, we should ramp our our staffing for this purpose (as well) | 12:15 |
| uli | i guess so. i don't see an obvious easy solution. | 12:15 |
| jki | and look for some more kernel engineer(s) to support? | 12:15 |
| pave1 | Or rather, bandwidth to fix backports, some of which are likely security fixes, some of which are not. | 12:16 |
| jki | in any case, senior kernel engineer profile needed - or good LLMs... | 12:16 |
| jki | we still have codex tokens... | 12:17 |
| pave1 | There's tradeoff between "all fixes to mainline are backported to xx-cip" and "no regressions in xx-cip". | 12:17 |
| jki | yes, but that needs discussion | 12:17 |
| jki | not simply "rules" | 12:17 |
| iwamatsu | `kUsing multiple LLMs for analysis might be a good idea. | 12:17 |
| pave1 | And we don't yet see regressions in xx-cip, so maybe I worry too much and it would be enough to document that | 12:17 |
| pave1 | a) we don't test all fixes | 12:18 |
| pave1 | b) we do take non-obvious fixes | 12:18 |
| pave1 | c) we take fixes longer than 100 lines. | 12:18 |
| jki | "100 lines" is a pointless rule | 12:18 |
| pave1 | Well, it is there in stable-kernel-rules.rst :-). | 12:18 |
| pave1 | Plus you can hardly call 200 lines patch "obviously correct". | 12:19 |
| jki | sure, but that is not the point | 12:19 |
| jki | you can split, "just" takes more effort | 12:19 |
| jki | and if staffolding is needed for old kernels, that write it | 12:19 |
| jki | all doable, but that takes time and resources to do and validate | 12:20 |
| jki | but "simply" droping a CVE fix because of "too complex by rule" is not an option | 12:20 |
| jki | it needs to be discussed at least, reasoned and documented | 12:21 |
| pave1 | Well, due to way CVEs work for kernel, everything is "CVE fix" now. | 12:21 |
| jki | but not everyting is critical | 12:21 |
| pave1 | Yes. | 12:21 |
| jki | can we make this a bit more concrete? which backports are under discussion now? | 12:21 |
| pave1 | Concrete example is e37dae2a4576c5 | 12:23 |
| jki | 4.19-st tree? | 12:23 |
| uli | -rc | 12:23 |
| pave1 | Yes. | 12:23 |
| jki | already tried different LLMs as well? | 12:24 |
| uli | for review or backport? | 12:24 |
| pave1 | That's a locking fix, and it would be good to have. | 12:24 |
| jki | happy to ask claude or codex later on for an opinion | 12:24 |
| jki | I recently had very good results with Opus and Fable on Xenomai trees, so rather "special" and "complex" as well | 12:25 |
| pave1 | Well... it is probable LLM did quite a good job. | 12:25 |
| uli | the problem is not this specific patch, it's that we have to look at all of them, unless we simply say that LLM review is enough... | 12:26 |
| pave1 | ...but now we have patch touching locking in ax25 protocol, and patch looks plausible (as LLM patches do), but we certainly did not test it. | 12:26 |
| jki | yes, understood - engineering capacity again | 12:26 |
| pave1 | ...plus its over 100 lines at so. | 12:26 |
| pave1 | To reiterate, LLM is probably doing good job there. | 12:27 |
| jki | folks, then prioritize: complex, critical backport go to a backlog, get documented as unfixed for now, but we move forward with the rest | 12:27 |
| pave1 | If I had to cram that patch into 4.19 at all costs, I may have done the same job. | 12:27 |
| jki | and we process the complex queue later | 12:27 |
| jki | holding back releases because of some complex corners is also not good | 12:28 |
| uli | my preference would be to keep the complex unless there is a concrete reason not to | 12:29 |
| jki | should we introduce voting? :) | 12:29 |
| pave1 | I believe "put this into backlog" is not good option. | 12:29 |
| pave1 | Voting is not really solution here :-). | 12:30 |
| jki | then, what to do now, for the current queue and for the future? | 12:30 |
| pave1 | I guess we should introduce transparency: we are backporting complex patches we can not test. | 12:30 |
| uli | yes, i think that's better than holding potentially important fixes back | 12:31 |
| pave1 | We are trying to keep regressions to the minimum, but due to the need to backport some complex patches, we may have some. | 12:31 |
| pave1 | We are not following "obviously correct", "tested" and "less than 100 lines" rules any more. | 12:31 |
| jki | is upstream still doing that...? | 12:31 |
| pave1 | Lets say that upstream was always flexible with that :-). | 12:32 |
| jki | see | 12:32 |
| pave1 | [It was probably enforced for patches submitted by people, but not for patches backported by stable team]. | 12:32 |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.57.116> has joined #cip | 12:33 | |
| jki | ok, what's next then for the current queue? | 12:33 |
| uli | pave1: how long do you think you'll still need for 4.19? | 12:34 |
| pave1 | I believe the current queue should be just released. I went through most patches that looked relevant. | 12:34 |
| uli | ok | 12:35 |
| uli | what about 4.4? | 12:36 |
| iwamatsu | I think I’ll be able to finish reviewing everything by tomorrow as well. | 12:36 |
| uli | thanks, i'll wait until tomorrow then. | 12:36 |
| jki | good, that sounds like some plan - thanks all already! | 12:37 |
| pave1 | 4.4: Lets say we do the release at tuesday? | 12:37 |
| uli | ok for me | 12:37 |
| iwamatsu | ok for me too. | 12:38 |
| pave1 | 4.4, 4.19: If patch for minor resource leak requires llm work, I'd say don't dot it. | 12:38 |
| uli | that's already implemented for 4.4 | 12:38 |
| uli | that's why there are "only" 63 patches :) | 12:39 |
| pave1 | There's ton of those, there will be more and noone cares. | 12:39 |
| pave1 | Aha, ok. | 12:39 |
| pave1 | Another possible rules might be "if bug requires GFP_KERNEL allocation failing we don't care" because we are already OOM and system is already unusuable. | 12:39 |
| uli | are there a lot of those? | 12:40 |
| pave1 | And "error paths in probing don't really require fixes" ... because if your driver fails to probe, your hardware is unusable, anyway. | 12:40 |
| pave1 | ...and you have already caught that during development. | 12:41 |
| pave1 | I have seen at least one of those in 4.19-st review. | 12:41 |
| pave1 | I was saying to myself "hmm, probably does not break anything, but hmm, I would not backport this". | 12:42 |
| uli | ok, i'll add those and see how it goes | 12:42 |
| pave1 | Thanks! | 12:43 |
| uli | IGNORE now includes: - it fixes an issue caused by a GFP_KERNEL memory allocation failure | 12:44 |
| uli | - it fixes an issue in the error path during device probing | 12:44 |
| uli | actually, i'll have to add "exclusively" to that | 12:44 |
| jki | ok, are we done with release topics? | 12:45 |
| pave1 | Do we prevent LLM from working on stuff we don't enable in our configs? | 12:45 |
| uli | i have a script sorting those out before the llm sees it | 12:46 |
| pave1 | Ok, good. That is one more reason to prune our configs. | 12:46 |
| jki | of course, as well as to maintain them according to real demands | 12:47 |
| jki | so, move on? | 12:47 |
| pave1 | yes. | 12:47 |
| jki | 5 | 12:47 |
| jki | 4 | 12:47 |
| jki | 3 | 12:47 |
| jki | 2 | 12:47 |
| jki | 1 | 12:47 |
| jki | #topic Kernel testing | 12:47 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:47 | |
| jki | anyone with testing topics today? | 12:48 |
| pave1 | If someone could take a look at https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/17875327047 | 12:48 |
| iwamatsu | Several labs are down.cybertrust and siemens-prag. | 12:48 |
| pave1 | It is new kind of failure and does not go away with retry. | 12:48 |
| iwamatsu | we can not use all x86-siemens-mcom device now. I think that is the cause. | 12:50 |
| jki | the M-Com in Munich does not run kernel tests, only image tests | 12:51 |
| arisut | no update here, other than some people are starting to use kci-dev with the mcp | 12:51 |
| pave1 | Aha, so that's known. It says "There are currently 2 "x86-siemens-mcom" devices online.", which confused me. | 12:51 |
| arisut | https://kernelci.org/blog/2026/09/12/talk-to-kernelci-kci-dev-now-speaks-mcp/ | 12:51 |
| jki | the one in Prague should do the other way around, but... | 12:51 |
| jki | clarifying Prague lab state right now | 12:51 |
| jki | uh, we even have 3 mcoms in Prague now, just no online lab | 12:52 |
| jki | I suppose we had no chance (time) yet to play with kci-mcp in our context :( | 12:53 |
| jki | more on testing? | 12:55 |
| jki | 5 | 12:55 |
| jki | 4 | 12:55 |
| jki | 3 | 12:55 |
| jki | 2 | 12:55 |
| jki | 1 | 12:55 |
| jki | #topic AOB | 12:55 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:55 | |
| jki | SECURITY.md: can send a v3 with the minor adjustments unless there are more comments | 12:56 |
| pave1 | Looks good. | 12:56 |
| jki | further topics? | 12:56 |
| pave1 | I wanted to ask : if there's SPARC problem in 4.4, we don't care, right? | 12:56 |
| pave1 | Does CRA allow us to do that? | 12:57 |
| jki | right, per scope we define in "Security Context" | 12:57 |
| uli | sparc is out. | 12:57 |
| pave1 | Ok, being more explicit about that would not be bad. | 12:57 |
| jki | I haven't read anything different about the CRA | 12:57 |
| jki | pavel: we cannot write down the details of the configs in the SECURITY.md, they are not defined there | 12:58 |
| jki | that's why we pointed to that repo - please read again | 12:58 |
| pave1 | Something like "if the issue is in unsupported parts of 4.4 or 4.19 kernel, please send report to dev null, we don't care". | 13:00 |
| pave1 | Ok, maybe not that explicit. | 13:00 |
| jki | you really need to read the whole documents | 13:00 |
| pave1 | Ok. | 13:01 |
| jki | LLM normally does today ;) | 13:01 |
| jki | ok more topics for today? | 13:01 |
| jki | 5 | 13:02 |
| jki | 4 | 13:02 |
| jki | 3 | 13:02 |
| jki | 2 | 13:02 |
| jki | 1 | 13:02 |
| jki | #endmeeting | 13:02 |
| collab-meetbot | Meeting ended Thu Nov 12 13:02:23 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:02 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/11/cip.2026-11-12-12.00.html | 13:02 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/11/cip.2026-11-12-12.00.txt | 13:02 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/11/cip.2026-11-12-12.00.log.html | 13:02 |
| *** 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/" | 13:02 | |
| jki | thanks all! | 13:02 |
| uli | thanks | 13:02 |
| pave1 | Thank you! | 13:02 |
| masami | thank you | 13:02 |
| iwamatsu | thank you | 13:02 |
| *** masami <masami!~masami@FL1-125-195-179-69.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:02 | |
| arisut | thx | 13:03 |
| jki | PS: prag-lab is online again | 13:05 |
| pave1 | Thank you! I'll retry the job. | 13:06 |
| jki | targets are already busy again :D | 13:07 |
| jki | ...but only with healthjobs, so go ahead | 13:07 |
| *** noctux <noctux!~noctux@user/noctux> has quit IRC (Read error: Connection reset by peer) | 13:23 | |
| *** noctux <noctux!~noctux@user/noctux> has joined #cip | 13:25 | |
| *** jki <jki!~jki@137.31.33.79> has quit IRC (Quit: Leaving) | 13:41 | |
| *** tmerciai2 <tmerciai2!~tmerciai@188.217.57.116> has quit IRC (Ping timeout: 242 seconds) | 14:11 | |
| *** frieder <frieder!~frieder@88.130.219.74> has quit IRC (Remote host closed the connection) | 16:20 | |
| *** arnd <arnd!sid21101@id-21101.hampstead.irccloud.com> has quit IRC (Server closed connection) | 23:31 | |
| *** arnd <arnd!sid21101@id-21101.hampstead.irccloud.com> has joined #cip | 23:31 | |
| *** sashal <sashal!sid491190@id-491190.hampstead.irccloud.com> has quit IRC (Server closed connection) | 23:42 | |
| *** sashal <sashal!sid491190@id-491190.hampstead.irccloud.com> has joined #cip | 23:42 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!