Thursday, 2025-08-21

*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has quit IRC (Ping timeout: 256 seconds)01:26
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has joined #cip01:27
*** tmerciai <tmerciai!~tmerciai3@net-188-217-58-238.cust.vodafonedsl.it> has joined #cip06:30
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has quit IRC (Ping timeout: 255 seconds)09:39
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has joined #cip09:40
*** vigneshr <vigneshr!uid375618@user/vigneshr> has joined #cip11:05
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip11:34
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.57> has joined #cip12:44
*** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has joined #cip12:57
*** jki <jki!~jki@195.145.170.160> has joined #cip13:00
jkihi all13:00
pave1Hi!13:00
iwamatsu_hello13:01
masamihello13:01
ulihello13:01
jkithen let's go13:01
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbotMeeting started Thu Aug 21 13:02:03 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:02
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:02
jki#topic AI review13:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jki- draft CVE handling process for CIP kernel [Jan]13:02
jkijust shared a draft with the core group13:02
jkithanks for first feedback already, still need to read :)13:02
pave1Yep, you have some replies :-).13:02
pave1Not sure why we are talking about CVEs in the first place.13:03
jkiplan would be to put something on the wall during out Summit next week, then discuss13:03
pave1For kernel, CVEs are just another identifier for stable kernel patches.13:03
jkiright13:03
jkiwill also try to make that clear13:04
pave1So you'll get stuff like "CVE-1"  for kernel, and then have "CVE-2" that reverts "CVE-1". Fun :-).13:04
jkistill, we have our tracker list, and we already heard more than once that it is considered very valuable13:04
jkieverything an happen, but I would not expect that to happen with every second CVE ;)13:05
pave1This will be with about 1% of them.13:05
jkiexamples always welcome13:05
*** iwamatsu_7 <iwamatsu_7!~iwamatsu_@155.190.52.57> has joined #cip13:06
jkialso to document where information is lost - and think about how annotation needs to be to reduce that risk13:06
*** iwamatsu_7 is now known as iwamatsu__13:06
jkibtw, no one expects upstream or the CIP kernel to be perfect in this, we should "just" apply best practices13:07
jkiok - please provide further feedback that should go into the discussion on Thursday upfront13:08
jkior speak up then ;)13:08
jkino other AIs on my list13:08
pave1I'm not sure what the goal here is.13:08
pave1We don't _want_ to have 0 CVEs for cip-4.4 kernel...13:08
jkidocument out process for paper work, would be one thing13:08
jkiwe will never have 0 CVEs in anything13:09
pave1...because that would mean buggy kernel.13:09
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.57> has quit IRC (Ping timeout: 250 seconds)13:09
jkiplease do not expect additional pressure on maintainers from writing down how things work13:09
patersoncIt's not only about the "CVE". It's about making sure that we are fixing known bugs in our kernels right?13:10
jkipatersonc: you first of all asked about CVEs ;)13:10
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.57> has joined #cip13:10
pave1I guess we should talk in person.13:11
jkibut, yes, bug handling in general is important too13:11
patersoncI did - but it's just because we have tooling tracking the CVEs, we don't have tooling tracking every upstream fix13:11
patersoncAlthough every upstream fix is a CVE now..13:11
pave1patersonc: I believe priority is a) not add new bugs, and b) given a), fix some bugs.13:11
jkiin theory, surely not in practice13:11
jkiand some bug fixes really don't deserve CVEs, but they should still be in stable13:12
pave1patersonc: Fortunately not every upstream fix. When things are applied to _stable_, they will get CVE identifier.13:12
pave1patersonc: If it does not apply to stable (patch failed), I'd expect it is just dropped.13:13
jkipaveL: functional fixes that do not address security aspects will not get CVEs (or will get them revoked)13:13
pave1jki: I believe the policy is "if it is a bug fix it gets an CVE" and then "if someone tries to revoke the CVE we may do that".13:14
*** iwamatsu__ <iwamatsu__!~iwamatsu_@155.190.52.57> has quit IRC (Ping timeout: 250 seconds)13:14
pave1jki: stable team is pretty clear about not deciding about security when assigning CVEs.13:14
jkipavel: already due to the fact that some fixing commit may pull preperatory commits you do not have a 1:1 between stable commit and CVE13:16
pave1jki: I'm not claiming 1:1 between stable commits and CVEs.13:17
jkibut I think we should really continue this on Thursday :)13:17
pave1jki: I'm saying that "admin can crash his own machine" will get an CVE.13:17
pave1jki: yes.13:17
jki513:18
jki413:18
jki313:18
jki213:18
jki113:18
jki#topic Kernel maintenance updates13:18
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:18
ulii'm working on 4.413:18
pave1I'm reviewing 6.12.42 and .43.13:19
masami This week reported 118 new CVEs and 6 updated CVEs.13:19
iwamatsu_I am reviewing 6.12.42. and I released 510.y-cip and 6.1.y-cip.13:19
pave1...and renesas patches. SPI and camera, camera is 55 patches.13:19
jkianything to add?13:21
jki513:21
jki413:21
jki313:21
jki213:21
jki113:21
jki#topic Kernel release status13:21
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:21
jkieverything green13:21
jkiany issues ahead?13:22
jki513:22
jki413:22
jki313:22
jki213:22
jki113:22
*** iwamatsu_68 <iwamatsu_68!~iwamatsu_@155.190.52.57> has joined #cip13:22
jki#topic Kernel testing13:22
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:22
patersoncArisu's KernelCI PR has now been merged, adding initial test support for CIP kernels13:23
patersoncHopefully it will push out to production soon13:23
patersoncThere are some known issues with booting the arm32 devices, but this seems to be a kernel config issu13:23
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.57> has quit IRC (Ping timeout: 250 seconds)13:23
patersoncI'll update more on the specifics next week13:24
jkimore test topics?13:26
patersoncNot from me13:26
jki513:27
jki413:27
jki313:27
jki213:27
jki113:27
jki#topic AOB13:27
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:27
jkifirst of all: we have the mini summit next week, this time, thus no irc meeting13:28
jkiskip, or should we shift?13:28
uliskip it, imo13:29
patersonc+113:29
pave1I believe skip. We'l have enough meetings next week :-)13:29
iwamatsu_68+113:29
jkiexactly :)13:29
jkibut... should he have a lunch meetup as kernel WG again?13:30
jkiwho will be there at all?13:30
ulio/13:30
patersonco/13:30
pave1o/13:30
iwamatsu_68I am not there...13:31
jkiif you like to meet, I would suggest the Wednesday lunch slot13:31
jkimeet at CIP booth13:31
jki?13:33
patersoncSounds tasty13:33
jkiok, be there if you like and can13:34
jkiany other topics for today?13:34
jki513:35
jki413:35
jki313:35
jki213:35
jki113:35
jki#endmeeting13:35
collab-meetbotMeeting ended Thu Aug 21 13:35:57 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:35
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/08/cip.2025-08-21-13.02.html13:35
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/08/cip.2025-08-21-13.02.txt13:35
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/08/cip.2025-08-21-13.02.log.html13: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
ulithanks13:36
pave1Thank you, and have a good trip!13:36
masamithank you13:36
iwamatsu_68Thank you13:36
jkithanks!13:36
jkisafe trips!13:36
patersonccheers13:36
*** iwamatsu_68 <iwamatsu_68!~iwamatsu_@155.190.52.57> has quit IRC (Quit: Client closed)13:37
*** jki <jki!~jki@195.145.170.160> has quit IRC (Ping timeout: 248 seconds)13:50
*** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)14:01
*** jki <jki!~jki@195.145.170.168> has joined #cip14:04
*** jki <jki!~jki@195.145.170.168> has quit IRC (Quit: Leaving)14:57
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Remote host closed the connection)16:57
*** tmerciai <tmerciai!~tmerciai3@net-188-217-58-238.cust.vodafonedsl.it> has quit IRC (Ping timeout: 256 seconds)18:09

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