Thursday, 2026-11-12

*** dl9pf <dl9pf!sid395223@user/dl9pf> has quit IRC (Server closed connection)01:28
*** dl9pf <dl9pf!sid395223@user/dl9pf> has joined #cip01:28
*** zar <zar!~quassel@mail.nazaryev.ru> has quit IRC (Server closed connection)02:23
*** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip02: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 #cip05:46
*** tmerciai1 <tmerciai1!~tmerciai@188.217.57.116> has joined #cip08: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 #cip08:12
*** frieder <frieder!~frieder@88.130.219.74> has joined #cip08: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 #cip08: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 #cip08: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 #cip09: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 #cip09: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 #cip09:43
*** 082AAAHVR <082AAAHVR!~tmerciai@188.217.57.116> has joined #cip09: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 #cip10:23
*** jki <jki!~jki@137.31.33.79> has joined #cip11:56
*** masami <masami!~masami@FL1-125-195-179-69.tky.mesh.ad.jp> has joined #cip11:57
jkihi all11:59
masamihello12:00
ulihallo12:00
jki#startmeeting CIP IRC weekly meeting12:00
collab-meetbotMeeting 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-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
collab-meetbotThe 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 review12: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
iwamatsuhello12:01
jkipavel: I think you wanted to start with that12:01
jkiif he is already around..12:02
jkiotherwise postpone that to AOB12:02
jkinothing else recorded12:02
jki512:02
jki412:02
jki312:02
jki212:02
jki112:02
jki#topic Kernel maintenance updates12:02
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:02
masamiThis week reported 21 new CVEs and 50 updated CVEs.12:03
uli4.4 request for reviews is out, 63 patches12:03
iwamatsuI reviewed 6.12.110 and 111.12:03
ulipave1 has so far reviewed ~50/90 of 4.1912:03
jkianything to add?12:05
pave1Sorry for being late :-).12:05
pave1Yep, I was reviewing 4.19.12:05
pave1At same point, we should clarify if / how stable kernel rules apply to -cip.12:05
jkiwe have something in the wiki, intentionally vague - IIRC according to your wishes12:06
jkibut maybe keep that topic in mind for AOB12:07
pave1Yep.12:08
jkianything else on maintenance?12:08
jki512:08
jki412:08
jki312:08
jki212:08
jki112:08
jki#topic Kernel release status12:08
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:08
jkiso, 4.4 and 4.19 are still waiting for the second reviews, right?12:09
ulicorrect12:09
jkiwhat can be done to accelerate that?12:09
iwamatsuam also reviewing those patches, but since there are so many, it is taking some time...12:10
pave1That's the aob topic... should we be doing complex backports?12:11
pave1Stable rules say: - It must be obviously correct and tested.12:11
pave1and -  It cannot be bigger than 100 lines, with context.12:11
jkiis 4.19 late because of complex feature backports?12:11
jkiwould be surprising12:11
jkior are the bug fixes too complex?12:11
pave1Not feature backports, but bug fixes are getting complex.12:12
uliwe don't backport any features. but some fixes get more complex the older the kernel gets12:12
jkibut that is nothing new: fix or document as "known bug", no?12:12
jkiwas there a discussion on that choice for the current queue already?12:12
pave1Well, rules are more than that. It also says "obviously correct", which, frankly, some really are not.12:13
pave1They also say "tested", but we are backporting even patches we are not testing, because it seems like lesser evil.12:13
ulithe problem is that some of the tricky fixes have rather high CVSS scores. if not, i would drop them anyway.12:14
pave1And it gives limit of 100 lines we are not enforcing.12:14
jkiso, problem is now missing bandwidth to perform and validate security fix backports12:14
pave1Yes.12:15
jkithat would mean, we should ramp our our staffing for this purpose (as well)12:15
ulii guess so. i don't see an obvious easy solution.12:15
jkiand look for some more kernel engineer(s) to support?12:15
pave1Or rather, bandwidth to fix backports, some of which are likely security fixes, some of which are not.12:16
jkiin any case, senior kernel engineer profile needed - or good LLMs...12:16
jkiwe still have codex tokens...12:17
pave1There's tradeoff between "all fixes to mainline are backported to xx-cip" and "no regressions in xx-cip".12:17
jkiyes, but that needs discussion12:17
jkinot simply "rules"12:17
iwamatsu`kUsing multiple LLMs for analysis might be a good idea.12:17
pave1And we don't yet see regressions in xx-cip, so maybe I worry too much and it would be enough to document that12:17
pave1a) we don't test all fixes12:18
pave1b) we do take non-obvious fixes12:18
pave1c) we take fixes longer than 100 lines.12:18
jki"100 lines" is a pointless rule12:18
pave1Well, it is there in stable-kernel-rules.rst :-).12:18
pave1Plus you can hardly call 200 lines patch "obviously correct".12:19
jkisure, but that is not the point12:19
jkiyou can split, "just" takes more effort12:19
jkiand if staffolding is needed for old kernels, that write it12:19
jkiall doable, but that takes time and resources to do and validate12:20
jkibut "simply" droping a CVE fix because of "too complex by rule" is not an option12:20
jkiit needs to be discussed at least, reasoned and documented12:21
pave1Well, due to way CVEs work for kernel, everything is "CVE fix" now.12:21
jkibut not everyting is critical12:21
pave1Yes.12:21
jkican we make this a bit more concrete? which backports are under discussion now?12:21
pave1Concrete example is e37dae2a4576c512:23
jki4.19-st tree?12:23
uli-rc12:23
pave1Yes.12:23
jkialready tried different LLMs as well?12:24
ulifor review or backport?12:24
pave1That's a locking fix, and it would be good to have.12:24
jkihappy to ask claude or codex later on for an opinion12:24
jkiI recently had very good results with Opus and Fable on Xenomai trees, so rather "special" and "complex" as well12:25
pave1Well... it is probable LLM did quite a good job.12:25
ulithe 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
jkiyes, understood - engineering capacity again12:26
pave1...plus its over 100 lines at so.12:26
pave1To reiterate, LLM is probably doing good job there.12:27
jkifolks, then prioritize: complex, critical backport go to a backlog, get documented as unfixed for now, but we move forward with the rest12:27
pave1If I had to cram that patch into 4.19 at all costs, I may have done the same job.12:27
jkiand we process the complex queue later12:27
jkiholding back releases because of some complex corners is also not good12:28
ulimy preference would be to keep the complex unless there is a concrete reason not to12:29
jkishould we introduce voting? :)12:29
pave1I believe "put this into backlog" is not good option.12:29
pave1Voting is not really solution here :-).12:30
jkithen, what to do now, for the current queue and for the future?12:30
pave1I guess we should introduce transparency: we are backporting complex patches we can not test.12:30
uliyes, i think that's better than holding potentially important fixes back12:31
pave1We are trying to keep regressions to the minimum, but due to the need to backport some complex patches, we may have some.12:31
pave1We are not following "obviously correct", "tested" and "less than 100 lines" rules any more.12:31
jkiis upstream still doing that...?12:31
pave1Lets say that upstream was always flexible with that :-).12:32
jkisee12: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 #cip12:33
jkiok, what's next then for the current queue?12:33
ulipave1: how long do you think you'll still need for 4.19?12:34
pave1I believe the current queue should be just released. I went through most patches that looked relevant.12:34
uliok12:35
uliwhat about 4.4?12:36
iwamatsuI think I’ll be able to finish reviewing everything by tomorrow as well.12:36
ulithanks, i'll wait until tomorrow then.12:36
jkigood, that sounds like some plan - thanks all already!12:37
pave14.4: Lets say we do the release at tuesday?12:37
uliok for me12:37
iwamatsuok for me too.12:38
pave14.4, 4.19: If patch for minor resource leak requires llm work, I'd say don't dot it.12:38
ulithat's already implemented for 4.412:38
ulithat's why there are "only" 63 patches :)12:39
pave1There's ton of those, there will be more and noone cares.12:39
pave1Aha, ok.12:39
pave1Another 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
uliare there a lot of those?12:40
pave1And "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
pave1I have seen at least one of those in 4.19-st review.12:41
pave1I was saying to myself "hmm, probably does not break anything, but hmm, I would not backport this".12:42
uliok, i'll add those and see how it goes12:42
pave1Thanks!12:43
uliIGNORE now includes: - it fixes an issue caused by a GFP_KERNEL memory allocation failure12:44
uli- it fixes an issue in the error path during device probing12:44
uliactually, i'll have to add "exclusively" to that12:44
jkiok, are we done with release topics?12:45
pave1Do we prevent LLM from working on stuff we don't enable in our configs?12:45
ulii have a script sorting those out before the llm sees it12:46
pave1Ok, good. That is one more reason to prune our configs.12:46
jkiof course, as well as to maintain them according to real demands12:47
jkiso, move on?12:47
pave1yes.12:47
jki512:47
jki412:47
jki312:47
jki212:47
jki112:47
jki#topic Kernel testing12:47
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:47
jkianyone with testing topics today?12:48
pave1If someone could take a look at https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/1787532704712:48
iwamatsuSeveral labs are down.cybertrust and siemens-prag.12:48
pave1It is new kind of failure and does not go away with retry.12:48
iwamatsuwe can not use all x86-siemens-mcom device now. I think that is the cause.12:50
jkithe M-Com in Munich does not run kernel tests, only image tests12:51
arisutno update here, other than some people are starting to use kci-dev with the mcp12:51
pave1Aha, so that's known. It says "There are currently 2 "x86-siemens-mcom" devices online.", which confused me.12:51
arisuthttps://kernelci.org/blog/2026/09/12/talk-to-kernelci-kci-dev-now-speaks-mcp/12:51
jkithe one in Prague should do the other way around, but...12:51
jkiclarifying Prague lab state right now12:51
jkiuh, we even have 3 mcoms in Prague now, just no online lab12:52
jkiI suppose we had no chance (time) yet to play with kci-mcp in our context :(12:53
jkimore on testing?12:55
jki512:55
jki412:55
jki312:55
jki212:55
jki112:55
jki#topic AOB12:55
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:55
jkiSECURITY.md: can send a v3 with the minor adjustments unless there are more comments12:56
pave1Looks good.12:56
jkifurther topics?12:56
pave1I wanted to ask : if there's SPARC problem in 4.4, we don't care, right?12:56
pave1Does CRA allow us to do that?12:57
jkiright, per scope we define in "Security Context"12:57
ulisparc is out.12:57
pave1Ok, being more explicit about that would not be bad.12:57
jkiI haven't read anything different about the CRA12:57
jkipavel: we cannot write down the details of the configs in the SECURITY.md, they are not defined there12:58
jkithat's why we pointed to that repo - please read again12:58
pave1Something 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
pave1Ok, maybe not that explicit.13:00
jkiyou really need to read the whole documents13:00
pave1Ok.13:01
jkiLLM normally does today ;)13:01
jkiok more topics for today?13:01
jki513:02
jki413:02
jki313:02
jki213:02
jki113:02
jki#endmeeting13:02
collab-meetbotMeeting 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-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/11/cip.2026-11-12-12.00.html13:02
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/11/cip.2026-11-12-12.00.txt13:02
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/11/cip.2026-11-12-12.00.log.html13: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
jkithanks all!13:02
ulithanks13:02
pave1Thank you!13:02
masamithank you13:02
iwamatsuthank you13:02
*** masami <masami!~masami@FL1-125-195-179-69.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:02
arisutthx13:03
jkiPS: prag-lab is online again13:05
pave1Thank you! I'll retry the job.13:06
jkitargets are already busy again :D13:07
jki...but only with healthjobs, so go ahead13:07
*** noctux <noctux!~noctux@user/noctux> has quit IRC (Read error: Connection reset by peer)13:23
*** noctux <noctux!~noctux@user/noctux> has joined #cip13: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 #cip23: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 #cip23:42

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