IRC logs for #cip for Thursday, 2021-04-08

« Wednesday, 2021-04-07 Index Friday, 2021-04-09 »
*** rajm has joined #cip03:26
*** monstr has joined #cip06:08
*** samwilson has joined #cip07:00
*** samwilson has quit IRC07:28
*** samwilson has joined #cip07:34
*** tpollard has joined #cip08:26
*** hiraku_toyooka has joined #cip08:39
*** masashi910 has joined #cip08:46
masashi910#startmeeting CIP IRC weekly meeting09:00
brlogger`Meeting started Thu Apr  8 09:00:00 2021 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
brlogger`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brlogger`The meeting name has been set to 'cip_irc_weekly_meeting'09:00
*** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910#topic rollcall09:00
*** brlogger` changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910please say hi if you're around09:00
wenshi09:00
iwamatsuhi09:00
patersonchi09:00
masashi910Let's get started.09:01
masashi910#topic AI review09:01
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:01
masashi9101. Combine root filesystem with kselftest binary - iwamatsu09:01
iwamatsuI recieved a mail from CTJ, but I do not read it. So, no update yet.09:01
masashi910iwamatsu: Noted. Thanks.09:02
masashi9102. Do some experiment to lower burdens on CI - patersonc09:02
patersoncNo updates09:02
masashi910patersonc: Noted. Thanks.09:02
masashi9103. Ask board owners(siemens_i386-rt/plathome_obsvx1) whether X.25 and floppy can be disabled - masashi91009:02
masashi910Iwamatsu-san disabled them. So, I close this.09:03
masashi910https://lore.kernel.org/cip-dev/OSBPR01MB2983E7B807513366EE13257392749@OSBPR01MB2983.jpnprd01.prod.outlook.com/T/#ma708cec130db6ea926a7f45f8fc30756155a865309:03
masashi910https://lore.kernel.org/cip-dev/OSBPR01MB2983E7B807513366EE13257392749@OSBPR01MB2983.jpnprd01.prod.outlook.com/T/#m7b03fd97b8326de92c48e1e1da73204966a82e2e09:03
masashi9104. Monitor the status of CVE-2021-3444 and CVE-2021-20292 (3/25) - Kernel Team09:03
masashi9105. Monitor the status of CVE-2021-29650 (4/1) - Kernel Team09:03
*** pave1 has joined #cip09:03
masashi910According to Wens-san's report:09:03
masashi910====09:03
masashi910No updates on CVE-2021-3444, CVE-2021-20292 or CVE-2021-29650 from previous weeks.09:04
masashi910====09:04
masashi910Any comments?09:04
pave1I have submitted stable patch for CVE-2021-29650.09:04
masashi910pave1: Great! Thanks!!!09:04
pave1I did not receive any feedback, but it will stay in the "to backport" branch, so you can stop tracking it.09:05
masashi910pave1: Sure, then I close "5. Monitor the status of CVE-2021-29650 (4/1) - Kernel Team"09:06
pave1Thank you. And sorry for being late. Other work was reviews of 5.10.28 and submitting of CVE-2021-29650 fix.09:06
masashi910So, I will close 5 and keep 4 for a while.09:07
masashi910pave1: Thanks for your works.09:07
masashi910So, let's move on.09:07
masashi910#topic Kernel maintenance updates09:07
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:07
wensThis week's report: https://lore.kernel.org/cip-dev/CAGb2v66M1mjZjBfHAwv1yECqCDHALzk4_fVD-bdB0V-4R=DPLg@mail.gmail.com/09:08
wensEight new issues this week, all fixed, but one's auto-backport (by Sasha) failed.09:08
wensFailed one is CVE-2020-36310, which is AMD SVM specific, which I think we can ignore?09:09
wensIt's not security issue anyway.09:09
pave1wens: Yes, I believe we can ignore that.09:09
wensOK. I will mark it as such.09:09
masashi910wens: Thanks for your works. Recently many new issues every week. :(09:10
wenspave1: about the fix for CVE-2021-29650, where did you submit it to?09:10
pave1masashi910: It seems barrier for getting CVE number is getting lower and lower.09:10
masashi910pave1: I see.09:10
wensmasashi910: It is unfortunate, but many of the fixes weren't even tagged for stable. And also, *not actual security issues*09:11
masashi910wens: Hmmmm. Thanks.09:11
pave1wens: I hope I sent it to the stable@kernel.org mailing list.09:11
masashi910iwamatsu: do you have updates?09:12
wenspave1: I'm not seeing it.09:12
iwamatsuI reviewed 4.4.265 and 5.10.28, and I have sent a patch for ISAR for QEMU testing on LAVA.09:13
masashi910iwamatsu: Thanks for your works.09:13
pave1wens: Thanks, I'll re-check.09:14
pave1wens: Are you subscribed to stable@?09:14
wensI am, but occasionally gmail drops messages due to DKIM/DMARC :(09:15
wensNo need to dwell on it, I'll check lore later.09:16
masashi910Ok, so shall we move on?09:16
masashi910309:16
pave1wens: It may well be error on my part, as I can't see it in sent box.09:16
masashi910209:16
masashi910109:16
masashi910#topic Kernel testing09:16
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:16
masashi910patersonc: The floor is yours.09:16
patersoncHello09:16
patersoncWe hit another snag in the LAVA master this week, which mean that jobs stopped processing.09:17
patersoncSorry09:17
patersoncI may have fixed it, or maybe it'll happen again - I'm not sure yet.09:17
patersoncAnd the Denx lab isn't online atm09:17
patersoncPerhaps the owner is on Easter holidays09:18
patersoncI guess that's about it09:19
patersoncSorry for all the downtime09:19
masashi910patersonc: Thanks for your works.09:19
masashi910any other topics?09:20
masashi910309:20
masashi910209:20
masashi910109:20
masashi910#topic CIP Security09:20
*** brlogger` changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:20
masashi910yoshidak[m]: Are you around?09:20
masashi910Yoshida-san does not seem to be here, so let's skip.09:21
masashi910#topic AOB09:21
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:21
masashi910Last week, I reported that Xilinx zcu102 was approved as a reference platform.09:22
masashi910So, I think the following table should be updated accordingly.09:22
masashi910https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware09:22
masashi910I will raise this issue at the next TSC and get approval to change.09:23
masashi910Any comments?09:23
pave1I think we can just update the table :-)09:23
iwamatsuDo we need approval?09:24
iwamatsu+109:24
masashi910pave1, iwamatsu: Thanks for your comments. Well, you are right. Then let's update it!09:25
iwamatsuWhen I updated it before, I dit not ask checking it with TSC.09:25
masashi910iwamatsu: OK. Then, let's go ahead. This is my AI.09:26
masashi910Are there any business to discuss?09:26
patersoncmasashi910: Perhaps also add a column for 5.10?09:26
masashi910patersonc: That's right. We need to classify "supported" and "just testing" based on the discussion last week.09:27
masashi910patersonc: So, let me consult with you how to change after this IRC. I will send email to you.09:28
pave1masashi910: I guess we can remove "just testing" boards from this.09:28
pave1masashi910: (Or at least that should be clearly marked).09:29
masashi910pave1: so "just testing" boards can be known only through LAVA results. Is it ok?09:29
patersoncWe could use a 'T' instead of 'Y'?09:30
masashi910patersonc: Ah, nice!09:30
pave1Nice :-).09:30
masashi910Ok, let's do that. Thanks for all your comments and ideas!09:30
patersoncThere is also a table here: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/centalisedtesting/cioverview09:31
masashi910Are there any business to discuss?09:31
patersoncBut it's probably out of date09:31
patersoncmasashi910: Can you add an action for me to update https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/centalisedtesting/cioverview with 5.10 info?09:31
masashi910patersonc: Sure, thanks for taking this action!09:32
masashi910any other topics?09:32
masashi910509:32
masashi910409:33
masashi910309:33
masashi910209:33
masashi910109:33
masashi910So, let's close today's meeting.09:33
masashi910#endmeeting09:33
brlogger`Meeting ended Thu Apr  8 09:33:22 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:33
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2021/04/cip.2021-04-08-09.00.html09:33
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/04/cip.2021-04-08-09.00.txt09:33
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2021/04/cip.2021-04-08-09.00.log.html09:33
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:33
masashi910Thank you, and stay safe!09:33
iwamatsuThank you09:33
pave1Thank you!09:33
wensThank you!09:33
patersoncCheers all09:34
wensI just realized CVE-2020-36310 doesn't affect any of our kernels.09:34
masashi910wens: I see. So we need not monitor this.09:35
wensCorrect.09:39
*** monstr has quit IRC10:10
*** pave1 has quit IRC10:11
*** monstr has joined #cip10:12
*** monstr has quit IRC10:25
*** monstr has joined #cip10:31
*** masashi910 has quit IRC10:58
sashalwens: I don't auto-backport KVM stuff by request of the maintainer. If something is missing please bug him directly :)11:23
*** hiraku_toyooka has quit IRC11:29
wensseems I confused the fix for this CVE with another one :(12:07
wenssashal: sorry about the noise12:07
*** samwilson has quit IRC12:50
*** samwilson has joined #cip12:50
*** samwilson has quit IRC14:05
*** samwilson has joined #cip14:16
*** samwilson has quit IRC16:45
*** tpollard has quit IRC16:57
*** monstr has quit IRC17:04
*** samwilson has joined #cip18:01
*** samwilson has quit IRC18:07
*** samwilson has joined #cip18:31
*** toscalix has joined #cip19:14
*** samwilson has quit IRC19:17
*** samwilson has joined #cip19:24
*** toscalix has quit IRC19:38
*** toscalix has joined #cip20:01
*** brlogger has joined #cip20:23
*** brlogger` has quit IRC20:26
*** samwilson has quit IRC20:51
*** rajm has quit IRC22:00
*** toscalix has quit IRC22:41
« Wednesday, 2021-04-07 Index Friday, 2021-04-09 »

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!