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

« Wednesday, 2021-01-27 Index Friday, 2021-01-29 »
*** ironfoot has quit IRC01:16
*** ironfoot has joined #cip01:18
*** dl9pf has quit IRC02:21
*** dl9pf has joined #cip02:22
*** samwilson__ has joined #cip06:54
*** rajm has joined #cip07:33
*** fujita has joined #cip08:02
*** yoshidak[m] has joined #cip08:55
*** masashi910 has joined #cip08:56
*** pave1 has joined #cip08:57
masashi910#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Jan 28 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
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brloggerThe 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
pave1hi09:00
wenshi09:00
iwamatsuhi09:00
yoshidak[m]hi09:00
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 update about this.09:01
masashi910iwamatsu: Sure. Thanks.09:01
masashi9102. Do some experiment to lower burdens on CI - patersonc09:01
patersoncHi all, I'm afraid I'm still in another meeting so I'll have to miss this meeting today. I don't have any testing updates.09:01
masashi910patersonc: Note. 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. Keep it open.09:02
masashi910any other topics?09:02
masashi910309:02
pave1For the record... nouveau code is not really up to usual kernel standards.09:02
pave1I hope Hitachi is not really using it, but if they are, they should move away.09:02
masashi910pave1: Thanks for your comment. Let's wait for their response.09:03
masashi910209:04
masashi910109:04
masashi910#topic Kernel maintenance updates09:04
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:04
pave1Reviews of 5.10.10 and 5.10.11, and corresponding 4.19 commits.09:04
wensOne new issue this week, CVE-2020-35513 [nfsd: incorrect umask], which was fixed way back in 4.17.09:05
wensand some updates regarding three existing CVEs in this week's report09:05
iwamatsuI revewed 4.4.253 and 5.10.1109:05
wenssee the report here: https://lore.kernel.org/cip-dev/CAGb2v67U62fBOE-OxbfGkOa-SJhmiJQQCXDvJ3bd44sWhsoTig@mail.gmail.com/09:06
masashi910pave1, wens, iwamatsu: Thanks for your works!09:06
wensI'm not sure what's going on with CVE-2020-27825's fix backport09:07
wensah, looks like there's an update: https://lore.kernel.org/stable/20210125142126.70d6a33c@gandalf.local.home/09:08
masashi910wens: At least, CVE-2021-3178, which was reported last week, was backported to all stable kernels. So, it is fixed.09:09
wensIndeed.09:10
masashi910wens: So,  CVE-2020-27825 should be monitored for the time being?09:11
pave1I don't think that one warrants monitoring. It is not important for our workloads.09:11
masashi910pave1: Thanks for your comment.09:12
wensI agree. I doubt anyone does tracing on production systems.09:12
masashi910wens: Ok. Then treat it as it should be.09:12
masashi910any other topics?09:13
masashi910As Chris-san mentioned that he has no updates, let's skip "Testing"09:15
masashi910So, next is Security.09:15
masashi910#topic CIP Security09:15
*** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:15
masashi910yoshidak[m]: The floor is yours.09:15
yoshidak[m]Hi09:15
yoshidak[m]There is no major update this week, but we are considering about static code analysis now.09:16
yoshidak[m]We are confirming a few static code analysis tools, still continue to discuss internally.09:16
yoshidak[m]Thank you, that's the end from me.09:17
pave1yoshidak: You had some questions about kernel design on the mailing list. Perhaps we should talk when the meeting ends?09:17
masashi910yoshidak[m]: Thanks for your reports!09:17
masashi910pave1, iwamatsu, wens: Do you know whether upstreams are doing static code analysis by using coverity or something?09:18
pave1masashi: There are multiple efforts running static analysis on kernel, yes.09:19
masashi910pave1: Thanks. Then, are those efforts done on 4.4 and 4.19 as well?09:19
pave1masashi: Not sure, probably not. As new development is not supposed to happen there, it should not be too useful.09:20
yoshidak[m]<pave1 "yoshidak: You had some questions"> pave1: Thank you for proposing this, but I don't know what Dinesh wants to know is. so, could you discuss on line with Dinesh again?09:21
masashi910pave1: Thanks, again. I checked web sites, but I cannot find code scanning works specific to 4.4 and 4.19.09:21
pave1masashi: Coverity fixes can be identified by "Addresses-Coverity:" in the commit log.09:21
pave1yoshidak: ok.09:22
masashi910pave1: Yes, thanks!09:22
masashi910any other topics?09:22
masashi910309:23
iwamatsuI remember seeing the presentation about it before.09:23
masashi910209:23
iwamatsuhttps://elinux.org/images/d/d3/Bargmann.pdf09:23
masashi910iwamatsu: Yes, there is some on-going task, like: https://scan.coverity.com/projects/linux09:24
masashi910It is active and the latest scanning was done 3 days ago.09:24
masashi910It is tagerting the latest version. Now, 5.11.0-rc5.09:25
masashi910Anyway, we need to figure out how to satisfy IEC62443-4-1 security requirement from kernel side.09:26
iwamatsuI see.09:26
masashi910iwamatsu: Thanks for your comment!09:26
masashi910Any other topics?09:26
masashi910309:26
masashi910209:26
masashi910109:26
masashi910#topic AOB09:27
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:27
masashi910Are there any business to discuss?09:27
masashi910509:27
masashi910409:27
masashi910309:27
masashi910209:27
masashi910109:27
masashi910There seem to be no topics to be discussed, so let's close the meeting.09:27
masashi910#endmeeting09:27
brloggerMeeting ended Thu Jan 28 09:27:40 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:27
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2021/01/cip.2021-01-28-09.00.html09:27
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2021/01/cip.2021-01-28-09.00.txt09:27
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2021/01/cip.2021-01-28-09.00.log.html09:27
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:27
masashi910Thank you, and stay safe!09:27
wensThank you!09:27
pave1Thank you!09:27
yoshidak[m]Thank you!09:27
iwamatsuThank you.09:28
*** pave1 has quit IRC09:33
*** fujita has quit IRC10:37
*** masashi910 has quit IRC11:16
*** samwilson__ has quit IRC12:48
*** samwilson__ has joined #cip12:48
*** tpollard has joined #cip12:55
*** samwilson__ has quit IRC16:34
*** samwilson__ has joined #cip18:06
*** samwilson__ has quit IRC18:34
*** tpollard has quit IRC20:09
*** tpollard has joined #cip20:12
*** brlogger has joined #cip20:57
*** tpollard has quit IRC21:06
*** rajm has quit IRC23:07
« Wednesday, 2021-01-27 Index Friday, 2021-01-29 »

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