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

*** helmut has quit IRC05:21
*** rajm has joined #cip06:04
*** samwilson_ has joined #cip07:06
*** masashi910 has joined #cip07:57
*** monstr has joined #cip07:59
*** tpollard has joined #cip08:16
*** pave1 has joined #cip08:56
masashi910#startmeeting CIP IRC weekly meeting09:00
brlogger`Meeting started Thu Apr  1 09:00:01 2021 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at
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
wens   hi09: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
iwamatsuno update09:01
masashi910iwamatsu: Noted, thanks!09:01
masashi9102. Do some experiment to lower burdens on CI - patersonc09:01
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
masashi910I got the confirmations from Minda-san and Jan-san respectively, so we can disable X.25 and floppy.09:02
masashi910iwamatsu: Could you disable them?09:02
iwamatsuSure, I will do it after this meeting.09:02
masashi910iwamatsu: Thanks! Then, I will close this AI.09:03
masashi9104. Monitor the status of CVE-2021-3444 and CVE-2021-20292 - Kernel Team09:03
masashi910According to Wens-san's report:09:03
masashi910CVE-2021-3444 - Debian added the following notes:09:03
masashi910This last pre-requisite commit though would depend on 092ed0968bb6 ("bpf: verifier support JMP32")09:03
masashi910which does not seem to make it possible to backport the fixes in 4.19.y easily.09:03
masashi910CVE-2021-20292 - Ubuntu tagged the commit introducing the issue as 8e7e70522d7609:04
masashi910("drm/ttm: isolate dma data from ttm_tt V4") from v3.3-rc1.09:04
masashi910So it looks like the fix needs to be backport to v4.4 as well.09:04
masashi910So, shall we continue to monitor them?09:04
wensI think so.09:04
masashi910wens: Sure. So I will keep this AI open.09:05
masashi910any other topics?09:05
masashi910#topic Kernel maintenance updates09:06
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:06
pave1I have reviewed patches queued for
wensThis week' s report:
wens9 new issues this week, all fixed. Two need backporting, but one can be ignored for CIP. Remaining one needing backport is CVE-2021-29650.09:07
iwamatsuI reviewed 4.4.254 and v5.10.27.09:07
masashi910pave1, wens, iwamatsu: Thanks for your works!09:08
masashi910Shall I make an AI to monitor CVE-2021-29650 status, or does anyone pick it up to work on?09:08
masashi910So, I will make an AI for this CVE for now.09:10
masashi910If it is not needed, please let me know.09:10
masashi910any other topics?09:10
masashi910#topic Kernel testing09:11
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:11
masashi910patersonc: The floor is yours.09:11
patersoncToday the LAVA master will be offline for an hour or so due to maintenance09:11
patersoncIn about 5 hours09:11
patersoncThat said, some of the labs are offline this morning - they all go disconnected last night09:12
patersoncSorry for the downtime09:12
patersoncThat's it from me09:13
masashi910patersonc: Thanks for your works!09:13
masashi910Any queries or comments?09:13
masashi910#topic CIP Security09:13
*** brlogger` changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:13
masashi910yoshidak[m]: Are you around?09:13
masashi910Because Yoshida-san does not seem to be here, let's skip.09:15
masashi910#topic AOB09:15
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:15
masashi910I have two topics.09:15
masashi9101. Announcement of new reference platform - Xilinx zcu10209:15
masashi910At the latest TSC, Xilinx zcu102 was approved to add to the reference platform list.09:16
masashi910Now it is going to be supported for 5.10/5.10-rt.09:16
masashi9102. Target boards for 5.10 and 5.10-rt09:17
masashi910The 5.10 target boards were agreed as follows:09:17
masashi910BBB, Cyclone V, QEMU(X86_64, Armv7, Armv8), RZ/G1M, RZ/G2M, SIMATIC IPC227E, OpenBlocks IoT VX2, Xilinx ZCU10209:17
masashi910Regading 5.10-rt, SIMATIC IPC227E and Xilinx MPSoC ZCU102 are requested by CIP-members.09:17
masashi910The kernel Team would like to add QEMU for testing.09:17
masashi910Chris-san suggests to add RZ/G1M and RZ/G2M to the 5.10-rt targets.09:18
masashi910patersonc: So, I will report that  RZ/G1M and RZ/G2M are added to 5.10-rt targets at the next TSC. Is it OK?09:18
patersoncThat's okay with me09:18
masashi910patersonc: Sure.09:18
masashi910So, any comments on the above?09:19
pave1Cyclone V board is somehow imporant for me, as I have physical access to that one.09:19
masashi910pave1: for 5.10-rt?09:20
pave1But I'd propose simply adding all available boards for 5.10-rt testing (even if we don't support them, and even if we don't have realtime config for them).09:20
pave1That would make it more likely that mistakes are caught, and should not really add much overhead.09:20
pave1Yes, for 5.10-rt.09:20
patersoncThere are some non-CIP reference platforms in the Renesas  lab, but only 1 of each. The issue comes in that pipelines will start failing if these boards go offline09:21
iwamatsu+1 > all available boards.09:21
pave1patersonc: So that's quite easy to diagnose -- if the results say "no available boards", it is not a "real" failure and can be ignored.09:22
patersoncOkay :)09:22
pave1patersonc: Yes, it would be nice to have different symbol than fail eventually, but...09:22
patersoncYes, GitLab doesn't support it though. If when CIP get a KernelCI instance things like this will be much better09:23
patersoncI just haven't had time, sorry09:23
masashi910pave1, patersonc, iwamatsu: I would like to confirm that this discussion is for testing, not official targets for 5.10-rt.09:23
pave1No problem :-).09:23
pave1masashi910: Yes, testing only.09:24
masashi910pave1: Thanks for your confirmation!09:24
masashi910So, the conclusion is to add all boards for 5.10-rt. Is it OK?09:25
pave1I believe so.09:25
iwamatsuIt may be good to separate official and non-official.09:25
wensas far as CVEs are concerned, I only look at cip-kernel-config09:26
masashi910iwamatsu: That's correct. Officials are SIMATIC IPC227E and Xilinx MPSoC ZCU102. Plus, RZ/G1M and RZ/G2M. Non-officials are the rest.09:27
pave1wens: Configs for -rt should be similar enough that it should not cause problems.09:27
wensok. If separate defconfigs get added, maybe we tag them as "test-only" then09:27
masashi910Thanks for these discussions! Any other topics?09:28
masashi910So, let's close today's meeting.09:29
brlogger`Meeting ended Thu Apr  1 09:29:38 2021 UTC.  Information about MeetBot at . (v 0.1.4)09:29
brlogger`Minutes (text):
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at"09:29
masashi910Thank you, and stay safe!09:29
pave1Thank you!09:29
wensThank you!09:29
iwamatsuThank you!09:29
*** pave1 has quit IRC11:10
*** masashi910 has quit IRC12:00
*** samwilson_ has quit IRC16:20
*** tpollard has quit IRC17:00
*** monstr has quit IRC17:21
*** helmut has joined #cip19:02
*** rajm has quit IRC22:03

Generated by 2.15.3 by Marius Gedminas - find it at!