| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 05:57 | |
| *** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has joined #cip | 05:58 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 06:26 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 07:13 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 08:25 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 12:27 | |
| *** jki <jki!~jki@46.128.88.20> has joined #cip | 13:00 | |
| jki | hi all | 13:00 |
|---|---|---|
| pave1 | hi! | 13:00 |
| patersonc | Hello | 13:00 |
| jki | small round today due to vacations... | 13:02 |
| jki | ok, start it nevertheless | 13:02 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot | Meeting started Thu May 2 13:02:38 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:02 |
| jki | [re-]started, but I was too optimistic. so: ongoing | 13:03 |
| jki | I don't think we have more AI, so | 13:03 |
| jki | 5 | 13:03 |
| jki | 4 | 13:03 |
| jki | 3 | 13:03 |
| jki | 2 | 13:03 |
| jki | 1 | 13:03 |
| jki | #topic Kernel maintenance updates | 13:03 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| pave1 | I did reviews, 6.1.88 and .90 | 13:03 |
| pave1 | Yesterday was holiday here, May 8th will be another one. | 13:04 |
| jki | ok | 13:06 |
| jki | how about the 4.19-rt? | 13:06 |
| pave1 | I'll take a look. | 13:06 |
| jki | thanks | 13:07 |
| jki | "This week reported 207 new CVEs and 10 updated CVEs." - going up again | 13:08 |
| jki | pavel: thanks for summarizing the HW CVEs on the list | 13:08 |
| pave1 | Yep. And the titles are still copy-pasted so they make no sense in CVE context. | 13:08 |
| pave1 | jki: No problem, but I did not exactly get a response there. | 13:09 |
| jki | at least we warned, no one can complain | 13:09 |
| pave1 | Yes. There's no way to fix that, anyway. We are just piling workarounds, but underlying bugs are not fixable. | 13:10 |
| patersonc | Last week was OSS-NA, so only a few CVEs reported. This week... | 13:10 |
| jki | are the CVEs documented as unfixed in our affected kernels? | 13:10 |
| uli | hi | 13:10 |
| uli | sorry for being late. i'm preparing the next 4.4 | 13:11 |
| pave1 | No, we should probably fix that. | 13:11 |
| jki | KNOWN-BUGS is only in 4.4 so far, right? | 13:12 |
| pave1 | But this whole thing is a bit of mess w.r.t. CVEs. | 13:12 |
| jki | well, yes | 13:12 |
| jki | but we could at least use that manually for the major CVEs | 13:12 |
| pave1 | The CVEs should be against the CPUs... but we have CVEs for bug workarounds... | 13:13 |
| jki | CVEs are CVEs | 13:13 |
| pave1 | Well.. These days CVEs are spam. | 13:13 |
| pave1 | :-( | 13:13 |
| pave1 | I'll look at KNOWN-BUGS for 4.19/5.10. | 13:14 |
| jki | the HW CVEs are unique and properly described, and if we add them to our kernels that do not even have mitigation attempts, that should be clear | 13:14 |
| jki | ok - anything else on maintenance? | 13:15 |
| pave1 | Yes. But my observation is that CVEs start to have "tree structure" in the case of CPU bugs. | 13:15 |
| pave1 | Intel CPU leaks secrets. | 13:15 |
| pave1 | Then we have kernel not doing proper workarounds for Intel bug. | 13:16 |
| pave1 | Plus we know many of the workarounds are just incomplete, they are just patching the exploits at this point. | 13:16 |
| pave1 | Ok, lets continue. | 13:16 |
| jki | 5 | 13:17 |
| jki | 4 | 13:17 |
| jki | 3 | 13:17 |
| jki | 2 | 13:17 |
| jki | 1 | 13:17 |
| jki | #topic Kernel release status | 13:17 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:17 | |
| jki | just 4.19-rt is late, we already discussed | 13:17 |
| jki | 5 | 13:17 |
| jki | 4 | 13:17 |
| jki | 3 | 13:17 |
| jki | 2 | 13:17 |
| jki | 1 | 13:17 |
| jki | #topic Kernel testing | 13:17 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:17 | |
| jki | patersonc: anything from you? | 13:19 |
| patersonc | Not really! | 13:19 |
| jki | our lab is still in reconstruction, hope to have that fixed "soon" | 13:20 |
| patersonc | Thanks, I meant to ask | 13:20 |
| jki | on Tuesday, the network socket was without network yet... | 13:20 |
| jki | ok | 13:20 |
| patersonc | :) | 13:21 |
| jki | moving on... | 13:21 |
| jki | 5 | 13:21 |
| jki | 4 | 13:21 |
| jki | 3 | 13:21 |
| jki | 2 | 13:21 |
| jki | 1 | 13:21 |
| jki | #topic AOB | 13:21 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:21 | |
| jki | the 9th is public holiday here (and possibly also elsewhere) | 13:21 |
| jki | I'm out for next week | 13:22 |
| pave1 | Do we cancel the meeting, or do I just take over it? | 13:23 |
| jki | if you can take over, we don't need to cancel | 13:23 |
| pave1 | Ok, I believe I can do that. | 13:23 |
| jki | I suspect, Japan will be back, and if no one else is on leave... | 13:23 |
| jki | thanks! | 13:23 |
| jki | anything else for today? | 13:24 |
| jki | 5 | 13:25 |
| jki | 4 | 13:25 |
| jki | 3 | 13:25 |
| jki | 2 | 13:25 |
| jki | 1 | 13:25 |
| jki | #endmeeting | 13:25 |
| collab-meetbot | Meeting ended Thu May 2 13:25:08 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:25 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-02-13.02.html | 13:25 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-02-13.02.txt | 13:25 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/05/cip.2024-05-02-13.02.log.html | 13:25 |
| *** 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:25 | |
| jki | thanks all! | 13:25 |
| pave1 | Thank you! | 13:25 |
| patersonc | Cheers | 13:25 |
| uli | thanks | 13:25 |
| *** jki <jki!~jki@46.128.88.20> has quit IRC (Quit: Leaving) | 13:27 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 14:28 | |
| *** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has quit IRC (Quit: Connection closed for inactivity) | 16:20 | |
| *** rajm <rajm!~robert@macc-04-b2-v4wan-169608-cust697.vm21.cable.virginm.net> has quit IRC (Ping timeout: 255 seconds) | 21:46 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!