| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 05:49 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 05:51 | |
| *** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has joined #cip | 06:11 | |
| *** ironfoot_ is now known as ironfoot | 10:43 | |
| *** patersonc_ is now known as patersonc | 11:45 | |
| *** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has joined #cip | 12:45 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:d591:a45e:1147:25d6> has joined #cip | 12:59 | |
| arisut | hello | 12:59 |
|---|---|---|
| uli_ | hello | 12:59 |
| iwamatsu__ | hello | 13:00 |
| masami | hi | 13:00 |
| *** jki <jki!~jki@62.156.206.57> has joined #cip | 13:00 | |
| jki | hi all | 13:00 |
| iwamatsu__ | hi | 13:00 |
| masami | hello | 13:00 |
| arisut | hi | 13:01 |
| pave1 | hi | 13:02 |
| jki | let's get started | 13:02 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot` | Meeting started Thu May 23 13:02:48 2024 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-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:02 |
| collab-meetbot` | The 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 review | 13:02 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | - prepare blog entry on SLTS kernel state and challenges [Jan] | 13:03 |
| jki | down in the prio list again, was struggling (and still are) with cip-core | 13:03 |
| jki | no other AIs recorded | 13:03 |
| jki | 5 | 13:03 |
| jki | 4 | 13:03 |
| jki | 3 | 13:04 |
| jki | 2 | 13:04 |
| jki | 1 | 13:04 |
| jki | #topic Kernel maintenance updates | 13:04 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:04 | |
| pave1 | I was reviewing 6.1.91. | 13:04 |
| uli_ | i'm back from vacation, nothing substantial to report yet | 13:04 |
| masami | This week reported 685 new CVEs and 8 updated CVEs. | 13:04 |
| iwamatsu__ | I am reviewing 6.1.91 | 13:04 |
| jki | 685 is a new record - any particular reason for that peak visible? | 13:05 |
| masami | not sure.. | 13:06 |
| jki | just curious, not that it would change the overall situation | 13:07 |
| pave1 | Shal we do anything with the CVEs? | 13:07 |
| pave1 | I went through some, and signal-to-noise is not quite usefu | 13:08 |
| pave1 | useful. | 13:08 |
| jki | well, we can only do automated stuff with them, given the amount | 13:08 |
| pave1 | We are automatically putting them into database noone reads | 13:08 |
| jki | can we filter out anything that we already got or that is not affecting older kernels? | 13:09 |
| jki | to have stats of potentially open issues, at least on the CVE paper? | 13:09 |
| pave1 | I believe we have similar information in better form already | 13:10 |
| pave1 | cves are just git dumps. Not sure what kind of paper would be useful to generate from that. | 13:11 |
| arisut | pave1: what are you referring to? | 13:11 |
| pave1 | arisut -- greg is copy-pasting git logs into cves. | 13:12 |
| masami | Investigating issues where the commit introducing the bug is not documented. Perhaps we should focus on such bugs? | 13:13 |
| pave1 | Masami -- commit introducing not known will be common. | 13:14 |
| jki | well, anything that is fix in X, affecting Y and possibly not even affecting CIP is not interesting, sure | 13:14 |
| jki | digging into details is likely not helpful beyond examples | 13:15 |
| pave1 | but maybe we could filter by commit fixing not listed, because those are not spam? | 13:15 |
| jki | having stats could be | 13:15 |
| pave1 | jki -- i have some stats. | 13:15 |
| pave1 | on very small sample 50% is simply not security related. | 13:16 |
| pave1 | 40% may be relevant in some crazy config. | 13:16 |
| jki | well, config correlation is another area of interest, if automatable | 13:17 |
| pave1 | 10% could be a real issue. | 13:17 |
| jki | you may have seen https://ciq.com/blog/why-a-frozen-linux-kernel-isnt-the-safest-choice-for-security/ | 13:17 |
| jki | and the fact that they didn't look at the configs | 13:17 |
| pave1 | I can take a look. I believe that's more broken than that. | 13:18 |
| patersonc | jki: I guess we don't know _every_ config a SLTS user will be using though? Unless there are some options that can _never_ be used? | 13:18 |
| jki | we have defined supported configs | 13:18 |
| jki | we are not supporting random ones | 13:18 |
| jki | those can be debated in details, but if we exclude drivers or complete subsystems, that are easy takes (or non-takes) | 13:19 |
| patersonc | What happens if a new member joins and adds more configs? We would have to go back and work out which CVEs are now relevant, which we couldn't do if they weren't in our database to start with? | 13:19 |
| patersonc | Anyway, this topic is probably worth a proper call/F2F about at some point? | 13:20 |
| jki | that is a valid point, and it would at least take some impact analysis, automated | 13:20 |
| jki | if we exclude CVE-0815 today, will adding CONFIG_Y bring it plus hundreds more in? | 13:21 |
| jki | so far, we cannot tell that | 13:21 |
| jki | and no one is able to do manual analysis | 13:21 |
| pave1 | Well, we pretend we support any config on supported architectures. | 13:21 |
| jki | nope, we surely don't | 13:22 |
| jki | we never | 13:22 |
| jki | CIP is not a distro kernel, and even distros have certain exclusion areas, starting with CONFIG_STAGING | 13:22 |
| pave1 | ok, sure, staging is out. | 13:23 |
| jki | and more, just look at an long-living enterprise kernel | 13:25 |
| jki | do not state that CIP is generic, please, that is neither true nor what we communicated all the time | 13:25 |
| jki | we may patch left and right, but only on best effort basis, if at all | 13:26 |
| pave1 | I guess we should create a list of 'definitely out' options at some point. | 13:26 |
| jki | how to maintain that? | 13:27 |
| jki | it would not be a technically executable something | 13:27 |
| jki | we have a whitelist, and members can expand it | 13:27 |
| jki | we need to take measure to assess expansion requests better | 13:28 |
| jki | likely a topic for next TSC as well... | 13:30 |
| jki | anything else about this or beyond on maintenance? | 13:30 |
| jki | 5 | 13:31 |
| jki | 4 | 13:31 |
| jki | 3 | 13:31 |
| jki | 2 | 13:31 |
| jki | 1 | 13:31 |
| jki | #topic Kernel release status | 13:31 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:31 | |
| jki | I saw 4.19-rt is out | 13:31 |
| jki | 6.1 is scheduled? | 13:31 |
| iwamatsu__ | I am working for 6.1.y-cip | 13:31 |
| jki | perfect | 13:32 |
| jki | anything else? | 13:32 |
| jki | 5 | 13:32 |
| jki | 4 | 13:32 |
| jki | 3 | 13:32 |
| jki | 2 | 13:32 |
| jki | 1 | 13:32 |
| jki | #topic Kernel testing | 13:32 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:32 | |
| patersonc | We had some gitlab runner token issues, resolved now. Sorry for the interruption Pavel | 13:33 |
| arisut | no news from me | 13:33 |
| patersonc | I've been looking into some cip core testing bits & bobs. | 13:33 |
| patersonc | That's about it | 13:33 |
| pave1 | no problem, it works now | 13:33 |
| jki | Siemens lab bring-back is delayed due to connectivity issues | 13:34 |
| patersonc | I've been trying to push internally for more time/resources to work on CIP testing - the project is well behind where it should be. We need to get a lot more in place before more LTS kernels go EOL and everyone jumps to SLTS... | 13:34 |
| patersonc | Thanks jki | 13:34 |
| jki | discussed with Quirin today, we have a resolution strategy now | 13:34 |
| jki | patersonc: thanks for bringing this up! so true | 13:35 |
| patersonc | I guess there's nothing else for testing this week... | 13:37 |
| jki | ok, then moving on... | 13:38 |
| jki | 5 | 13:38 |
| jki | 4 | 13:38 |
| jki | 3 | 13:38 |
| jki | 2 | 13:38 |
| jki | 1 | 13:38 |
| jki | #topic AOB | 13:38 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:38 | |
| jki | iwamatsu__: there are quite a few open MRs on the config repo - already had time to check? | 13:39 |
| jki | specifically the x86 generic one would help to also move forward with isar-cip-core | 13:39 |
| iwamatsu__ | I am reviewing now, so I think I can merge it tomorrow. | 13:40 |
| jki | great, TIA! | 13:41 |
| jki | other topics? | 13:41 |
| jki | just checking: next week is public holiday again for me | 13:41 |
| jki | I may not be available | 13:42 |
| pave1 | I have something just before.... | 13:42 |
| pave1 | ...but there's good chance it ends in time. | 13:43 |
| iwamatsu__ | I can takeover. | 13:43 |
| patersonc | I won't be here next Thursday, apologies | 13:43 |
| jki | ok, if the round becomes too small, make it short or skip directly | 13:44 |
| jki | but thanks for your offer, iwamatsu-san | 13:44 |
| iwamatsu__ | :) | 13:44 |
| pave1 | So cancel or keep? | 13:45 |
| iwamatsu__ | If there are few participants, I think it is okay to cancel. | 13:48 |
| jki | looks like | 13:48 |
| arisut | ok for me too | 13:48 |
| uli_ | i'm ok either way | 13:48 |
| jki | use email for anything urgent to discuss | 13:48 |
| arisut | yeah me too | 13:48 |
| masami | ok | 13:48 |
| pave1 | Ok, so next one is cancelled. See you in 14 days. | 13:49 |
| jki | good | 13:50 |
| arisut | see you pave1 | 13:50 |
| jki | then closing for today... | 13:50 |
| jki | 5 | 13:50 |
| jki | 4 | 13:50 |
| jki | 3 | 13:50 |
| jki | 2 | 13:50 |
| jki | 1 | 13:50 |
| jki | #endmeeting | 13:50 |
| collab-meetbot` | Meeting ended Thu May 23 13:50:48 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:50 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-23-13.02.html | 13:50 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-23-13.02.txt | 13:50 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-23-13.02.log.html | 13:50 |
| *** 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:50 | |
| jki | thanks you all | 13:50 |
| arisut | thanks you | 13:51 |
| pave1 | Thank you! | 13:51 |
| iwamatsu__ | Thank you | 13:51 |
| masami | thank you | 13:51 |
| *** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:51 | |
| uli_ | thanks | 13:51 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:d591:a45e:1147:25d6> has quit IRC (Quit: Client closed) | 13:55 | |
| *** jki <jki!~jki@62.156.206.57> has quit IRC (Quit: Leaving) | 15:54 | |
| *** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has quit IRC (Ping timeout: 260 seconds) | 21:46 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!