IRC logs for #cip for Thursday, 2021-02-25

« Wednesday, 2021-02-24 Index Friday, 2021-02-26 »
*** cp- has quit IRC01:58
*** cp- has joined #cip02:03
*** cp- has quit IRC02:45
*** cp- has joined #cip02:46
*** gavinlai has quit IRC06:42
*** gavinlai has joined #cip06:56
*** rajm has joined #cip07:09
*** monstr has joined #cip07:14
*** samwilson_ has joined #cip07:36
*** masashi910 has joined #cip07:42
*** pave1 has joined #cip08:59
masashi910#startmeeting CIP IRC weekly meeting09:00
brlogger`Meeting started Thu Feb 25 09:00:01 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
pave1gu09:00
pave1hi09:00
iwamatsuhi09: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
*** hungtran has joined #cip09:01
iwamatsuno update09:01
masashi910iwamatsu: Sure. Thanks.09:01
masashi9102. Do some experiment to lower burdens on CI - patersonc09:01
masashi910patersonc: are you around?09:01
patersoncNo updates09:02
masashi910patersonc: Sure. Thanks.09:02
masashi9103. Check hitachi_omap defconfigs wrt CVE-2020-27820 [drm/nouveau UAF] - Hitachi-team09:02
masashi910Still waiting for Hitachi-team's response. It's been a while, so I am asking them again.09:02
masashi910any other topics?09:02
masashi910309:02
masashi910209:02
masashi910109:02
masashi910#topic Kernel maintenance updates09:02
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:02
wensHi, sorry I'm late09:02
masashi910wens: Hi. We are now #topic Kernel maintenance updates09:03
pave1I have reviewed 5.10.17, .18 and related kernels09:03
wensFive new issues this week, though three of them seem to refer to out-of-tree driver09:03
iwamatsuI reviewed 4.4.258 and 5.10.1709:04
wensReport here: https://lore.kernel.org/cip-dev/CAGb2v65e+un0E5SwvhNShDz2MObJFZU7DsMvFXN077dSRQdEMQ@mail.gmail.com/09:04
wensI also fixed a bug in the Debian tracker import script09:04
*** tpollard has joined #cip09:05
masashi910pave1, wens, iwamatsu: Thanks for your works!09:05
wensBy the way, it seems we got no response to the GitLab forum post09:05
masashi910wens: I see. Then, the issue still exists?09:05
wensI haven't tried09:05
masashi910wens: I see.09:06
masashi910If users are suffering from the issue, we may want to consider some action, like patch revert?09:07
masashi910Let's discuss offline if needed. Shall we move on?09:09
wensSure.09:09
wensI wanted to ask09:09
masashi910Sure. Any other topics?09:09
wensHow should we mark issues that are fixed in firmware (like the Intel GPU issues)?09:09
wensand for the ones that refer to out-of-tree drivers, I will mark them as "ignore: out-of-tree vendor driver"09:10
pave1wens: ignore: firmware? :-)09:10
wenssure ... I guess? It doesn't quite help users actually track the fix. But I suppose that would be out of scope, since the project is only supposed to track the kernel09:11
masashi910wens: in you email, "Last, CVE-2020-12362, CVE-2020-12363, and CVE-2020-12364 are now known09:12
masashi910to be fixed by a firmware update. However to use the new firmware, a kernel patch [2] is required."09:12
masashi910In order to track "kernel patch [2] ", some info should be logged?09:13
wensYes. I can add that, but that is only the prerequisite to the actual fix (the firmware)09:14
masashi910wens: Right... So, as Pavel-san mentions, "ignore: firmware" might be enough.09:17
masashi910wens: What do you think?09:19
masashi910Shall we move on?09:20
masashi910309:20
masashi910209:20
masashi910109:20
masashi910#topic Kernel testing09:20
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:20
masashi910patersonc: The floor is yours.09:20
patersoncI don't think I have anything to report today09:21
patersoncI'll try and think of something for the extended TSC :P09:21
masashi910patersonc: Thanks.09:21
masashi910any other topics?09:21
masashi910309:21
masashi910209:22
masashi910109:22
masashi910Today, Yoshida-san is not here. So, let's skip Security.09:22
iwamatsusorry, I have a question about intel's CVE.09:22
masashi910please.09:22
iwamatsuCommit c784e5249e is not in other LTS trees. Do we need to backport this?09:22
wensI think so, but the commit isn't exactly small09:23
iwamatsuI see, thank.09:24
pave1Is any of our boards using i915?09:24
wensUnlikely? x86 servers normally would have some BMC that also includes VGA controller09:25
iwamatsuyes.09:26
iwamatsufor example, siemens's kernel config have this config.09:26
iwamatsuAnd I had a question about this CVE from within my company, so I was thinking about how to fix with it.09:27
pave1I guess we can backport. It is not small but it is not _too_ scary.09:27
masashi910So, shall I make this backporting issue as an AI?09:28
pave1Umm. Let me take a look at that, no need for AI.09:28
masashi910pave1: OK.09:28
masashi910any other topics?09:29
pave1Yes, actually.09:29
iwamatsupavel: thanks,09:29
masashi910309:29
masashi910209:29
masashi910109:29
iwamatsuI will check it too.09:29
masashi910#topic CIP Security09:29
*** brlogger` changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:29
masashi910Let's skip security.09:29
masashi910#topic AOB09:29
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:29
pave1o/09:30
masashi910Please.09:30
pave1Michal Simek, working with/for Xilinx, contacted me and asked about ZynqMP support for CIP.09:30
pave1I believe that's the candidate board we have listed, and according to him neccessary support should be in 5.10.09:31
pave1So... if there's still interest in that board, it might be useful to talk to him, and he can probably offer help.09:32
masashi910pave1: If Xilinx can support ZyncMP in CIP, that would be great.09:32
iwamatsunice09:32
masashi910Regarding the interest in ZynqMP, shall I ask CIP community about that?09:33
masashi910Or Long TSC meeting might be a good opportunity to discuss.09:33
pave1I believe no steps are neccessary at the moment.09:33
pave1Just don't be surprised if he contacts us.09:33
masashi910pave1: Sure. Thanks for this headsup!09:34
masashi910Any other topics?09:34
pave1Alternatively I can send an email mutually introducing you or something like that.09:34
masashi910pave1: Yes, that woud be great!09:35
pave1masashi910: ok!09:35
masashi910pave1: Thanks!09:35
masashi910Any other topics?09:35
masashi910309:35
masashi910209:35
masashi910109:35
masashi910So, Let's close today's meeting.09:36
masashi910#endmeeting09:36
brlogger`Meeting ended Thu Feb 25 09:36:13 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:36
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2021/02/cip.2021-02-25-09.00.html09:36
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/02/cip.2021-02-25-09.00.txt09:36
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2021/02/cip.2021-02-25-09.00.log.html09:36
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:36
masashi910Thank you, and stay safe!09:36
wensThanks!09:36
pave1Thank you!09:36
iwamatsuThank you!09:36
*** hungtran has quit IRC09:56
*** sudip_ has joined #cip10:00
*** sudip has quit IRC10:03
*** sudip_ is now known as sudip10:26
pave111:03
*** brlogger has joined #cip23:34
« Wednesday, 2021-02-24 Index Friday, 2021-02-26 »

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