| *** rajm has joined #cip | 02:38 | |
| *** rajm has quit IRC | 03:46 | |
| *** rajm has joined #cip | 07:29 | |
| *** therisen has joined #cip | 07:44 | |
| *** masashi910 has joined #cip | 07:46 | |
| masashi910 | quit | 07:48 |
|---|---|---|
| *** masashi910 has quit IRC | 07:48 | |
| *** masashi910 has joined #cip | 07:51 | |
| *** pave1 has joined #cip | 08:54 | |
| *** suzuki90 has joined #cip | 08:58 | |
| *** kazu has joined #cip | 08:59 | |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
| brlogger` | Meeting started Thu Dec 19 09:00:02 2019 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 rollcall | 09:00 |
| *** brlogger` changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| pave1 | hi | 09:00 |
| masashi910 | please say hi if you're around | 09:00 |
| kazu | hi | 09:00 |
| iwamatsu | hi | 09:00 |
| suzuki90 | hi | 09:00 |
| wens | hi | 09:00 |
| patersonc | hi | 09:00 |
| masashi910 | #topic AI review | 09:00 |
| *** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | 1. Test LTS (pre)releases directly - patersonc | 09:00 |
| patersonc | Hello | 09:01 |
| masashi910 | Chris-san, hi! | 09:01 |
| masashi910 | Chris-san, do you have updates? | 09:01 |
| patersonc | I've now improved the way the commits we test are shown in GitLab | 09:01 |
| patersonc | e.g. https://gitlab.com/cip-playground/linux-stable-rc-ci/pipelines | 09:01 |
| patersonc | It's now clear which commit is tested | 09:02 |
| patersonc | Last 2 things remaining are to merge the PRs, and move everything to the cip-testing project | 09:02 |
| masashi910 | patersonc: thanks! OK, shall we keep this AI open? | 09:02 |
| patersonc | Yes please | 09:03 |
| patersonc | Getting there... | 09:03 |
| masashi910 | patersonc: sure! | 09:03 |
| masashi910 | 2. Create a way/process to run LTP only for release tests - patersonc | 09:03 |
| masashi910 | patersonc: do you have updates on this? | 09:03 |
| patersonc | Process has been proposed, MRs are submitted | 09:03 |
| patersonc | I just need to document the process on the Wiki and merge | 09:04 |
| patersonc | (process was also agreed by maintainers) | 09:04 |
| patersonc | Feel free to keep this open | 09:04 |
| masashi910 | patersonc: thanks for your progress! then, shall we keep this AI open as well? | 09:04 |
| patersonc | Yep | 09:05 |
| masashi910 | patersonc: OK! | 09:05 |
| masashi910 | 3. Combine rootfilesystem with kselftest binary - Iwamatsu-san | 09:05 |
| masashi910 | Iwamatsu-san, do you have updates on this? | 09:05 |
| iwamatsu | masashi910: No update. | 09:05 |
| iwamatsu | please keep this A.I. | 09:05 |
| masashi910 | iwamatsu: thanks for your report. Sure, I will keep this ai open. | 09:06 |
| masashi910 | 4. Document a process on how to add tests to the CIP test setup - patersonc | 09:06 |
| patersonc | No progress | 09:06 |
| masashi910 | patersonc: thanks for your report! | 09:06 |
| masashi910 | 5. Arrangement of F2F Kernel Meeting in Nurnberg - masashi910 | 09:07 |
| masashi910 | I set up a doodle poll last week. | 09:07 |
| masashi910 | So far, only Chris-san responded to this. I would like to report the result to TSC tomorrow. So, please fill your availability to the poll. | 09:07 |
| masashi910 | https://doodle.com/poll/73if9scwqrh5ge38 | 09:07 |
| masashi910 | then, let me move to next. | 09:07 |
| patersonc | 0/ | 09:07 |
| masashi910 | #topic kernel maintenance updates | 09:07 |
| *** brlogger` changes topic to "kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:08 | |
| patersonc | There is a chance I'll only be attending EW remotely, depending on budget. | 09:08 |
| masashi910 | patersonc: I see. If the meeting is set up, I will also set up the zoom channel. | 09:09 |
| patersonc | masashi910: Thanks | 09:09 |
| masashi910 | pave1, iwamatsu, wens, bwh: do you have any updates? | 09:10 |
| wens | classify-failed-patches will now (pending merge request) include stable patch review series from Greg. there are still some patches that are left out due to random tags. I'll add these as I find them. | 09:10 |
| wens | I assume people likely don't want Sasha's AUTOSEL series to be included though | 09:10 |
| pave1 | I did reviews on 4.19.89 and 1.19.90, and am now in progress of merging of "Add RZ/G2N SYSC/RST/Clock/PFC support" series. | 09:10 |
| iwamatsu | I review LTS-rc on stable ML, I send some comment. | 09:11 |
| wens | cip-kernel-sec gained (pending MR) four new CVEs, one is fixed, three (as of commit time) are not | 09:11 |
| pave1 | wens: Yes, excluding autosel stuff should save a lot of work. | 09:12 |
| masashi910 | wens, pave1, iwamatsu: thanks for your works! | 09:12 |
| wens | there's also a new make target that will show mails that are probably patches but aren't included | 09:13 |
| pave1 | wens: Could we talk after the meeting? | 09:13 |
| wens | pave1: sure | 09:13 |
| patersonc | o/ | 09:13 |
| masashi910 | wens, pave1: thanks! | 09:13 |
| masashi910 | any other topics? | 09:13 |
| masashi910 | 3 | 09:13 |
| masashi910 | 2 | 09:13 |
| masashi910 | 1 | 09:13 |
| patersonc | yes | 09:14 |
| masashi910 | #topic Kernel testing | 09:14 |
| *** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:14 | |
| patersonc | Just to let you all know, Biju and Fabrizio will be leaving Renesas tomorrow, so you'll see a dramatic drop in patches coming from them :) | 09:14 |
| patersonc | If there is any feedback you need on patches etc. before then, it may be worth asking today | 09:14 |
| patersonc | Sorry for the short notice | 09:14 |
| pave1 | patersonc: They will be missed... | 09:14 |
| patersonc | pave1: Very much so! | 09:14 |
| masashi910 | patersonc: I see. Thanks for sharing this info. And please send our best regards to them for their contributions! | 09:15 |
| patersonc | I will | 09:15 |
| masashi910 | patersonc: the floor is yours | 09:15 |
| patersonc | Back to CIP testing... | 09:15 |
| patersonc | As reported earlier I've been improving the LTS stable-rc build/testing process | 09:16 |
| patersonc | Pretty much done now, just need to merge and move the project to cip=testing | 09:16 |
| patersonc | I've also been working on setting up LTP testing for '-rc' branches | 09:16 |
| patersonc | The Mentor lab/boards are back online after some lab maintenance last weekend | 09:16 |
| patersonc | I'll merge CI support for them soon, but there is a worry that the internet connection is randomly very slow | 09:17 |
| patersonc | Which can cause jobs to fail, often | 09:17 |
| patersonc | I think that's about it from me. Any queries? | 09:17 |
| masashi910 | patersonc: thanks for your works! | 09:18 |
| patersonc | No worries | 09:18 |
| masashi910 | does anybody have any questions, or any other topics? | 09:19 |
| masashi910 | 3 | 09:19 |
| masashi910 | 2 | 09:19 |
| masashi910 | 1 | 09:19 |
| masashi910 | #topic CIP Core | 09:19 |
| *** brlogger` changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:19 | |
| kazu | hello | 09:19 |
| masashi910 | kazu: the floor is yours | 09:19 |
| kazu | 1. PDP: Package review on-going, please start discussions about specific packages if you need | 09:19 |
| kazu | I'm a bit worrying no discussion about the packages :) | 09:20 |
| kazu | 2. Just started https://gitlab.com/cip-project/cip-core/deby/issues/4; use the existing configs for kernel builds | 09:20 |
| kazu | I would like to ask one question about this later | 09:20 |
| kazu | 3. In-progress https://gitlab.com/cip-project/cip-core/deby/issues/7; still checking and reusing the old script to submit tests to LAVA: https://gitlab.com/cip-project/cip-core/deby/blob/master/poky/scripts/lava-submit-job.sh | 09:20 |
| kazu | I will focus on this in this month | 09:21 |
| kazu | That's all from me, any question? | 09:21 |
| masashi910 | kazu: regarding 2, "I would like to ask one question about this later", do you mean after the call? | 09:21 |
| kazu | sorry, in AOB is better | 09:21 |
| patersonc | kazu: Do CIP plan to support all of the dependency patches long-term? Or just the requested packages? | 09:21 |
| masashi910 | kazu: I see. | 09:21 |
| kazu | patersonc sorry, what does " the dependency patches" mean here? | 09:22 |
| patersonc | I think the security group requested 19(?) packages? But they require another x packages on top | 09:23 |
| kazu | patersonc Yes, correct | 09:23 |
| patersonc | Will we support everything long-term? Or just the 19 | 09:23 |
| kazu | patersonc Dependency packages will be discussed in the next step, they are now requesting the 21 packages first | 09:24 |
| patersonc | Ah okay | 09:24 |
| patersonc | Thanks | 09:24 |
| kazu | because reviewing everything in one proposal is a bit complicated :) | 09:24 |
| kazu | any other topics? | 09:24 |
| masashi910 | kazu: thank you! | 09:25 |
| masashi910 | then let's move to the next | 09:25 |
| masashi910 | #topic Software update | 09:25 |
| *** brlogger` changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:25 | |
| suzuki90 | hi | 09:25 |
| suzuki90 | I've put a license file of apache license 2.0 into the top of cip-sw-updates-demo repository. | 09:25 |
| suzuki90 | https://gitlab.com/cip-playground/cip-sw-updates-demo/blob/master/LICENSE | 09:25 |
| suzuki90 | And I'm preparing an approval request for creating our WG's subgroup in cip-project of Gitlab. | 09:25 |
| suzuki90 | That's all from me. | 09:26 |
| masashi910 | suzuki90: Thanks! | 09:26 |
| masashi910 | any other topics? | 09:26 |
| masashi910 | 3 | 09:26 |
| masashi910 | 2 | 09:26 |
| masashi910 | 1 | 09:26 |
| masashi910 | #topic AOB | 09:26 |
| *** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:26 | |
| masashi910 | 1. IRC meeting next week | 09:26 |
| masashi910 | Although it is a holiday season, I would like to hold an IRC meeting next week. | 09:26 |
| masashi910 | 3 | 09:27 |
| masashi910 | 2 | 09:27 |
| masashi910 | 1 | 09:27 |
| kazu | hi | 09:27 |
| masashi910 | kazu: please | 09:27 |
| kazu | can i ask one? | 09:27 |
| patersonc | I'll be missing the meeting for the next 2 weeks | 09:27 |
| masashi910 | patersonc: OK, thanks for letting me know. | 09:27 |
| kazu | I'm checking the existing kernel configs for each CIP reference hardware, the following understanding correct? | 09:27 |
| kazu | Available configs: https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/tree/master/4.19.y-cip/ | 09:28 |
| pave1 | So Dec 26? Not sure if I'll be able to make that one. | 09:28 |
| kazu | Used configs: https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/blob/master/trees/linux-4.19.y-cip.yml | 09:28 |
| kazu | qemux86-64: (no config?)bbb: (no config?)iwg20m: renesas_shmobile_defconfigsimatic-ipc227e: ?OpenBlocks IoT: plathome_obsvx2.confighihope-rzg2m: renesas_defconfig | 09:28 |
| kazu | Oops, will add one by one... | 09:28 |
| patersonc | I think that's correct | 09:28 |
| kazu | qemux86-64: (no config?) | 09:28 |
| kazu | bbb: (no config?) | 09:28 |
| kazu | iwg20m: renesas_shmobile_defconfig | 09:28 |
| masashi910 | pave1: thanks. No worries. | 09:29 |
| kazu | simatic-ipc227e: ? | 09:29 |
| kazu | OpenBlocks IoT: plathome_obsvx2.config | 09:29 |
| kazu | hihope-rzg2m: renesas_defconfig | 09:29 |
| kazu | I just want to confirm if there are configs for qemux86-64 and bbb or not... | 09:30 |
| patersonc | No that I've seen | 09:30 |
| patersonc | If they are added I'll start building them in CI :) | 09:30 |
| iwamatsu | kazu: I have a config to qemu-x86-64. so I will send PR to config repo. | 09:30 |
| pave1 | Do we have qemu/bbb configured so that it could be used for testing if we hav ethe configs? | 09:30 |
| patersonc | Or if someone points me to a suitable config elsewhere/intree | 09:31 |
| patersonc | pave1: qemu - yes. BBB - maybe e/Jan | 09:31 |
| kazu | patersonc iwamatsu Thank you | 09:31 |
| patersonc | We can build without the boards in the lab though | 09:31 |
| masashi910 | kazu, patersonc, iwamatsu, pave1: thanks for your discussion. | 09:32 |
| pave1 | patersonc: Yes, agreed. | 09:32 |
| masashi910 | kazu: do you think any AI needed? | 09:32 |
| kazu | At least, the config for qemux86-64 will be added through the PR? | 09:33 |
| patersonc | Agreed. And a config for BBB would be good too. | 09:34 |
| iwamatsu | OK, I ask BBB config to Jan. | 09:34 |
| patersonc | For both boards, I think we need a config for both 4.4 and 4.19 | 09:34 |
| kazu | patersonc iwamatsu Thank you again | 09:35 |
| iwamatsu | And I send PR to config repo, OK? | 09:35 |
| masashi910 | AI: add config for qemux86-64 and BBB. Is it reasonable? | 09:36 |
| kazu | I'm OK, thanks | 09:36 |
| masashi910 | kazu: thanks. | 09:36 |
| masashi910 | any other business? | 09:36 |
| masashi910 | 3 | 09:36 |
| masashi910 | 2 | 09:36 |
| masashi910 | 1 | 09:37 |
| masashi910 | #endmeeting | 09:37 |
| brlogger` | Meeting ended Thu Dec 19 09:37:03 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:37 |
| brlogger` | Minutes: https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-19-09.00.html | 09:37 |
| brlogger` | Minutes (text): https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-19-09.00.txt | 09:37 |
| brlogger` | Log: https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-19-09.00.log.html | 09:37 |
| *** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:37 | |
| wens | thanks! | 09:37 |
| kazu | Thank you everyone :) | 09:37 |
| pave1 | Thanks! | 09:37 |
| suzuki90 | Thank you! | 09:37 |
| masashi910 | thanks bye-bye! | 09:37 |
| *** suzuki90 has quit IRC | 09:37 | |
| iwamatsu | thank you | 09:38 |
| patersonc | See you in the new year! | 09:38 |
| patersonc | iwamatsu: I've sent some MR reviews your way, if you have time | 09:38 |
| pave1 | wens: Would it make sense to pick up patches from stable-5.4 as a backup? That way if regular expressions fail to pick them on the list, they are still not lost... | 09:38 |
| iwamatsu | patersonc: OK, I will check | 09:38 |
| patersonc | iwamatsu: Thank you! | 09:38 |
| pave1 | wens: But my main question was: is there list of patches that should be backported (or at least looked at) somewhere? | 09:39 |
| patersonc | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/ ;) | 09:40 |
| wens | pave1: currently there isn't. for now it's just looking at what was posted vs what was picked up | 09:40 |
| pave1 | patersonc: :-). I was hoping for a little.. shorter list ;-). | 09:40 |
| patersonc | git log -1000 ? | 09:40 |
| pave1 | patersonc: I hate you :-). | 09:41 |
| patersonc | You're welcome! | 09:41 |
| patersonc | It's a serious question though, especially when Greg stops supporting 4.4/4.19 | 09:41 |
| patersonc | I wonder if CIP will have to have our own AI tool like Sasha? (well, re-use his) | 09:41 |
| wens | I guess the issue is the same, humans are needed to judge whether a patch needs to be backported | 09:42 |
| pave1 | wens: Ok, so if you see something critical (maybe those 3 CVEs?), could you notify the lists? | 09:42 |
| pave1 | patersonc: I believe starting from Linus' tree is ... way too much work. | 09:42 |
| pave1 | patersonc: But we can start from the oldest -stable that _is_ supported. | 09:43 |
| pave1 | patersonc: If we filter out everything with Sasha's name on it, we may have quite reasonable list. | 09:43 |
| patersonc | True | 09:43 |
| wens | pave1: regarding having stable-5.4 as a backup, could you elaborate? | 09:44 |
| patersonc | Presumably not everything Sasha selects is bad though? | 09:44 |
| pave1 | patersonc: Alternatively.... there are distributions such as SuSE doing very similar work. | 09:44 |
| pave1 | patersonc: But when I checked, they were maintaining 4.4 but not 4.19 iirc. | 09:44 |
| wens | pave1: you mean looking at v5.4..stable-5.4.y right? | 09:45 |
| pave1 | patersonc: I have not really seen many from Sasha screaming "this is critical". People are normally quite good at adding cc: stable. | 09:46 |
| patersonc | pave1: Fair doos | 09:47 |
| wens | either that, or other people figure out something broke and patch(es) need to be backported | 09:47 |
| pave1 | wens: My idea was.. if the scripts fail to pick up patch from the stable mailing list, and the patch appears in stable-5.4, we still may want to look at it. | 09:48 |
| wens | I see. The scripts will pick up stable-5.4 rc review series though | 09:48 |
| wens | unless Greg changes his tooling, or somehow sneaks in a patch without review | 09:48 |
| wens | but hey, Linus does that lol | 09:49 |
| pave1 | Aha. Ok... in such case, I guess we don't need to do much. | 09:49 |
| pave1 | wens: Hmm. Greg does that, too. | 09:49 |
| wens | ok, I'll look into it and maybe merge that into the produced patch-list | 09:49 |
| pave1 | wens: When problems are found during 4.19.91-rc1 review, he'll push 4.19.91-rc2 to the git, maybe with some new patches, and I'm not sure if those are cc-ed to the lists... | 09:50 |
| wens | I don't recall seeing them marked that way | 09:51 |
| wens | so probably not | 09:51 |
| iwamatsu | CC doesn't seem to be. It is reported that rc2 has been released. | 09:52 |
| pave1 | You mentioned 3 CVEs in need of backporting. Do you have links (or could you send them to cip-dev)? | 09:53 |
| wens | the tool also doesn't know about rejected patches, so presumably we would want to add an ignore list | 09:53 |
| wens | the 3 CVEs are not fixed in mainline yet | 09:53 |
| pave1 | wens: Aha, ok. | 09:55 |
| wens | the one that was fixed has fixes all the way back to 4.14 | 09:55 |
| wens | pave1: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4ea99936a1630f51fc3a2d61a58ec4a1c4b7d55a | 09:57 |
| pave1 | Ok, that may get an CVE... but hopefully people are not enabling random debugging options in production, so I don't see it as critical. | 09:58 |
| pave1 | (But thanks :-) ) | 09:59 |
| wens | no problem | 09:59 |
| wens | there's a bunch of CVEs that are really corner cases... like the "crafted filesystem" types | 10:00 |
| wens | not something the average user is going to run into | 10:00 |
| pave1 | Yep. Having a CVE does not mean bug is critical, really. "Denial of service" aka "kernel crash" can get a CVE, too.... | 10:01 |
| pave1 | patersonc: I did push to https://gitlab.com/cip-project/cip-kernel/linux-cip/tree/ci/pavel/linux-cip to get the kernel tested, but I don't see usual icons from the CI. | 10:05 |
| pave1 | Do I need to do something else? | 10:05 |
| patersonc | pave1: When did you push? | 10:06 |
| pave1 | Few minutes ago. | 10:06 |
| patersonc | Sometimes there are some delays on GitLab's servers | 10:06 |
| patersonc | I suggest wait 10 mins | 10:07 |
| patersonc | If it still doesn't happen you can kick the build off manually | 10:07 |
| patersonc | https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/new | 10:07 |
| pave1 | Aha, ok :-). | 10:07 |
| patersonc | I see a lot of problems with gitlab.com's services :( | 10:07 |
| patersonc | A lot of 500 errors etc. when trying to access their own repositories etc. | 10:08 |
| pave1 | Hosting sources is quite complex problems, it seems. | 10:08 |
| patersonc | I've heard that rumour! | 10:08 |
| pave1 | :-) | 10:08 |
| patersonc | * goes afk for 15 mins | 10:09 |
| * patersonc * goes afk for 15 mins | 10:09 | |
| *** masashi910 has quit IRC | 10:21 | |
| *** masashi910 has joined #cip | 10:26 | |
| patersonc | pave1: Did you trigger it manually in the end? | 10:30 |
| pave1 | patersonc: Yes, and that did the trick. | 10:38 |
| *** kazu has quit IRC | 10:42 | |
| patersonc | :) | 10:43 |
| pave1 | Thanks for help and bye for now... | 10:49 |
| patersonc | ttfn | 10:49 |
| patersonc | iwamatsu: ping | 10:50 |
| *** pave1 has quit IRC | 10:52 | |
| *** masashi910 has quit IRC | 10:57 | |
| *** cp- has quit IRC | 16:05 | |
| *** cp- has joined #cip | 16:06 | |
| *** cp- has quit IRC | 16:11 | |
| *** cp- has joined #cip | 16:12 | |
| *** therisen has quit IRC | 16:16 | |
| *** m4t has quit IRC | 20:18 | |
| *** m4t has joined #cip | 20:21 | |
| *** masashi910 has joined #cip | 22:59 | |
| *** rajm has quit IRC | 23:01 | |
| *** masashi910 has quit IRC | 23:04 | |
| *** masashi910 has joined #cip | 23:04 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!