Thursday, 2024-02-29

« Wednesday, 2024-02-28 Index Friday, 2024-03-01 »
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:53
*** rajm <rajm!~robert@82.27.50.32> has joined #cip06:59
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has quit IRC (Ping timeout: 252 seconds)08:29
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has joined #cip08:30
*** frieder <frieder!~frieder@i577B93E6.versanet.de> has joined #cip08:52
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:195e:4918:1985:8ab0> has joined #cip12:59
iwamatsu__hello13:03
patersonchi13:03
pave1Hi!13:03
ulihello13:03
*** jki <jki!~jki@p5b0f192f.dip0.t-ipconnect.de> has joined #cip13:03
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has joined #cip13:03
jkihi!13:04
jkidid you start already?13:04
iwamatsu__no yet13:04
jkiI'm running low on battery, still looking for supplies13:04
jkimaybe someone else should in case I drop13:04
pave1I have good power.13:05
masamihi. my network connection was bad...13:05
pave1#startmeeting CIP IRC weekly meeting13:05
collab-meetbot`Meeting started Thu Feb 29 13:05:45 2024 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.13:05
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:05
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:05
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:05
pave1#topic AI review13:05
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:05
pave1- prepare blog entry on SLTS kernel state and challenges [Jan]13:06
jkinow I just found one :D13:06
jkino progress in the past week, sorry13:06
pave1No problem. Other AIs?13:06
pave1313:06
pave1213:06
pave1113:06
pave1#topic Kernel maintenance updates13:06
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:06
ulii'm backporting for 4.413:07
pave1I am reviewing 6.1.79 and .81.13:07
masami This week reported 130 new CVEs and 21 updated CVEs.13:07
pave1Yep, about that.13:07
jkioh, wow13:07
jkithat many13:07
pave1I don't believe Greg is acting in good faith here.13:07
pave1He copies changelogs verbatim with zero analysis. Not even making it13:07
pave1sentences or stripping irrelevant information. Sometimes he pastes "In13:07
pave1the Linux kernel, the following vulnerability has been resolved:"13:07
pave1before the changelog. Result is basically DoS on people that try to be13:07
pave1carefull and not pick everything from stable. Spamming us is colateral13:07
pave1damage. I don't think arguing with him makes sense. This should be13:08
pave1escalated.13:08
masamiwe can see lots of CVE numbers are reserved at git repo https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/reserved13:08
pave1So... yes, wow :-(.13:08
jkiso, what is the damage for us now?13:08
pave1CVE-2023-52466 is example of bad cve.13:08
jkialready13:08
pave1CVE-2023-52437 is another one.13:09
iwamatsu__I am reviewing 6.1.7913:09
pave1Well... it will make our CVE tracking useless.13:09
jkibut that was questionable from a technical perspective already, back then because too many fixes had no number13:10
jkiat least that reason is kind of "gone" now...13:10
jkibut, yeah13:10
pave1We should simply ignore any CVE from Greg. But it would be better to escalate through Neal and LF,13:11
pave1because this will harm whole community.13:11
jkican you write up some concrete points regarding that?13:12
jkiI will try, but I need input13:12
pave1Ideally, security people should do that.13:12
pave1Because they are supposed to know what CVEs look like.13:12
jkiI will try to chat with our own folks on that13:14
pave1I can try to provide input, but Masami's "New CVE entries this week" already has plenty.13:14
jkiyep13:14
pave1I don't believe "the patch applied okay, so just paste its changelog into CVE" is what security community expects.13:14
pave1Ok, anything else?13:15
pave1313:15
pave1213:15
pave1113:15
pave1#topic Kernel release status13:15
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:15
pave14.19-rt is late.13:15
pave1v4.19.307-rt133-rc1 exists, so I guess we should coordinate cip & rt release when that is out.13:16
pave1IIRC others are on track.13:17
pave1Anything else?13:17
pave1313:17
pave1213:17
pave1113:17
jkihas upstream 4.19-rt any issue?13:17
jki(BTW, CVE-2023-52437 is on rejected by now)13:18
jkimy question aims at if we as CIP should/could do something actively, or if we simply wait a bit more13:18
pave1Not that I know of. I'd need to take second look. I believe it is normal "-rc1 before release".13:19
jkiok, then let's continue13:20
pave1I believe we should tell Linux Foundation that this does not work for us. We may be in good position to influence Greg.13:20
jkiack, but we will have to explain the reasons sufficiently13:21
pave1It is likely that there's someone at cve.org who will realise this is bad, so waiting would work, but we can't be sure.13:21
pave1It is a spam. Greg is not doing any analysis.13:21
pave1So now either we have to do the analysis, or we can simply ignore it.13:22
pave1And given it has CVE numbers, our customers likely don't expect us ignoring it.13:22
jkiunderstood13:23
jkialready chatting with our CERT in parallel13:23
pave1Good :-).13:23
pave1Move on?13:24
jkiack13:24
pave1313:24
pave1213:24
pave1113:24
pave1#topic Kernel testing13:24
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:24
patersoncI don't think I've got anything to share this week13:24
arisutno updates from me13:24
jkiwhat's the deal with the kernelci bot messages now?13:25
jkithey are still there or back, aren't they?13:25
patersoncI'm checking with them already13:25
patersoncMaybe the merge request hasn't hit production yet13:25
arisutwhat message can you give a link?13:25
patersoncSome were sent to cip-dev today13:26
jkiexactly - is that intentional?13:26
patersoncThe change to stop it has been merged, but it could be that kernelci's production instance hasn't been updated to include it yet13:27
pave1So I guess it should fix itself within week or so, and we can revisit next meeting?13:28
patersoncyep13:28
pave1Good.13:28
jkithat's fine, yes13:28
pave1I took a look at squad.13:28
pave113:29
pave1irc is acting funny.13:29
pave1Squad triggers automatically at push?13:30
pave1And we need to look if all tests are finished, and that results are either pass or xfail?13:30
patersoncWhen a build or test job is completed in gitlab CI, it notifies squad13:31
arisutpatersonc any progress on sending results to squad from kernelci?13:33
patersoncI haven't had a chance to look yet, sorry13:33
jkiok - more testing topics?13:34
pave1Ok, so it is "check gitlab page for green crosses, then squad for pass or xfail"?13:34
patersoncYea13:34
patersoncsquad will indicate the results of the actual test cases13:35
pave1Ok, I guess I'll have a chance to try it soon.13:35
patersoncgitlab only shows if the lava job got to the end or not13:35
pave1Ok, move on?13:35
pave1313:35
pave1213:35
pave1113:35
pave1#topic AOB13:35
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:35
pave1Anything else?13:36
pave1513:36
pave1413:36
pave1313:36
pave1213:36
pave1113:36
pave1#endmeeting13:36
collab-meetbot`Meeting ended Thu Feb 29 13:36:31 2024 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/2024/02/cip.2024-02-29-13.05.html13:36
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/02/cip.2024-02-29-13.05.txt13:36
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/02/cip.2024-02-29-13.05.log.html13: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 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:36
pave1Thank you!13:36
iwamatsu__Thank you13:36
ulithanks13:36
patersoncOSS Japan dates were announced13:36
masamithank you13:36
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:36
patersonc(28-29 Oct)13:37
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has joined #cip13:37
pave1I guess Japan would be quite a trip from here.13:38
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Client Quit)13:38
arisutthanks you13:39
*** jki <jki!~jki@p5b0f192f.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 272 seconds)13:53
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:195e:4918:1985:8ab0> has quit IRC (Quit: Client closed)14:45
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)16:27
*** frieder <frieder!~frieder@i577B93E6.versanet.de> has quit IRC (Remote host closed the connection)20:07
*** rajm <rajm!~robert@82.27.50.32> has quit IRC (Ping timeout: 272 seconds)22:53
« Wednesday, 2024-02-28 Index Friday, 2024-03-01 »

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