Thursday, 2024-07-04

« Wednesday, 2024-07-03 Index Friday, 2024-07-05 »
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip04:47
*** frieder <frieder!~frieder@89.244.121.50> has joined #cip05:58
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.104> has quit IRC (Quit: Konversation terminated!)07:23
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.104> has joined #cip07:23
*** iwamatsu__ <iwamatsu__!~iwamatsu_@155.190.52.19> has joined #cip12:35
*** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has joined #cip12:54
*** Dinesh <Dinesh!~Dinesh@2405:201:d007:f8c2:b409:b077:e84f:3367> has joined #cip12:58
*** jki <jki!~jki@62.156.206.45> has joined #cip12:59
jkihi everyone13:00
ulihello13:00
masamihi13:00
DineshHello All13:00
arisuthi13:00
pave1hi13:00
patersoncHello13:00
iwamatsu__hello13:01
jkigood, let's start13:01
jki#startmeeting CIP IRC weekly meeting13:01
collab-meetbot`Meeting started Thu Jul  4 13:01:46 2024 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 review13:01
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:01
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:01
jkino news13:02
jkiand nothing else from last time13:02
jkiso...13:02
jki513:02
jki413:02
jki313:02
jki213:02
jki113:02
jki#topic Kernel maintenance updates13:02
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:02
ulii've been preparing the next 4.4 release13:02
masamiThis week reported 1 new CVEs and 0 updated CVEs. It was quiet week.13:03
iwamatsu__I am reviewing 6.1.96.13:03
jkianything else?13:04
pave1I'm reviewing .1..13:04
pave16.1.96.13:04
pave1There's recent -rt release, so I'll likely do matching 6.1-cip and then -cip-rt.13:06
jkiboth are due these days anyway13:06
*** Dinesh <Dinesh!~Dinesh@2405:201:d007:f8c2:b409:b077:e84f:3367> has quit IRC (Remote host closed the connection)13:08
jkiok, them moving on13:08
jki513:08
jki413:08
iwamatsu__I will release  linux-6.1.y-cip with 6.1.96. :-)13:08
*** Dinesh <Dinesh!~Dinesh@2405:201:d007:f8c2:b409:b077:e84f:3367> has joined #cip13:08
jkiperfect13:08
jki313:08
jki213:08
jki113:08
jki#topic Kernel release status13:08
pave1iwamatsu> ok, thanks, that will help me.13:08
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:08
jkiall green, next to come we already discussed :)13:09
jkialmost: 5.10 and 4.19 are also due soon13:09
jkianyway - any blockers in sight?13:09
pave1I don't see any.13:10
jki513:10
jki413:10
jki313:10
jki213:10
jki113:10
jki#topic Kernel testing13:10
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:10
arisutsent issue #2594 for creating a development tool on KernelCI that can send locally changes to tests https://github.com/kernelci/kernelci-core/issues/259413:10
jkiSiemens lab is up again13:11
arisutcurrently is under discussion13:11
arisutjki: nice13:11
patersoncjki: Ah right, I didn't notice :D13:12
patersoncThanks13:12
jkicorrection - except for the de0-nano-soc13:12
jkiwe need to check that again13:12
patersoncjki: Shall I delete the lab-cip-siemens-prague worker?13:13
arisutthe KernelCI client could be used for testing local CIP kernel sources directly on KernelCI, with extended flexibility (like decide if publish results or which laboratory to use)13:14
jkipatersonc: we are still hoping to eventually get it online13:14
jkijust the "when" is unclear13:14
patersoncarisut: That sounds useful13:14
arisutalso CIP patches could be tested13:15
patersoncjki: Okay, I'll leave it then - thanks13:15
arisutit should improve kernel development13:16
pave1Yes, ability to test local tree without git commit would be nice.13:16
arisutyes buildbot try already allow such feature13:16
arisutis few years that I'm talking about having something similar to what buildbot does13:17
jkicool!13:18
arisutafter many discussion I decided to just open a issue somewhere about such features13:18
*** frieder <frieder!~frieder@89.244.121.50> has quit IRC (Remote host closed the connection)13:20
arisutprobably will be created as an extension of kci tool13:20
jkianything else on testing?13:22
patersoncNot from me13:22
jki513:23
jki413:23
jki313:23
jki213:23
jki113:23
jki#topic AOB13:23
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:23
jkiDinesh: you wanted to discuss about BV feedback13:24
DineshYes13:24
DineshShall I briefly explain?13:24
jkijup13:24
DineshFor meeting DM-3 requirement of IEC-62443-4-1 (Asessing security related issues) It expects documented process to assess security issues13:24
DineshSWG documented based on upstream https://gitlab.com/cip-project/cip-documents/-/blob/master/process/Security_issues_handling.md?ref_type=heads#dm-3-assessing-security-related-issues-13:25
DineshWhen we had discussion with BV, they mentioned kernel WG will be doing some assessment to select fewer security issues for CIP out of large number of issues13:25
DineshSo the main point we have to discuss the criteria used to select fewer issues by kernel WG13:26
pave1Ummm. Not kernel wg.13:26
jkione element we are starting to look into: CVE filtering based on kernel config13:27
Dineshok13:27
DineshJan you mentioned for filtering automation in TSC13:27
jkiI mentioned that a few weeks ago, it's scheduled on our side to look into options and caveats13:27
jkinot yet there, though :)13:28
Dineshok understood13:28
pave1Or better yet. It depends on 'select from where'13:28
pave1CVEs for kernel contain too much noise to be useful.13:28
jkiyeah, this is not going to be noise cancelation13:29
Dinesh:)13:29
pave1We can filter based on config, and it may eliminate 50% issues,13:29
jkibut, conceptually, it could also just be applied on any interesting commit in newer kernels13:29
pave1but that's still way too much noise.13:30
DineshAt least based on kernel config seems quite relevant13:30
pave1So.. someone needs to come with less noisy security issues source.13:30
jkithat's why I said in the TSC that coupling our backport procedures with what is today called "CVE" may not be helpful13:32
jkistill, the general task remains: indentify /relevant/ fixes from upstream for our kernels13:32
jkiDinesh: anything else you'd like to discuss?13:34
DineshYeah so as of now SWG will mark it as in-progress13:34
DineshNo that's all I had for discussion13:34
pave1(Or with additional manpower. Filtering CVEs might be half-time to full-time job).13:34
jkiright, that is the risk13:35
jkiand if that should become a hard requirement for us, we need to make this transparent as early as possible13:36
pave1+113:37
jkiDinesh: are there any indications in that direction?13:37
DineshNo hard requirement13:37
jkigood :)13:37
jkiany other business for today?13:38
jki513:38
jki413:39
jki313:39
jki213:39
jki113:39
jki#endmeeting13:39
collab-meetbot`Meeting ended Thu Jul  4 13:39:06 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:39
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/07/cip.2024-07-04-13.01.html13:39
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/07/cip.2024-07-04-13.01.txt13:39
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/07/cip.2024-07-04-13.01.log.html13:39
*** 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:39
arisutthanks you13:39
jkithanks all!13:39
iwamatsu__Thank you13:39
pave1thank you!13:39
ulithanks13:39
masamithank you13:39
DineshThanks All13:39
*** Dinesh <Dinesh!~Dinesh@2405:201:d007:f8c2:b409:b077:e84f:3367> has left #cip13:39
*** jki <jki!~jki@62.156.206.45> has quit IRC (Quit: Leaving)13:41
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip13:42
*** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)14:02
*** iwamatsu__ <iwamatsu__!~iwamatsu_@155.190.52.19> has quit IRC (Ping timeout: 250 seconds)14:26
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)17:57
« Wednesday, 2024-07-03 Index Friday, 2024-07-05 »

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