Thursday, 2026-05-21

*** collab-meetbot <collab-meetbot!~supybot@ec2-34-211-103-193.us-west-2.compute.amazonaws.com> has joined #cip00:15
*** ChanServ sets mode: +o collab-meetbot00:16
*** collab-meetbot` <collab-meetbot`!~supybot@ec2-35-167-58-160.us-west-2.compute.amazonaws.com> has quit IRC (Remote host closed the connection)00:22
*** sskartheekadivi <sskartheekadivi!~sskarthee@user/sskartheekadivi> has quit IRC (Ping timeout: 256 seconds)05:42
*** sskartheekadivi <sskartheekadivi!~sskarthee@user/sskartheekadivi> has joined #cip05:44
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:48
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)05:53
*** frieder <frieder!~frieder@88.130.219.81> has joined #cip06:36
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip07:29
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 244 seconds)07:43
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip10:18
*** jki <jki!~jki@195.145.170.160> has joined #cip11:52
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip11:59
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has joined #cip12:00
iwamatsuhello12:03
pave1Hi!12:03
uli_hello12:03
masamihello12:03
iwamatsuJan is not here yet.12:03
iwamatsuhm, I takeover today.12:06
iwamatsu #startmeeting CIP IRC weekly meeting12:06
iwamatsu#startmeeting CIP IRC weekly meeting12:06
collab-meetbotMeeting started Thu May 21 12:06:39 2026 UTC and is due to finish in 60 minutes.  The chair is iwamatsu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:06
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:06
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:06
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:06
iwamatsu#topic AI review12:06
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:06
iwamatsuNo AI12:06
iwamatsu512:06
iwamatsu412:07
iwamatsu312:07
iwamatsu212:07
iwamatsu112:07
iwamatsu#topic Kernel maintenance updates12:07
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:07
uli_i pushed 4.4 this week, and 4.19-rc earlier today12:07
pave1I was reviewing 6.12.88, .90.12:07
iwamatsuI reiviewed 6.12.83, 84 and 85.12:08
masamiThis week reported 4 new CVEs and 25 updated CVEs.12:08
iwamatsuanything else?12:08
pave1masami: Any idea if those "famous" bugs12:08
iwamatsu512:08
iwamatsu412:08
iwamatsu312:08
pave1already hit the mainline or stable?12:08
iwamatsu212:08
iwamatsuIs it like Dirty Frag?12:12
pave1Dirty frag and freinds, I was wondering if there are fixes in mainline/stable already.12:12
pave1But we can discuss over emali.12:12
masamipavel: I I think dirty frag like bugs are more repored for while12:13
jkihi all, sorry, got pulled out by colleagues12:13
jkiwhat about the ptrace bug?12:15
jkiis that fixes in CIP kernels as well now?12:15
pave1That one has hit the stable.12:15
pave1...but I don't believe we have it in all cip kernels.12:16
pave1...do you know what impact is that? (And if it has name / cve?)12:16
uli_i picked it for the next 4.19 from 5.10, so it will make it into the next 4.4.12:17
jkihttps://app.opencve.io/cve/CVE-2026-4633312:17
jkishould be this one12:17
iwamatsuabout ptrace issue,  this issue is not fixed in 6.12.y-cip.12:17
iwamatsuI am going to release it tomorrow.12:18
jkifix in 6.12.8912:18
iwamatsuyes.12:18
masamianother LPE is PinTheft. It is published 2 days ago. https://github.com/v12-security/pocs/tree/09e835b587bf71249775654061ae4c79e92cf430/pintheft12:18
pave1Needs "CAP_SYS_PTRACE" to exploit.12:18
pave1That's ... non issue.12:18
pave1(Basically.)12:19
jkiyes (maybe except with fancy containers)12:19
pave1Yes. I believe we have bigger problems to worry about.12:19
jkiwe should still track and - if needed - decide whether to backport or document as unfixed12:20
pave1I believe it will eventually be backported to everything. (uli?)12:21
pave1But I don't believe ptrace bug warrants extra releases.12:21
jkiit should be bundled with other fixes, yes12:22
pave1+112:22
iwamatsuanything else?12:23
iwamatsu512:23
iwamatsu412:23
iwamatsu312:23
iwamatsu212:23
iwamatsu112:23
iwamatsu#topic Kernel release status12:23
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:23
jki4.4-rt is late IIRC12:24
pave1Aha, forgot about 4.4 with all the releases.12:24
pave14.4-cip is out, can do -rt.12:24
iwamatsugot it , thanks.12:24
iwamatsuanything else?12:25
iwamatsu512:25
iwamatsu412:25
iwamatsu312:25
iwamatsu212:25
iwamatsu112:25
iwamatsu#topic Kernel testing12:25
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:25
patersoncLAVA server upgrade day today12:25
patersoncIt's done, but there's a DNS/Cloudflare issue that I'm waiting on LF to fix...12:26
jkiQuirin is absent - may affect Siemens lab Munich then12:26
iwamatsupatersonc: ok, thanks for your work.12:27
patersoncI'll email the list once the server is back online again12:27
iwamatsuanything else?12:28
iwamatsu512:28
iwamatsu412:28
iwamatsu312:28
iwamatsu212:28
iwamatsu112:28
iwamatsu#topic AOB12:28
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:28
jkiUli and I will be at Embedded Recipes next week12:29
jkiunfortunately, there is not break during our irc slot12:29
jkibut maybe we can do that in parallel ;)12:29
pave1:-)12:30
jkiif not, someone please jump in again12:30
iwamatsuOK, if it is difficult, I will takeover.12:31
iwamatsuother topic?12:31
jkiTIA!12:31
iwamatsu512:31
iwamatsu412:31
iwamatsu312:31
iwamatsu212:31
iwamatsu112:31
iwamatsu#endmeeting12:31
collab-meetbotMeeting ended Thu May 21 12:31:59 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:31
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/05/cip.2026-05-21-12.06.html12:31
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/05/cip.2026-05-21-12.06.txt12:31
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/05/cip.2026-05-21-12.06.log.html12:31
*** 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/"12:31
iwamatsuThank you!12:32
jkibye!12:32
uli_thanks12:32
pave1Thank you!12:32
masamithank you12:32
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:32
patersoncCheers12:33
ysionneauis 4.19 affected by https://github.com/v12-security/pocs/tree/09e835b587bf71249775654061ae4c79e92cf430/pintheft ?12:35
jkiah, nice - the LPE of the day12:49
jkiformally spoken, the 4.19-cip should not be affected because you need to have CONFIG_IO_URING enabled, and that is not the case for the CIP kernel configs (unless I missed something)12:50
jki...is not the case for the 4.19 cip configs - newer CIP kernels have this on12:50
ysionneauwell, we don't have exactly cip config :p12:52
jkiin fact, there was no IO_URING in 4.19 yet12:53
jkiso you should be safe, irrespective of the config12:53
ysionneauok good, thanks :)12:53
jkidisclaimer: this is just an ad-hoc analysis12:53
*** vigneshr <vigneshr!uid375618@user/vigneshr> has quit IRC (Quit: Connection closed for inactivity)12:53
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Remote host closed the connection)13:01
*** jki <jki!~jki@195.145.170.160> has quit IRC (Quit: Leaving)13:06
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip15:12
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 252 seconds)16:26
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip16:41
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 250 seconds)17:12
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip17:18
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 252 seconds)17:28
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip17:29
*** frieder <frieder!~frieder@88.130.219.81> has quit IRC (Remote host closed the connection)17:41
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 248 seconds)17:42
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip17:46
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)17:51
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip17:52
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)18:03
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip18:05
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Remote host closed the connection)19:09
*** sskartheekadivi <sskartheekadivi!~sskarthee@user/sskartheekadivi> has quit IRC (Ping timeout: 250 seconds)21:01
*** sskartheekadivi <sskartheekadivi!~sskarthee@user/sskartheekadivi> has joined #cip21:17

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