*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 00:51 | |
*** monstr <monstr!~monstr@2a02:768:2307:40d6:f666:9af6:3fed:e53b> has joined #cip | 07:42 | |
*** masami <masami!~masami@FL1-60-237-215-110.tky.mesh.ad.jp> has joined #cip | 12:29 | |
*** uli <uli!~uli@55d42c1b.access.ecotel.net> has joined #cip | 12:50 | |
*** pavel <pavel!~pavel@88.103.239.131> has joined #cip | 12:58 | |
*** pavel is now known as pav3l | 12:58 | |
*** pav3l is now known as pave1 | 12:58 | |
*** josiah|2 <josiah|2!~kvirc@pool-71-179-138-156.bltmmd.fios.verizon.net> has joined #cip | 13:00 | |
*** jki <jki!~jki@88.215.84.132> has joined #cip | 13:01 | |
jki | #startmeeting CIP IRC weekly meeting | 13:02 |
---|---|---|
brlogger_ | Meeting started Thu Sep 9 13:02:10 2021 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:02 |
brlogger_ | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:02 |
brlogger_ | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:02 |
*** brlogger_ changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
jki | #topic rollcall | 13:02 |
*** brlogger_ changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
pave1 | hi | 13:02 |
jki | hi everyone | 13:02 |
uli | hi | 13:02 |
alicef | o/ | 13:02 |
masami | hi | 13:02 |
josiah|2 | Hi | 13:02 |
jki | great, almost full-house | 13:03 |
jki | is chris going to join? | 13:03 |
patersonc[m] | hi | 13:03 |
jki | perfect | 13:03 |
jki | anyone missing? | 13:03 |
jki | iwamatsu | 13:04 |
jki | well, let's start nevertheless I would say | 13:05 |
pave1 | Yep :-). | 13:05 |
jki | #topic AI review | 13:05 |
*** brlogger_ changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:05 | |
jki | 1. Combine root filesystem with kselftest binary - iwamatsu & alicef | 13:06 |
jki | any news? | 13:06 |
patersonc[m] | I don't think so | 13:06 |
alicef | Investigating on how to expand the cip-core for make kselftest work on the user space | 13:06 |
alicef | expand cip-core space | 13:07 |
jki | ok - i know it's being used already, I suppose you saw the recipe | 13:07 |
alicef | yes | 13:07 |
jki | but I don't have details either -> maybe contact our mentor colleagues | 13:07 |
jki | e.g. via isar ML | 13:08 |
alicef | yes | 13:08 |
jki | good | 13:08 |
jki | any new AIs? | 13:08 |
jki | I think I forgot one from last week: | 13:09 |
jki | Add lava URLs to wiki page | 13:09 |
jki | patersonc: think you wanted to check that, right? | 13:10 |
patersonc[m] | I can't remember the details for this | 13:12 |
jki | kernelci.ciplatform.org and cip.kernelci.org: add to wiki once ready | 13:13 |
alicef | jki: cip.kernelci.org is already ready | 13:13 |
patersonc[m] | Ah okay | 13:13 |
patersonc[m] | Thanks | 13:13 |
patersonc[m] | I'll get that done | 13:13 |
jki | TIA! | 13:14 |
jki | other AIs? | 13:14 |
jki | 3 | 13:14 |
jki | 2 | 13:14 |
jki | 1 | 13:14 |
jki | #topic Kernel maintenance updates | 13:14 |
*** brlogger_ changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:14 | |
pave1 | I have reviewed patches queued for 5.10.62/63/64. | 13:15 |
uli | fixed a couple of minor issues in the scripts in cip-kernel-config and lts-commit-list | 13:15 |
masami | There is 3 new CVEs in this week. | 13:15 |
masami | CVE-2021-3715, CVE-2021-3759, CVE-2021-40490 are new CVEs. | 13:15 |
masami | These CVEs have been fixed in the mainline and some stable kernels. | 13:15 |
masami | CVE-2021-3739, CVE-2021-3743, CVE-2021-3753, CVE-2021-38198, CVE-2021-3444, CVE-2021-3600 have updated. | 13:16 |
masami | They have been fixed in the mainline and some stable kernels. | 13:16 |
jki | also for all our CIP kernel versions? | 13:18 |
jki | or how do those report map on our kernels generally? | 13:18 |
masami | jki: not all cip kernels are fixed. | 13:19 |
pave1 | jki: We don't have to do anything this week. | 13:19 |
jki | ok | 13:19 |
pave1 | jki: CVE-2021-3759: is missing cgroup accounting -- DoS only if you have shell. | 13:20 |
jki | still learning the meanings ;) | 13:20 |
masami | jik: This report is based on mainline and stable kernels. | 13:20 |
pave1 | CVE-2021-38198: is KVM nastyness. It is unclear if we want to track this one. Anyway someone backported it to 4.14, so things are improving. | 13:21 |
jki | ok - move on? | 13:21 |
pave1 | 3 | 13:22 |
pave1 | 2 | 13:22 |
pave1 | 1 | 13:22 |
pave1 | :-) | 13:22 |
jki | #topic Kernel testing | 13:22 |
*** brlogger_ changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:22 | |
alicef | cip KernelCI production can now be seen at https://cip.kernelci.org | 13:23 |
patersonc[m] | We've been working on various topics for the KernelCI kackfest | 13:23 |
patersonc[m] | hackfest | 13:23 |
alicef | smc (spectre meltdown check) | 13:23 |
alicef | got merged and is now working on production | 13:23 |
alicef | example: https://linux.kernelci.org/test/plan/id/6138e379ab9d472d1ad596a8/ | 13:23 |
alicef | currently some cip configuration are used on staging kernelci (currently only for qemu arm and x86-64) | 13:23 |
alicef | configuration are from https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/ | 13:23 |
alicef | patersonc[m] and I are currently fixing the kernelci pages links about and reference about CIP | 13:24 |
alicef | like https://static.staging.kernelci.org/docs/org/tsc/#cip-instance and https://static.staging.kernelci.org/docs/instances/ | 13:25 |
jki | nice | 13:25 |
alicef | currently I'm working with the help of patersonc[m] on making kernelci work with the isar-cip-core images | 13:26 |
alicef | also I'm adding iec-security-tests as kernelci test | 13:26 |
jki | ok - i think / hope the preconditions are fulfilled | 13:26 |
jki | like being able to generate to right images (tarballs etc.) | 13:26 |
alicef | that is what I'm working on yes | 13:27 |
jki | if something should be missing, we have other isar layers generating for lava, e.g. https://gitlab.denx.de/Xenomai/xenomai-images | 13:27 |
alicef | mmm ? | 13:28 |
alicef | if something is missing we cannot just add it to the isar-cip-core ? | 13:28 |
jki | yes, sure | 13:28 |
jki | that link was just another source of inspiration | 13:29 |
alicef | I didn't know about xenomai-core | 13:29 |
jki | or ask on the list, we could help so that you don't need to learn isar first | 13:29 |
jki | and isar-cip-core | 13:29 |
alicef | currently I'm making the script for deploying the images to kernelci fileserver | 13:29 |
alicef | using the kernelci api | 13:29 |
jki | ok, that is surely specific | 13:30 |
alicef | jki: thanks that would be helpful | 13:30 |
jki | drop an email with question, my colleague Quirin can likely help as well (he did that for xenomai) | 13:31 |
alicef | creating tarball ? | 13:31 |
jki | including that, yes | 13:31 |
alicef | yes ok | 13:32 |
jki | kas[-container] build ...:kas/opt/targz-img.yml | 13:32 |
alicef | there are no other updates for me | 13:32 |
alicef | yes | 13:33 |
jki | ok - anything else for this topic? | 13:33 |
alicef | on isar just need to be enabled from .gitlab-ci | 13:33 |
alicef | not at the moment | 13:33 |
jki | #topic AOB | 13:33 |
*** brlogger_ changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:33 | |
uli | one thing | 13:34 |
uli | i'm a "developer" member of all projects on gitlab now, but the master branches of cip-kernel-config and lts-commit-list are set to "protected" | 13:34 |
uli | apparently that means i need extra-special permissions to push there | 13:34 |
uli | who do i bother about that? | 13:34 |
pave1 | You definitely need permissons for lts-commit-list. | 13:34 |
jki | handling that | 13:35 |
uli | ok, thanks | 13:35 |
jki | how is cip-kernel-config maintained so far? | 13:36 |
jki | multi-maintainer? MRs? | 13:36 |
pave1 | iwamatsu is marked a | 13:36 |
pave1 | as a maintainer. | 13:36 |
jki | so he will merge to master? | 13:36 |
pave1 | I believe I have committed directly to it, but he's the one responsible... | 13:36 |
jki | then let's clarify this with him | 13:37 |
jki | maybe write him an email, uli? | 13:38 |
uli | can do | 13:38 |
pave1 | I believe Ulrich should get access there (same as lts-commit-list), but in this case it might be polite to ask before commiting. | 13:38 |
jki | right | 13:39 |
jki | lts-commit-list already done now | 13:39 |
uli | thx | 13:39 |
jki | good, any other access issues to clarify? | 13:39 |
uli | not from me | 13:39 |
jki | or other AOBs? | 13:40 |
pave1 | We should probably create shared whiteboard somewhere to coordinate patch reviews. | 13:40 |
pave1 | Not sure if git is suitable for that... | 13:40 |
pave1 | Ideally something that can be easily scripted... | 13:40 |
pave1 | If someone has quick idea, speak now, otherwise I'll write email to the list. | 13:41 |
jki | would issue tracking work (with email feeding)? | 13:41 |
pave1 | I think I'd avoid email for this. | 13:41 |
pave1 | I was thinking more like wiki page. We don't really need history, we just need shared place where people can write to easily. | 13:42 |
jki | wiki is generally with history... | 13:42 |
pave1 | jki: I know. I guess we can live with history but don't need it. | 13:43 |
jki | ...and is actually in git, if using one from gitlab.com | 13:43 |
jki | but maybe start with describing the workflows you have in mind | 13:43 |
pave1 | Ok, lets do that over email? | 13:43 |
jki | fine for me | 13:44 |
jki | anything else for today? | 13:44 |
jki | 3 | 13:45 |
jki | 2 | 13:45 |
jki | 1 | 13:45 |
jki | thank you all, have a nice day! | 13:45 |
jki | #endmeeting | 13:45 |
brlogger_ | Meeting ended Thu Sep 9 13:45:47 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:45 |
brlogger_ | Minutes: https://irclogs.baserock.org/meetings/cip/2021/09/cip.2021-09-09-13.02.html | 13:45 |
brlogger_ | Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/09/cip.2021-09-09-13.02.txt | 13:45 |
brlogger_ | Log: https://irclogs.baserock.org/meetings/cip/2021/09/cip.2021-09-09-13.02.log.html | 13:45 |
*** brlogger_ changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 13:45 | |
pave1 | Thank you! ...and stay safe. | 13:46 |
masami | Thank you! bye! | 13:46 |
uli | see you | 13:46 |
jki | you too, bye! | 13:46 |
*** masami <masami!~masami@FL1-60-237-215-110.tky.mesh.ad.jp> has quit IRC | 13:47 | |
*** josiah|2 <josiah|2!~kvirc@pool-71-179-138-156.bltmmd.fios.verizon.net> has quit IRC | 13:52 | |
*** pave1 <pave1!~pavel@88.103.239.131> has quit IRC | 13:53 | |
*** jki <jki!~jki@88.215.84.132> has quit IRC | 14:01 | |
*** uli <uli!~uli@55d42c1b.access.ecotel.net> has left #cip | 14:04 | |
*** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip | 14:25 | |
*** zar_ <zar_!~quassel@mail.nazaryev.ru> has quit IRC | 14:25 | |
*** zar_ <zar_!~quassel@mail.nazaryev.ru> has joined #cip | 14:30 | |
*** zar <zar!~quassel@mail.nazaryev.ru> has quit IRC | 14:30 | |
*** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip | 14:58 | |
*** zar_ <zar_!~quassel@mail.nazaryev.ru> has quit IRC | 14:58 | |
*** zar <zar!~quassel@mail.nazaryev.ru> has quit IRC | 14:59 | |
*** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip | 14:59 | |
*** zar <zar!~quassel@mail.nazaryev.ru> has quit IRC | 15:00 | |
*** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip | 15:00 | |
*** brlogger <brlogger!~supybot@45.114.123.168> has joined #cip | 15:02 | |
*** ChanServ sets mode: +o brlogger | 15:02 | |
*** brlogger <brlogger!~supybot@45.114.123.168> has joined #cip | 15:05 | |
*** ChanServ sets mode: +o brlogger | 15:05 | |
*** zar <zar!~quassel@mail.nazaryev.ru> has quit IRC | 15:05 | |
*** monstr <monstr!~monstr@2a02:768:2307:40d6:f666:9af6:3fed:e53b> has quit IRC | 16:50 | |
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 21:51 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!