| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed) | 00:18 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 03:49 | |
| *** arnd <arnd!sid21101@id-21101.hampstead.irccloud.com> has quit IRC (Server closed connection) | 04:33 | |
| *** arnd <arnd!sid21101@id-21101.hampstead.irccloud.com> has joined #cip | 04:33 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:34 | |
| *** frieder <frieder!~frieder@i577B9007.versanet.de> has joined #cip | 07:06 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 255 seconds) | 07:27 | |
| *** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 256 seconds) | 08:32 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip | 09:45 | |
| *** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip | 09:45 | |
| *** uli <uli!~quassel@static.153.40.69.159.clients.your-server.de> has joined #cip | 12:10 | |
| *** hunter <hunter!~hunter@d5ppdgz8zjprl3tys18-4.rev.dnainternet.fi> has joined #cip | 12:18 | |
| *** hunter <hunter!~hunter@d5ppdgz8zjprl3tys18-4.rev.dnainternet.fi> has quit IRC (Client Quit) | 12:19 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed) | 12:31 | |
| *** masami <masami!~masami@FL1-125-195-134-41.tky.mesh.ad.jp> has joined #cip | 12:45 | |
| *** hunter <hunter!~hunter@d5ppdg4q7-ktrmynjd8-4.rev.dnainternet.fi> has joined #cip | 12:59 | |
| *** jki <jki!~jki@195.145.170.186> has joined #cip | 12:59 | |
| jki | hi all | 13:00 |
|---|---|---|
| pave1 | hi! | 13:00 |
| hunter | hello! | 13:00 |
| uli | hello | 13:00 |
| arisut | hi | 13:00 |
| iwamatsu | hi | 13:00 |
| masami | hi | 13:01 |
| jki | let's go | 13:01 |
| jki | #startmeeting CIP IRC weekly meeting | 13:01 |
| collab-meetbot | Meeting started Thu Nov 16 13:01:52 2023 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 review | 13:02 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | nothing in my logs | 13:02 |
| jki | moving directly on... | 13:02 |
| jki | #topic Kernel maintenance updates | 13:02 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| uli | i'm reviewing 6.1.63 | 13:02 |
| masami | This week reported 4 new CVEs and 0 updated CVEs. | 13:02 |
| iwamatsu | I am reviewing 6.1.63-rc. | 13:03 |
| pave1 | I was reviewing AUTOSEL, now reviewing 6.1.63. | 13:03 |
| jki | more topics? | 13:06 |
| 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 | 13:07 |
| uli | on track | 13:07 |
| pave1 | 4.4-rt and 4.19-rt is ok. | 13:08 |
| jki | 4.19 | 13:08 |
| iwamatsu | on track | 13:08 |
| jki | 5.10 | 13:08 |
| iwamatsu | on track | 13:09 |
| pave1 | 5.10-rt is due in 3 days. Unfortunately, we do not have good match, -cip is on 5.10.200 and -rt is on 5.10.199 | 13:09 |
| pave1 | I asked for 5.10.200-rt, but no reply so far. | 13:09 |
| pave1 | I can probably mix -cipi-rt from what we have, if they don't respond. | 13:10 |
| jki | that was my thought as well | 13:10 |
| jki | 6.1 | 13:11 |
| iwamatsu | on track | 13:11 |
| pave1 | -rt is due in 13 days, so I'm looking for suitable -rt. | 13:11 |
| jki | okay... | 13:11 |
| jki | #topic Kernel testing | 13:12 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:12 | |
| jki | no Chris, no topics? :) | 13:14 |
| hunter | well | 13:14 |
| hunter | me, crhis and sietze are meeting next tuesday to discuss some things including utilizing SQUAD for testing | 13:15 |
| jki | great | 13:15 |
| jki | we have some outage in our lab, to be fixed the next days | 13:15 |
| hunter | ah hope it isn't too bad | 13:16 |
| jki | temporary lab using temporary hardware - you get what you asked for... | 13:16 |
| hunter | yep xD that is true | 13:17 |
| jki | ok, if there are no other testing topics... | 13:18 |
| jki | 5 | 13:18 |
| jki | 4 | 13:18 |
| jki | 3 | 13:18 |
| jki | 2 | 13:18 |
| jki | 1 | 13:18 |
| jki | #topic AOB | 13:18 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:18 | |
| jki | I actually have two by now | 13:18 |
| jki | who of CIP will participate in the RT Project meeting next Monday? | 13:19 |
| hunter | what is the RT project? | 13:19 |
| jki | preempt-rt project | 13:19 |
| hunter | ah okay | 13:19 |
| jki | CIP is a member, funding the upstreaming and maintenance | 13:19 |
| iwamatsu | next monday? | 13:19 |
| pave1 | If that's remote, I can likely do it. | 13:19 |
| iwamatsu | aha, ok. I am going to join it. | 13:20 |
| jki | we as Siemens are member as well, but I'm flying, and all colleagues are I asked are blocked | 13:20 |
| jki | it's 18:00 CET - might be mid of the night for you, iwamatsu-san ;) | 13:21 |
| iwamatsu | hehe, but it is no problem for me. | 13:21 |
| pave1 | :-) | 13:21 |
| jki | anyway, not only Siemens, I guess also CIP would be very interested now what is the reason that 6.7 didn't got -rt | 13:21 |
| jki | printk was apparently merged, the last official blocker | 13:21 |
| pave1 | jki: Well, my impression is that -rt is "always" going to be in the next kernel. Becuase that's just a lot of work. | 13:22 |
| jki | that was not what was communicated recently | 13:22 |
| pave1 | jki: Yes, it will be interesting to know the reasons, but it is really quite big project. | 13:23 |
| jki | no, for mainline to flip the config options, it's not that big anymore | 13:23 |
| jki | sure, there will be further optimizations needed afterwards | 13:23 |
| jki | but we are looking for remaining functional blockers - if any | 13:24 |
| jki | and CIP, we do not want to maintain our next SLTS kernel in two flavours anymore | 13:24 |
| pave1 | jki: We still likely will have to :-). preempt-rt being enabled != preempt-rt being enabled for everything we care about. | 13:25 |
| jki | so, also the path to get major optimizations resolved over the upcoming releases would be important | 13:25 |
| pave1 | (Ok, if the patches are small we can just ship rt-patched kernel and call it "cip"). | 13:25 |
| jki | well, let's see, at least ask for it and hopefully get answer | 13:25 |
| pave1 | So there will likely be explanations, and likely people will be asking. | 13:26 |
| pave1 | There will meeting minutes, I'm sure; I guess you'll get those? | 13:26 |
| jki | sure, but those are not interactive ;) | 13:26 |
| pave1 | Yep. I guess, as uusual, half of the meeting will be "why we are not merged, yet". | 13:27 |
| pave1 | If not, I can ask :-). | 13:27 |
| pave1 | But I doubt it will make much difference in the long run. | 13:28 |
| pave1 | What may make the difference -- we could try to influence priority of the architectures. | 13:28 |
| jki | for CIP, we basically need a roudmap towards end of 2024 | 13:29 |
| jki | 2024 LTS | 13:29 |
| jki | ok, thanks! | 13:29 |
| pave1 | Ok, I'll try to keep that in mind. | 13:29 |
| jki | second topic: I'm traveling towards East, and I will likely not be available the next two weeks at our normal slots | 13:30 |
| jki | actually, next 3: I'll be flying back from OSS J then :) | 13:30 |
| jki | would anyone be able to jump in? first for next week? | 13:31 |
| pave1 | I can do next week. | 13:31 |
| jki | perfect, thanks already! | 13:31 |
| jki | anyone with other topics? | 13:32 |
| pave1 | There's cool new x86 vulnerability. | 13:32 |
| pave1 | CVE-2023-23583. | 13:33 |
| jki | isn't that ucore-mitigated already? | 13:33 |
| pave1 | Not sure. This is the 'rex rep movsb', and yes, it should be fixed in microcode. | 13:33 |
| jki | rep rex movsb :) | 13:33 |
| jki | exactly | 13:34 |
| pave1 | Aha, so that's old news then :-). | 13:34 |
| jki | I'm not aware of OS measures / mitigations, except for loading that ucode | 13:34 |
| pave1 | ack. | 13:34 |
| jki | it's also not affecting all types of Intel CPUs | 13:35 |
| jki | "just" some more recent generations | 13:35 |
| jki | ok - anything else? | 13:36 |
| 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 Nov 16 13:36:40 2023 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/2023/11/cip.2023-11-16-13.01.html | 13:36 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/11/cip.2023-11-16-13.01.txt | 13:36 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/11/cip.2023-11-16-13.01.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 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:36 | |
| jki | thanks all! | 13:36 |
| uli | thanks | 13:36 |
| iwamatsu | thank you | 13:36 |
| masami | thank you | 13:36 |
| *** masami <masami!~masami@FL1-125-195-134-41.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:37 | |
| hunter | thanks! see everyone in the next one | 13:37 |
| *** hunter <hunter!~hunter@d5ppdg4q7-ktrmynjd8-4.rev.dnainternet.fi> has quit IRC (Quit: Konversation terminated!) | 13:37 | |
| *** jki <jki!~jki@195.145.170.186> has quit IRC (Quit: Leaving) | 13:37 | |
| pave1 | Thank you! | 13:38 |
| *** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Server closed connection) | 15:25 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip | 15:25 | |
| *** gregkh <gregkh!sid42031@id-42031.ilkley.irccloud.com> has quit IRC (Server closed connection) | 15:34 | |
| *** gregkh <gregkh!sid42031@id-42031.ilkley.irccloud.com> has joined #cip | 15:34 | |
| *** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 256 seconds) | 16:31 | |
| *** frieder <frieder!~frieder@i577B9007.versanet.de> has quit IRC (Remote host closed the connection) | 19:23 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Server closed connection) | 19:39 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 19:39 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip | 20:31 | |
| *** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip | 20:31 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 240 seconds) | 22:48 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed) | 23:56 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!