IRC logs for #cip for Thursday, 2020-12-10

*** ltu8 has joined #cip03:02
*** rynofinn has quit IRC06:11
*** rynofinn has joined #cip06:11
*** eduardas has joined #cip06:50
*** eduardas has quit IRC07:06
*** rajm has joined #cip07:08
*** masashi910 has joined #cip08:16
*** samwilson_ has joined #cip08:19
*** fujita has joined #cip08:33
*** pavel1 has joined #cip08:59
masashi910#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Dec 10 09:00:01 2020 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at
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
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
masashi910Based on the offline discussion after the last IRC meeting, I created this AI.09:01
masashi910patersonc: are you around?09:02
masashi910OK, let's come back when he joins.09:02
masashi910any other topics?09:02
masashi910#topic Kernel maintenance updates09:03
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:03
iwamatsuI reviewed 4.4.247 and 4.4.248-rc09:03
pavel1I have reviewed 4.19.162 and started reviews on
wensFive new issues this week. I believe we would want to backport the fix for CVE-2020-2858809:04
wensIt was not tagged for stable.09:04
pavel1Let me investigate....09:04
wensalso, hitachi enables DRM_NOUVEAU in their omap defconfig, which is perplexing.09:05
*** tpollard has joined #cip09:06
masashi910wens: Then, shall I ask them about it?09:06
wensmasashi910: Yes, please.09:06
masashi910wens: Sure.09:06
masashi910wens: Also, for the record, let me just log the url of your cip-kernel-sec report sent to cip-dev.09:06
masashi910wens: I have a couple of questions about cip-kernel-sec. Could I ask such questions after this meeting?09:07
masashi910wens: Thanks!09:07
masashi910pavel1, iwamatsu, wens: Thanks for your works!09:09
masashi910pavel1: While you are investigating the cve, shall we move on?09:09
pavel1masashi910: Yes, move on. It makes sense to continue over email.09:09
masashi910pavel1: Thanks!09:10
masashi910any other topics?09:10
masashi910#topic Kernel testing09:10
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:10
masashi910patersonc: are you here?09:10
masashi910So, let's skip this part this week.09:11
masashi910#topic CIP Security09:11
*** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:11
masashi910yoshidak[m]: the floor is yours.09:11
yoshidak[m]There is no major update from last week.09:11
yoshidak[m]We hold the meeting w/ Exida tomorrow.09:12
yoshidak[m]That's the end from me today.09:12
masashi910yoshidak[m]: Thanks for your works!09:12
masashi910any other topics?09:12
masashi910#topic AOB09:12
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:12
masashi910Regarding the development start based on 5.10, it was announced with the following blog.09:13
masashi910That's it from me.09:14
masashi910pavel1: Please.09:14
pavel1Do we start preparations? 5.10.1 is likely to be huge.09:14
pavel1As in -- lots of stuff to review.09:14
masashi910pavel1: Yes, but after 5.10 is released.09:15
wensIIRC -rt is not merged into mainline yet?09:15
pavel1Alternatively, we could wait for say 5.10.5 before forking cip branch.09:15
iwamatsuyes, it is  not merge yet.09:15
pavel1Major effect would be that we would not have reviewed 5.10 to 5.10.5 changes :-).09:15
pavel1No, -rt is not yet merged into mainline in an usable way.09:16
masashi910pavel1: I think we can choose the best timing.09:17
pavel1Ok :-).09:17
masashi910pavel1, iwamatsu, wens: Let's discuss about it in the future. :)09:18
masashi910pavel1: Do you have any insights on CVE-2020-2858809:19
pavel1It looks to me like vulnerable code is not in 4.4 or 4.19, but let me confirm.09:20
sudipCVE-2020-28588 was introduced by 631b7abacd02 in v5.1 and that has not been backported so I dont  think any CIP kernel is affected09:20
pavel1If it is, it is easy to fix/backport.09:20
masashi910sudip: Thanks for this info!09:21
wensIf it's a straightforward backport, I suppose we could still ask greg to include it for v5.4, as a way of showing the helpful side of CIP09:22
pavel1wens: I'd let someone else do that. I'm pretty sure we are not the only ones watching CVEs.09:23
iwamatsuOh, this commit's comit date is CommitDate: Fri Apr 5 09:26:43 2019 -0400. but Auther date is Mon Nov 7 16:26:37 2016 -050009:23
pavel1wens: Or maybe we can/should do that if it is not fixed by january :-).09:23
wenspavel1: fine with me. I suppose we might see bwh or some other distro guys asking for it. :)09:24
masashi910So, shall we keep our eyes on this CVE, and decide what to do in the future?09:24
masashi910I mean, make this as an AI.09:25
wensSure. Let's keep it until, say, mid-January?09:25
masashi910Great! Thanks!09:26
masashi910Any other topics?09:26
masashi910If there are no topics, then, let's close the meeting.09:26
brloggerMeeting ended Thu Dec 10 09:26:34 2020 UTC.  Information about MeetBot at . (v 0.1.4)09:26
brloggerMinutes (text):
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at"09:26
masashi910Thank you, and stay safe!09:26
wensThank you!09:26
iwamatsuThank you.09:26
pavel1Stay safe!09:26
sudipthanks masashi91009:26
ebardiecheers all09:26
masashi910wens: Today, I executed scripts listed here:09:27
masashi910As a result of scripts/, I can search issues. But I cannot find some of CVEs you reported today.09:27
masashi910CVE-2020-27820, CVE-2020-27830, and CVE-2020-28588 are in the list, but CVE-2020-27786 and CVE-2020-29534 are not.09:27
masashi910I wonder whether your sources to analyze the latest CVE patches are different from the above scripts. Or somehow, my environment could be corrupted?09:27
wensI haven't used the webview to be honest.09:28
masashi910wens: then, are you using command lines?09:29
wensI do the imports and edit the files by hand mostly.09:29
sudipmasashi910: you can use script09:30
wensmaybe it only shows issues that aren't fixed? just like report_affected.py09:30
wensCVE-2020-27786 is fixed for all kernels, and CVE-2020-29534 only affects v5.5+09:30
masashi910sudip, wens: Thanks for this info! I will try!!!09:30
wenswith, you can specify which branch ( or mainline ) you want to track09:31
masashi910wens, sudip: Thanks for staying after the meeting. This info is really helpful!09:32
wensRegarding cip-kernel-sec, there is an open issue stating that we do not track issues that have been retired by distros09:32
wensNot sure if adding them is helpful. If an issue is retired, surely it is fixed by then?09:32
masashi910wens: Hmmm. I cannot judge... Shall we ask other members opinions?09:33
masashi910maybe next week?09:34
wenssure. please add an AI for it? #
masashi910wens: sure, I will.09:35
masashi910Then, see you next week!09:36
wensSee you!09:37
*** fujita has quit IRC10:33
*** pavel1 has quit IRC10:42
*** eduardas has joined #cip12:38
*** masashi910 has quit IRC13:17
*** eduardas has quit IRC13:29
*** eduardas has joined #cip13:44
*** samwilson_ has quit IRC17:08
*** eduardas has quit IRC17:08
*** samwilson_ has joined #cip17:34
*** tpollard has quit IRC17:36
*** monstr has quit IRC17:43
*** toscalix has joined #cip17:59
*** toscalix has quit IRC18:00
*** toscalix has joined #cip18:01
*** toscalix has quit IRC18:10
*** toscalix has joined #cip18:13
*** samwilson_ has quit IRC18:18
*** toscalix has quit IRC18:19
*** toscalix has joined #cip18:19
*** toscalix has quit IRC18:34
*** toscalix has joined #cip18:34
*** toscalix has quit IRC18:43
*** toscalix has joined #cip18:48
*** toscalix has quit IRC18:59
*** toscalix has joined #cip20:45
*** toscalix has quit IRC22:50
*** rajm has quit IRC23:02

Generated by 2.15.3 by Marius Gedminas - find it at!