| *** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has joined #cip | 05:56 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 05:56 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 05:57 | |
| *** frieder <frieder!~frieder@i59F664FA.versanet.de> has joined #cip | 07:07 | |
| *** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has joined #cip | 12:53 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:ab09:f648:2a3d:eb60> has joined #cip | 12:58 | |
| *** jki <jki!~jki@77.47.46.127> has joined #cip | 13:01 | |
| jki | hi everyone | 13:01 |
|---|---|---|
| iwamatsu__ | hello | 13:02 |
| patersonc | Afternoon | 13:02 |
| masami | hi | 13:02 |
| pave1 | Hi! | 13:02 |
| uli | hello | 13:02 |
| arisut | hi | 13:02 |
| jki | let's start then | 13:03 |
| jki | #startmeeting CIP IRC weekly meeting | 13:03 |
| collab-meetbot | Meeting started Thu Jun 13 13:03:05 2024 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:03 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:03 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:03 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | #topic AI review | 13:03 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | - prepare blog entry on SLTS kernel state and challenges [Jan] | 13:03 |
| jki | no news, unfortunately | 13:03 |
| jki | I've nothing more recorded otherwise | 13:03 |
| jki | 5 | 13:04 |
| jki | 4 | 13:04 |
| 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.93. | 13:04 |
| uli | i've been reviewing 6.1.93 | 13:04 |
| masami | This week reported 8 new CVEs and 4 updated CVEs. | 13:04 |
| iwamatsu__ | I reviewed 6.1.93. | 13:04 |
| jki | anything else? | 13:06 |
| jki | 8 CVEs sound like vacation phase | 13:06 |
| pave1 | Yeah, we'll just get 196 next week :-). | 13:07 |
| jki | 5 | 13:07 |
| jki | 4 | 13:07 |
| jki | 3 | 13:07 |
| jki | 2 | 13:07 |
| jki | 1 | 13:07 |
| jki | #topic Kernel release status | 13:07 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:07 | |
| jki | 4.4 is late | 13:07 |
| uli | there were concerns about the quality of a patch | 13:08 |
| uli | so pave1 suggested to wait for the 4.19 release | 13:08 |
| uli | but that release hasn't come so far | 13:08 |
| uli | i'm inclined to drop the patch and move on | 13:08 |
| pave1 | Yeah. I don't believe we should be basing our releases on 4.19-rc. | 13:08 |
| jki | which patch in particular? | 13:08 |
| uli | x86/insn: Fix PUSH instruction in x86 instruction decoder opcode map | 13:08 |
| pave1 | 4.19.316-rc1 is out, so I expect 4.19.316 in few days. | 13:09 |
| uli | stable doesn't have a schedule; we do | 13:09 |
| pave1 | I mean -- there's not neccessarily anything wrong with the named patch, | 13:10 |
| pave1 | but if it was not yet released in part of 4.19.x, we should not be releasing it. | 13:10 |
| uli | that makes it impossible to relese anything on time | 13:11 |
| pave1 | No, why? | 13:11 |
| uli | i've been basing almost every release so far on an rc | 13:11 |
| pave1 | Don't :-). | 13:11 |
| uli | because the release doesn't happen when we need it | 13:11 |
| pave1 | Just take patches from latest version than happen, and ignore anything newer. | 13:11 |
| uli | that's an option | 13:12 |
| pave1 | Patches that are not in in 4.19.x are straight from mainline, and untested. | 13:12 |
| uli | but introduces quite some latency | 13:12 |
| pave1 | They may be completely bogus, breaking build, etc. | 13:12 |
| pave1 | Yes, I believe we should live with latency. | 13:12 |
| pave1 | Mainline stuff gets applied to queue-4.19. Then -rc1 comes | 13:13 |
| pave1 | people test that, and bad patches are dropped. Then we get 4.19.x | 13:13 |
| pave1 | We should ignore everything before it gets to 4.19.x | 13:13 |
| uli | ok, i can live with that. | 13:13 |
| jki | unless it looks very critical - but that requires special handling anyway | 13:14 |
| pave1 | Yep. | 13:14 |
| pave1 | and when things do get very critical, we do get -stable releases, anyway. | 13:14 |
| uli | i can do that from now on. | 13:15 |
| jki | good | 13:15 |
| pave1 | Thank you :-). | 13:15 |
| jki | then 4.4 will come soon | 13:15 |
| uli | yep. | 13:15 |
| pave1 | With this one, 4.19.316 should happen around Monday, so it might be easy to just wait. | 13:15 |
| pave1 | (And verify the patches are still there in the release). | 13:16 |
| pave1 | Or we can stash them and reapply after the release. | 13:16 |
| uli | i can wait until monday night, and if there isn't anything yet, i'll release base on .315 | 13:16 |
| uli | *based | 13:17 |
| jki | good, moving on... | 13:17 |
| jki | 5 | 13:17 |
| jki | 4 | 13:17 |
| jki | 3 | 13:17 |
| jki | 2 | 13:17 |
| pave1 | Works for me. "Sat, 15 Jun 2024 11:31:50 +0000." is the date Greg quoted for 4.19.316. | 13:17 |
| jki | 1 | 13:17 |
| uli | ok | 13:18 |
| jki | #topic Kernel testing | 13:18 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:18 | |
| arisut | no news afaik | 13:18 |
| patersonc | jki: Are there any updates for the Siemens LAVA lab? | 13:18 |
| arisut | looks still down from last time I checked | 13:19 |
| jki | nope, but our team was on a Retreat (partial excuse) | 13:19 |
| patersonc | Okay | 13:19 |
| patersonc | I'm not sure I have any news this week | 13:21 |
| jki | anything else on testing? | 13:21 |
| jki | 5 | 13:22 |
| jki | 4 | 13:22 |
| jki | 3 | 13:22 |
| jki | 2 | 13:22 |
| jki | 1 | 13:22 |
| jki | #topic AOB | 13:22 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:22 | |
| pave1 | I'll be travelling for two weeks starting Jun 24. | 13:22 |
| masami | I will be absent from the next meeting and the one after that. | 13:22 |
| jki | ok | 13:22 |
| arisut | I will absent next meeting | 13:23 |
| pave1 | There's Linux RT meeting at Jun 26; not sure if I can make it there. | 13:23 |
| jki | I should be there | 13:23 |
| jki | can wear both hats this time | 13:24 |
| pave1 | Iwamatsu-san also has our hat :-). | 13:24 |
| iwamatsu__ | yes :) | 13:25 |
| jki | does that time slot fit you? | 13:25 |
| iwamatsu__ | it is no problem. | 13:26 |
| jki | ok, fine | 13:26 |
| jki | something else: we discussed internally to look into the topic of mapping CVEs (via commits) on kernel configs | 13:26 |
| jki | is anyone aware of preexisting public approaches? | 13:27 |
| jki | seems not :) | 13:29 |
| pave1 | So in git@gitlab.com:cip-project/cip-kernel/lts-commit-list.git | 13:29 |
| pave1 | we have bin/commit.py. | 13:29 |
| pave1 | That computes "relevant" for a commit based on source file list. | 13:29 |
| masami | https://events.linuxfoundation.org/archive/2022/open-source-summit-japan/program/schedule/ | 13:29 |
| pave1 | And we generate source file lists manually from our configs from time to time. | 13:29 |
| masami | title "Config based CVE matching for | 13:30 |
| masami | Linux kernel" | 13:30 |
| pave1 | We use that for reviews. | 13:30 |
| jki | found it - thanks! | 13:30 |
| masami | koverage command in kmax repo looks helpful. https://github.com/paulgazz/kmax | 13:30 |
| jki | I think it would be good for us to execute automated mapping (as far as possible) for incoming CVEs as well as config changes | 13:32 |
| jki | we may have some time to try out something and then discuss further | 13:33 |
| jki | ok - anything else? | 13:35 |
| jki | 5 | 13:36 |
| jki | 4 | 13:36 |
| jki | 3 | 13:36 |
| jki | 2 | 13:36 |
| jki | 1 | 13:36 |
| jki | #endmeeting | 13:36 |
| collab-meetbot | Meeting ended Thu Jun 13 13:36:22 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:36 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/06/cip.2024-06-13-13.03.html | 13:36 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/06/cip.2024-06-13-13.03.txt | 13:36 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/06/cip.2024-06-13-13.03.log.html | 13:36 |
| *** 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:36 | |
| jki | thanks, all! | 13:36 |
| uli | thank you | 13:36 |
| iwamatsu__ | thank you | 13:36 |
| masami | thank you | 13:36 |
| pave1 | Thank you! | 13:36 |
| *** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:36 | |
| arisut | thank you | 13:36 |
| arisut | /quit | 13:42 |
| * patersonc waves | 13:42 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:ab09:f648:2a3d:eb60> has quit IRC (Quit: Client closed) | 13:47 | |
| *** jki <jki!~jki@77.47.46.127> has quit IRC (Quit: Leaving) | 14:10 | |
| *** frieder <frieder!~frieder@i59F664FA.versanet.de> has quit IRC (Remote host closed the connection) | 14:21 | |
| *** prabhakalad <prabhakalad!~prabhakar@147.161.225.104> has quit IRC (Ping timeout: 264 seconds) | 21:05 | |
| *** prabhakalad <prabhakalad!~prabhakar@147.161.225.83> has joined #cip | 21:06 | |
| *** prabhakalad <prabhakalad!~prabhakar@147.161.225.83> has quit IRC (Ping timeout: 256 seconds) | 21:13 | |
| *** prabhakalad <prabhakalad!~prabhakar@147.161.225.104> has joined #cip | 21:13 | |
| *** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has quit IRC (Ping timeout: 268 seconds) | 21:45 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!