Thursday, 2026-10-22

*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:52
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 244 seconds)05:56
*** frieder <frieder!~frieder@i59F664FB.versanet.de> has joined #cip06:02
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has quit IRC (Read error: Connection reset by peer)07:22
*** 073AALZPY <073AALZPY!~tmerciai@188.217.58.137> has joined #cip07:23
*** sskartheekadivi3 <sskartheekadivi3!~sskarthee@user/sskartheekadivi> has quit IRC (Ping timeout: 243 seconds)07:46
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has joined #cip07:48
*** 073AALZPY <073AALZPY!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 248 seconds)07:51
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 265 seconds)08:04
*** 092AAHXHH <092AAHXHH!~tmerciai@188.217.58.137> has joined #cip08:05
*** sskartheekadivi3 <sskartheekadivi3!~sskarthee@user/sskartheekadivi> has joined #cip08:05
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has joined #cip08:27
*** 092AAHXHH <092AAHXHH!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 260 seconds)08:30
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 258 seconds)09:31
*** tmerciai1 <tmerciai1!~tmerciai@188.217.58.137> has joined #cip09:32
*** tmerciai1 <tmerciai1!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 257 seconds)10:27
*** tmerciai1 <tmerciai1!~tmerciai@188.217.58.137> has joined #cip10:27
*** tmerciai1 <tmerciai1!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 241 seconds)10:59
*** 048AAH4IE <048AAH4IE!~tmerciai@188.217.58.137> has joined #cip10:59
*** frieder <frieder!~frieder@i59F664FB.versanet.de> has quit IRC (Read error: Connection reset by peer)11:26
*** frieder <frieder!~frieder@i59F664FB.versanet.de> has joined #cip11:43
*** tmerciai <tmerciai!~tmerciai@188.217.58.137> has joined #cip11:58
*** masami <masami!~masami@FL1-122-133-192-182.tky.mesh.ad.jp> has joined #cip11:59
*** 048AAH4IE <048AAH4IE!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 260 seconds)12:00
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has joined #cip12:00
iwamatsuhello12:01
pave1Hi!12:01
masamihello12:01
iwamatsu #startmeeting CIP IRC weekly meeting12:02
iwamatsu#startmeeting CIP IRC weekly meeting12:02
collab-meetbotMeeting started Thu Oct 22 12:02:08 2026 UTC and is due to finish in 60 minutes.  The chair is iwamatsu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:02
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:02
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:02
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:02
iwamatsu#topic AI review12:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:02
iwamatsuNo AI12:02
iwamatsuanything else ?12:02
iwamatsu512:02
iwamatsu412:03
iwamatsu312:03
iwamatsu212:03
iwamatsu112:03
iwamatsu#topic Kernel maintenance updates12:03
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:03
pave1I am reviewing 6.12.113 / 114.12:03
masamiThis week reported 440 new CVEs and 1149 updated CVEs.12:03
iwamatsuI was reviewing 6.12.109.12:03
iwamatsuThere are a lot of CVEs again this week...12:04
pave1iwamatsu: Are there any "interesting" ones?12:04
pave1From security news, apparently PHP has something major,12:05
pave1and some certificate authority had secret key of "4".12:05
pave1But I did not hear anything major about kernel.12:05
masamiCVE-2026-99999(PwnEscape) is new named vulnerability12:06
iwamatsuCVE-2026-9999912:06
iwamatsuyes12:06
pave1I'll take a look. At least they have easy-to-remember nubmer :-)12:07
iwamatsuThere’s been some talk lately about issues involving PHP and certificates.12:07
iwamatsuanything else?12:08
iwamatsu512:08
iwamatsu412:08
iwamatsu312:08
iwamatsu212:08
iwamatsu112:08
iwamatsu#topic Kernel release status12:08
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:08
*** tmerciai <tmerciai!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 254 seconds)12:08
iwamatsulinux-4.19.y-cip is late.12:09
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has joined #cip12:09
iwamatsumaybe, uli is working this.12:09
iwamatsuanything else?12:09
iwamatsu512:09
iwamatsu412:09
iwamatsu312:09
iwamatsu212:09
iwamatsu112:09
iwamatsu#topic Kernel testing12:10
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:10
iwamatsuping patersonc12:10
ulihi, sorry for being late. 4.19 is still in progress.12:10
iwamatsuuli: noted, thanks!12:11
*** sskartheekadivi3 <sskartheekadivi3!~sskarthee@user/sskartheekadivi> has quit IRC (Ping timeout: 260 seconds)12:11
patersoncHello12:11
iwamatsuhi patersonc12:11
patersoncI created an MR to add configs for 7.312:11
patersoncOnce merged the stable-rc  pipelines should work12:11
pave1Thank you!12:11
iwamatsuOh, sorry. I forgot it. I will check after this meeting.12:11
patersoncThanks12:12
iwamatsuanything else?12:12
patersoncNope12:12
pave1The 4 second -cip-rt delay detected by kernelci is on my radar,12:12
pave1but I am assuming it is some kind of test/config problem. I may12:13
pave1have some questions later.12:13
patersoncThanks12:13
iwamatsuRegarding the KernelCI test result notification, I don't mind receiving the emails.12:15
iwamatsuHowever, I align with the views of Pavel and Uli. therefore, please disable them.12:15
pave1Lets not do this. cip-devel is supposed to be useful for development, automated spam12:15
pave1will polute the archives etc.12:16
pave1Aha :-)12:16
iwamatsu:-)12:17
iwamatsu512:17
iwamatsu412:17
iwamatsu312:17
iwamatsu212:17
iwamatsu112:17
iwamatsu#topic AOB12:18
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:18
iwamatsu patch review workflow/coordination12:18
pave1CVE-2025-99999: if someone has information to share (such as12:18
pave1sha of the fix, webpages, exploit, versions where fixes hit -stable)12:19
pave1, please share them with cip-dev. Otherwise I'll try to compile something12:19
pave1later.12:19
masamimve-2026-99999. Mainline was fixed by 6785011f8b16abf40b1e9d8b2e332232b3e6882212:19
iwamatsupatch review: Do you have any information regarding this?12:20
pave1iwamatsu: I guess we do that over email?12:20
masamiall stable kernel were fixed.12:20
masamiyou can read details from https://pwn.ai/blog/pwnescape12:21
iwamatsuIf we do not currently have any opinions or information, we will discuss the matter via the mailing list.12:21
pave1masami: Thanks, I'm taking notes.12:22
iwamatsuIf there’s nothing else, let’s discuss it on the mailing list.12:22
pave1masami: In your opinion, do we need to roll some12:22
pave1early releases?12:22
iwamatsuI think a special release is necessary.12:23
masamiThis vulnerability is vm/container escape, so embed linux may not use these functionalities.12:23
iwamatsuWe need to verify that KVM is enabled.12:24
masamiyes12:25
pave1Some notes said local user can also exploit it. I guess we decide on the mailing list?12:26
iwamatsuKVM is set to 'm' on arm64 and x86 with some versions12:27
iwamatsupave1: OK. Lets talk on the mailing list.12:28
iwamatsuanything else?12:28
iwamatsu512:28
iwamatsu412:28
iwamatsu312:28
iwamatsu212:28
iwamatsu112:28
iwamatsu#endmeeting12:28
collab-meetbotMeeting ended Thu Oct 22 12:28:51 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:28
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/10/cip.2026-10-22-12.02.html12:28
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/10/cip.2026-10-22-12.02.txt12:28
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/10/cip.2026-10-22-12.02.log.html12:28
*** 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:28
ulithanks12:28
iwamatsuThanks all.12:29
masamithank you12:29
pave1Thank you!12:29
*** masami <masami!~masami@FL1-122-133-192-182.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:29
*** sskartheekadivi3 <sskartheekadivi3!~sskarthee@user/sskartheekadivi> has joined #cip12:35
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 267 seconds)14:12
*** tmerciai <tmerciai!~tmerciai@188.217.58.137> has joined #cip14:13
*** arisut <arisut!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo)14:33
*** arisut <arisut!~none@gentoo/developer/alicef> has joined #cip14:34
*** ChanServ sets mode: +o arisut14:34
*** sskartheekadivi3 <sskartheekadivi3!~sskarthee@user/sskartheekadivi> has quit IRC (Read error: Connection reset by peer)14:35
*** sskartheekadivi3 <sskartheekadivi3!~sskarthee@user/sskartheekadivi> has joined #cip14:35
*** frieder <frieder!~frieder@i59F664FB.versanet.de> has quit IRC (Ping timeout: 251 seconds)15:32
*** tmerciai <tmerciai!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 258 seconds)15:47
*** tmerciai <tmerciai!~tmerciai@188.217.58.137> has joined #cip15:47
*** tmerciai <tmerciai!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 255 seconds)15:52
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has joined #cip15:52
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 260 seconds)16:43
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has joined #cip16:44
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 243 seconds)17:18
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has joined #cip17:18
*** tmerciai <tmerciai!~tmerciai@188.217.58.137> has joined #cip17:34
*** tmerciai2 <tmerciai2!~tmerciai@188.217.58.137> has quit IRC (Ping timeout: 272 seconds)17:34

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