Thursday, 2026-05-14

« Wednesday, 2026-05-13 Index Friday, 2026-05-15 »
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:55
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)06:25
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has joined #cip11:40
*** cbeznea_ <cbeznea_!~cbeznea@82.78.167.139> has joined #cip11:45
*** jki <jki!~jki@46.128.82.95> has joined #cip12:00
jkihi all12:00
iwamatsuhello12:00
uli_hello12:00
masamihello12:00
jki#startmeeting CIP IRC weekly meeting12:01
collab-meetbot`Meeting started Thu May 14 12:01:11 2026 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:01
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:01
jki#topic AI review12:01
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:01
jkinone12:01
jki512:01
jki412:01
jki312:01
jki212:01
jki112:01
jki#topic Kernel maintenance updates12:01
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:01
masamiThis week reported 215 new CVEs and 7 updated CVEs.12:01
uli_i'm working on the next 4.412:01
iwamatsuI reiviewed 6.12.82.12:02
jkiwhat's the state of dirty frag and the rxrpc thing in our queues?12:03
uli_4.19 is affected by one of the two issues; the 5.10 patch applies without changes12:03
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip12:03
uli_4.4 is not affacted12:03
uli_affected12:03
pave1I am reviewing 6.12.68, .8812:04
jkiso, handle like copy fail and release earlier as well?12:05
jkiall stable kernels should be fixed by now IIUC12:05
jkior only propose mitigations to our users (disable feature/module)?12:05
pave1We probably should do that.12:05
pave1Releases.12:06
iwamatsu+112:06
jkiok12:06
uli_no opinion myself, i'm ok either way12:06
pave1It would help if we knew if there's another one12:06
pave1pending.12:06
uli_there is cve-2026-4630012:07
uli_fix is not in mainline yet12:07
masamiyes. it is another Dirty Frag vulnerability class12:07
jkiwhich one is that?12:07
iwamatsuhttps://github.com/v12-security/pocs/tree/main/fragnesia12:07
masamimitigation is same as for dirtyfrag12:09
jki"nice"12:09
jkiis a patch under discussion at least?12:09
uli_https://lists.openwall.net/netdev/2026/05/13/7912:10
jkijust spotted it, looking for a thread now12:10
jkiwell, might be worth to wait a day then, no?12:11
uli_i would say so12:11
pave1agreed.12:11
jkibut the other fixes could be staged already12:12
jkiokay (or not...)12:13
jkimore on maintenance?12:13
patersonccbeznea_ posted a fix for the USB issue that is broken currently in CIP 5.10: https://lore.kernel.org/all/20260514111300.2152386-1-claudiu.beznea@kernel.org/. Do we want to fix something directly in CIP? Or wait for it to filter through LTS? I'm keen to get CIP booting again...12:13
iwamatsuWe need to wait for the LTS version that apply it.12:15
pave1We should probably merge something before next release.12:15
iwamatsuIf it's applied , should we cherry-pick it without waiting for LTS?12:16
patersoncLTS would probably be faster than getting it into mainline :)12:17
pave1I'd say so. We have regression on supported board.12:17
pave1We can make exceptions here.12:17
cbeznea_the stable v5.10 backport that triggered the issue we are seeing currently with CIP 5.10 was wrong, as Pavel pointed out in the thread https://lore.kernel.org/all/20260501225859.504868-1-nobuhiro.iwamatsu.x90@mail.toshiba . Maybe we could pick this small fix until the mainline is fixed. The USB PHY tend to be slow even for fixes12:18
jkiso, the workaround of spinning instead of sleeping was not accepted?12:18
jkiIIRC, that was only aligning to current mainline, and it would be gone again after that more complex solution above is accepted12:19
cbeznea_I checked 5.10 stable trees few days ago but didn't notice any fix integrated12:19
pave1Agreed it is right workaround but Greg did not react to followup mail.12:20
pave1We should just take msleep -> mdelay into cip.12:20
pave1And let mainline / stable figure out better fix once12:21
pave1our boards are booting.12:21
iwamatsuOK, agree.12:22
jkiperfect12:22
patersoncThanks12:22
cbeznea_thanks!12:22
iwamatsuNow, let's apply  the mdelay patch to fix the problem.12:23
jkihttps://lore.kernel.org/netdev/agRhFtawP06hWyRa@v4bel/ - more frag stuff, unclear if exploitable at this point12:23
jkilet's cross fingers that we won't have to switch to weekly releases...12:24
jki...or even more12:24
pave1At some point we'll declare12:25
pave1that local exploits can wait....12:25
pave1But hopefully this should fly over in month or so.12:26
jkithe patterns may repeat: find a new vul-class, start AI, find lots of instances in short time, with exploits12:27
pave1Yep.12:27
jkiso, move on?12:27
jki512:28
jki412:28
jki312:28
jki212:28
jki112:28
jki#topic Kernel release status12:28
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:28
jkiall fine, but we know, why...12:28
jkianything to add?12:28
jki512:28
jki412:28
jki312:29
jki212:29
jki112:29
jki#topic Kernel testing12:29
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:29
arisutnothing to add12:29
patersoncWe now have stable-rc testing for 7.0.y12:29
pave1That was today?12:30
patersoncYes12:30
pave1Aha, good, thanks!12:31
jkimore on testing?12:32
patersoncNot from me12:33
jki512:33
jki412:33
jki312:33
jki212:33
jki112:33
jki#topic AOB12:33
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:33
jkifurther topics for today?12:34
jkiif not...12:35
jki512:35
jki412:35
jki312:35
jki212:35
jki112:35
jki#endmeeting12:35
collab-meetbot`Meeting ended Thu May 14 12:35:21 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:35
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/05/cip.2026-05-14-12.01.html12:35
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/05/cip.2026-05-14-12.01.txt12:35
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/05/cip.2026-05-14-12.01.log.html12:35
*** 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:35
jkithanks all!12:35
iwamatsuThank you12:35
uli_thanks12:35
masamithank you12:35
arisutthanks12:35
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:35
pave1Thank you!12:35
patersonccheers12:35
*** jki <jki!~jki@46.128.82.95> has quit IRC (Quit: Leaving)12:35
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Remote host closed the connection)12:54
*** cbeznea_ <cbeznea_!~cbeznea@82.78.167.139> has quit IRC (Ping timeout: 256 seconds)19:58
*** cbeznea <cbeznea!~cbeznea@82.78.167.139> has joined #cip20:04
*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has quit IRC (Read error: Connection reset by peer)20:14
*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has joined #cip20:15
*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has quit IRC (Read error: Connection reset by peer)20:18
*** cbeznea <cbeznea!~cbeznea@82.78.167.139> has quit IRC (Read error: Connection reset by peer)20:35
« Wednesday, 2026-05-13 Index Friday, 2026-05-15 »

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