| *** iwamatsu has joined #cip | 04:09 | |
| *** iwamatsu has quit IRC | 04:10 | |
| *** iwamatsu has joined #cip | 04:12 | |
| *** iwamatsu has quit IRC | 04:13 | |
| *** iwamatsu has joined #cip | 04:16 | |
| *** iwamatsu has joined #cip | 04:16 | |
| *** iwamatsu has quit IRC | 04:17 | |
| *** iwamatsu has joined #cip | 04:18 | |
| *** iwamatsu has quit IRC | 04:29 | |
| *** iwamatsu has joined #cip | 04:29 | |
| *** iwamatsu has quit IRC | 04:53 | |
| *** iwamatsu has joined #cip | 04:53 | |
| *** iwamatsu has quit IRC | 04:55 | |
| *** iwamatsu has joined #cip | 04:57 | |
| *** iwamatsu_ has joined #cip | 04:59 | |
| *** robertmarshall has joined #cip | 07:09 | |
| *** patersonc has joined #cip | 07:16 | |
| *** robertmarshall has quit IRC | 07:18 | |
| *** robertmarshall has joined #cip | 07:18 | |
| *** robertmarshall is now known as rajm | 07:20 | |
| *** iwamatsu__ has joined #cip | 07:36 | |
| *** iwamatsu__ has quit IRC | 07:37 | |
| *** iwamatsu__ has joined #cip | 07:39 | |
| *** iwamatsu__ has quit IRC | 07:40 | |
| * rajm returns and has run a successful healthcheck on BBB with an email to the list | 07:51 | |
| *** iwamatsu__ has joined #cip | 07:52 | |
| *** hungtran has joined #cip | 07:57 | |
| *** HoloIRCUser has joined #cip | 07:57 | |
| HoloIRCUser | , | 07:58 |
|---|---|---|
| patersonc | Welcome back rajm | 07:58 |
| rajm | thanks patersonc! | 07:58 |
| *** HoloIRCUser is now known as iwamatsu____ | 07:58 | |
| *** Tzongyen_Lin has joined #cip | 07:59 | |
| szlin | #startmeeting | 08:00 |
| szlin | #roll call | 08:00 |
| szlin | please say hi if you're here. | 08:00 |
| patersonc | hi | 08:01 |
| hungtran | hi | 08:03 |
| patersonc | Not many here today then? | 08:05 |
| *** mungaip has joined #cip | 08:06 | |
| patersonc | Hi szlin, is the meeting going ahead? | 08:09 |
| iwamatsu____ | hi! | 08:10 |
| Tzongyen_Lin | hi | 08:10 |
| *** iwamatsu__ has joined #cip | 08:10 | |
| *** iwamatsu__ has joined #cip | 08:10 | |
| szlin | ._./ | 08:11 |
| szlin | #topic action item review | 08:11 |
| szlin | About having a git group account in kernel.org - still waiting for response from Ben | 08:11 |
| szlin | https://lists.cip-project.org/pipermail/cip-dev/2018-August/001505.html | 08:11 |
| szlin | #topic kernel maintenance updates | 08:11 |
| szlin | I've sent some overlayfs backport patches to stable-4.4.y | 08:11 |
| szlin | https://www.spinics.net/lists/stable/msg253507.html | 08:11 |
| szlin | These patches fix read-only issue when non-empty workdir occurred | 08:11 |
| szlin | in overlayfs, the non-empty workdir could be easily reproduced in | 08:11 |
| szlin | power-failure test during write operations. | 08:11 |
| szlin | I will continue to send bugfix patches in overlayfs in these day. | 08:11 |
| szlin | patersonc: yes | 08:11 |
| szlin | patersonc: the network status seems weird. | 08:11 |
| patersonc | szlin: Yes, I just got 10 lines at once! | 08:11 |
| szlin | patersonc: can you see my updates? | 08:11 |
| szlin | oops... | 08:11 |
| patersonc | :) | 08:11 |
| *** toscalix has joined #cip | 08:11 | |
| szlin | According to kernel.org, the next stable kernel might be 4.19 | 08:12 |
| patersonc | Has anyone seen anything concrete about LTS v4.19? | 08:12 |
| *** toscalix has quit IRC | 08:13 | |
| patersonc | szlin: Do we know when Debian will make a decision on their next Kernel? | 08:14 |
| szlin | Not from me | 08:14 |
| szlin | patersonc: we need to ask Ben | 08:14 |
| patersonc | Okay | 08:14 |
| *** toscalix has joined #cip | 08:15 | |
| szlin | But the date of 4.19 might be happened in Oct or Nov. | 08:15 |
| patersonc | I would guess v4.19 will be out mid Oct | 08:16 |
| szlin | patersonc: about the kernel of buster, you may refer to here | 08:17 |
| szlin | https://lists.debian.org/debian-kernel/2016/08/msg00099.html | 08:17 |
| *** moxavictor has joined #cip | 08:17 | |
| *** sangorrin has joined #cip | 08:17 | |
| sangorrin | yes | 08:17 |
| szlin | that's why I mentioned that we need to ask Ben | 08:18 |
| patersonc | Okay | 08:18 |
| szlin | any other point? | 08:18 |
| sangorrin | https://www.kernel.org/releases.html | 08:18 |
| sangorrin | yes | 08:19 |
| sangorrin | the bug that jan mentioned the other day | 08:19 |
| sangorrin | L1FT or something | 08:19 |
| patersonc | That's the new Intel bug | 08:19 |
| sangorrin | it was fixed in 4.4 from what i see | 08:19 |
| sangorrin | in the patch queue | 08:19 |
| szlin | sangorrin: https://www.phoronix.com/scan.php?page=news_item&px=L1TF-Foreshadow-Kernel-Updates | 08:20 |
| toscalix | sangorrin: bwh is working on the new CIP 4.4 kernel and includes that patch | 08:20 |
| iwamatsu____ | nice | 08:20 |
| sangorrin | ok cool | 08:20 |
| toscalix | I believe I mentioned a few days ago somewhere (I cannot remember when or where, but CIP channel for sure) | 08:21 |
| szlin | toscalix: did you get the feedback from Ben? About having a git group account in kernel.org | 08:21 |
| sangorrin | it will be good to run LTP cve tests often | 08:21 |
| patersonc | Are there any specific test cases for it? | 08:21 |
| sangorrin | i think the spectre bugs appear in /proc somewhere | 08:21 |
| sangorrin | so we could add a test checking /proc/cpuinfo | 08:22 |
| toscalix | szlin: no about that point no | 08:22 |
| sangorrin | also in /sys/devices/system/cpu/vulnerabilities/l1tf | 08:22 |
| toscalix | szlin: I thought it was solved. I mean, we were going to ask | 08:23 |
| sangorrin | toscalix: wagner mentioned an email address | 08:23 |
| * toscalix have a release next week. I have been disconnected the last few days | 08:24 | |
| sangorrin | https://www.kernel.org/category/contact-us.html | 08:24 |
| sangorrin | the problem is that we need someone with reputation to back us, so Ben could help us with that | 08:24 |
| szlin | toscalix: sorry, I don't get it. who will ask group account in kernel.org for CIP | 08:24 |
| toscalix | szlin: should it be Ben? | 08:26 |
| toscalix | or somebody with certain level of representation will? | 08:26 |
| toscalix | who will manage it? | 08:26 |
| szlin | ok, I suggest to discuss this topic in TSC meeting next Monday | 08:27 |
| sangorrin | toscalix: good point, maybe we can wait until the next kernel maintainer is completely decided | 08:27 |
| patersonc | TSC should probably set it up, but having Ben's/Greg's ack would help | 08:28 |
| toscalix | patersonc: agree. I believe there is a mail I sent last week about it and Ben haven't answered it. I will ping him about it | 08:29 |
| patersonc | Thanks | 08:29 |
| patersonc | o/ | 08:29 |
| szlin | #action Agustin will ping Ben for the feedback of git group account in kernel.org | 08:30 |
| szlin | patersonc: please | 08:30 |
| szlin | any other point? | 08:31 |
| patersonc | If CIP chooses v4.19 for the next Kernel, when do you think we'd aim to make the first v4.19.y-cip release? | 08:31 |
| sangorrin | it would be nice to have support for RX-G1M as soon as it is released | 08:32 |
| sangorrin | RZ i mean | 08:32 |
| patersonc | RZ/G1M should be supported by default as it is upstreamed | 08:33 |
| sangorrin | that's great | 08:33 |
| szlin | I think it depends on the maintainer of 4.19 in CIP. AFAIK, we don't have release policy about that. | 08:33 |
| patersonc | RZ/G2M will not be, as we're still upstreaming it. First patches will hit v4.20 | 08:33 |
| szlin | (please correct me if I'm wrong | 08:33 |
| patersonc | szlin: I don't think there is a policy, no. | 08:34 |
| szlin | patersonc: so you may contact maintainer of 4.19.y in CIP for that | 08:35 |
| patersonc | Okay | 08:36 |
| szlin | any other point? | 08:36 |
| szlin | 3 | 08:36 |
| szlin | 2 | 08:36 |
| szlin | 1 | 08:36 |
| szlin | #topic kernel testing | 08:36 |
| szlin | Any update? | 08:37 |
| toscalix | rajm ? | 08:37 |
| * toscalix pnging rajm | 08:37 | |
| szlin | thanks. let's move forward | 08:38 |
| szlin | #topic AOB | 08:38 |
| toscalix | meanwhile, I have a question | 08:38 |
| szlin | please | 08:38 |
| toscalix | about kernel testing | 08:38 |
| toscalix | is there a prospect date to have the infra in place for testing it? | 08:38 |
| rajm | sorry - missed the ping | 08:41 |
| toscalix | a line or two of your recent progress? | 08:41 |
| rajm | to give a late update - moving forward with containering the kernelci and LAVA - some issues with networking and inter docker package communication | 08:42 |
| rajm | now that I'm back off a week away I'll look to addressing there - thanks | 08:43 |
| toscalix | where can we follow progress? | 08:43 |
| toscalix | tickets to follow? | 08:44 |
| rajm | hopefully here, and in the ticket / journal | 08:44 |
| rajm | just a mo | 08:44 |
| sangorrin | rajm: are you using compose? one reason it may not communicate is if you don't put the compose version | 08:44 |
| rajm | I am using compose | 08:44 |
| *** moxavictor has quit IRC | 08:45 | |
| rajm | journal at https://wiki.linuxfoundation.org/civilinfrastructureplatform/journal | 08:45 |
| toscalix | https://gitlab.com/cip-project/cip-testing/testing/issues/192 | 08:45 |
| rajm | I was using lucj's version which uses compose in the start.sh script but I'm still finding issues | 08:45 |
| szlin | toscalix: we want to build the infra. at our own site in Q1/ Q2 next year, and we're working on it. | 08:46 |
| toscalix | and check related issues | 08:46 |
| szlin | Align with CIP testing is our next step. | 08:46 |
| rajm | thanks toscalix (and #197) | 08:46 |
| szlin | patersonc: sangorrin do you have any prospect date to have the infra in place for testing it? | 08:47 |
| toscalix | in order for each one of us to align, we need to know details about the CIP infra | 08:47 |
| sangorrin | rajm: I added stuff for proxy's in lucj's version. I hope i didnt break that :) | 08:47 |
| rajm | sangorrin: I'll check the commits - the kernelci looks fine it's 'just' an inability to download any builds | 08:48 |
| sangorrin | szlin: i don't have time to maintain a lab, I use fuego for testing CIP | 08:48 |
| patersonc | szlin: We're currently trying to get B@D up and running for iwg20m behind our firewalls etc. Next step is to get a lava-slave up and running for CIP. | 08:48 |
| patersonc | (thanks to rajm for his help) | 08:48 |
| szlin | thanks. | 08:48 |
| rajm | ta patersonc! | 08:49 |
| toscalix | sangorrin: we do not either. We hope to use B@D and send results to the central infra | 08:49 |
| sangorrin | rajm: yes i have seen that problem | 08:49 |
| sangorrin | i think you still can access the builds if you input the url by hand | 08:49 |
| patersonc | There is already a central kernelci server, so I guess B@D could be configured to report there? | 08:49 |
| sangorrin | but the links are wrong | 08:49 |
| toscalix | patersonc: yes | 08:49 |
| patersonc | https://kernelci.ciplatform.org/ | 08:50 |
| toscalix | \o/ | 08:50 |
| rajm | ah - they're trying to pull off the local docker and they need to use one of the other instances | 08:50 |
| sangorrin | toscalix: yeah, the central infra is what i am waiting for as well | 08:51 |
| patersonc | We need to assign a KernelCI maintainer/admin I guess. | 08:51 |
| sangorrin | patersonc: yes, someone that assigns the tokens etc | 08:52 |
| toscalix | patersonc: yes | 08:52 |
| patersonc | Does anyone have and experience with KernelCI? | 08:52 |
| toscalix | patersonc: since this person needs to be assigned internally, because it will require some work, this is the perfect topic to raise at TSC | 08:53 |
| sangorrin | patersonc: I have a little of experience, but not as much as rajm or robert | 08:53 |
| patersonc | toscalix: I was about to say that :) | 08:53 |
| toscalix | it cannot be on best effort basis. It requires internal support from the company to do this | 08:54 |
| szlin | #action discuss the KernelCI maintainer/admin at TSC meeting | 08:54 |
| rajm | Needs to do some looking on those issues - I was thinking it might need knowlege of the guts of the system but maybe not | 08:54 |
| sangorrin | in agl the maintenance is done by kernelci creators, isn't it? | 08:55 |
| toscalix | there is a contract in place and jan-simon also helps | 08:55 |
| toscalix | but the contract is not just for this, but for other tasks also | 08:55 |
| toscalix | I would assume a CIP Member would contribute with a person for this | 08:56 |
| sangorrin | do you mean at full time? | 08:57 |
| patersonc | szlin: The TSC topic should cover all testing infrastructure (e.g. lava master), not just KernelCI | 08:57 |
| toscalix | since every company tests kernels, so this can be a good place to learn or an easy infra to maintain if you are already maintaining one | 08:57 |
| patersonc | sangorrin: I wouldn't have thought so | 08:57 |
| toscalix | sangorrin: no full time no, but more time at the beginning, less overtime | 08:57 |
| szlin | #undo | 08:57 |
| szlin | #action discuss the testing infra. including maintainer/admin at TSC meeting | 08:58 |
| * toscalix need to go | 08:58 | |
| szlin | any other point? | 08:58 |
| szlin | 3 | 08:58 |
| szlin | 2 | 08:58 |
| szlin | 1 | 08:58 |
| szlin | #endmeeting | 08:58 |
| szlin | thanks all | 08:58 |
| patersonc | Thanks | 08:59 |
| sangorrin | oh too late, but i was going to ask if we are going to review the lts paches at some point | 08:59 |
| rajm | ta szlin! | 09:00 |
| szlin | sangorrin: we can discuss it all the time, not just in IRC weekly meeting :D | 09:01 |
| sangorrin | ok | 09:01 |
| *** Tzongyen_Lin has quit IRC | 09:01 | |
| iwamatsu____ | thanks all | 09:01 |
| sangorrin | i was reviewing the changes to modify_ldt, but i have no idea how to test that... | 09:01 |
| sangorrin | i guess i will have to enable kasan and run the test in the commit message | 09:02 |
| patersonc | iwanatsu___: Are you officially the CIP maintainer now? | 09:03 |
| sangorrin | patersonc: not officially | 09:06 |
| sangorrin | btw bootlin rejected our offer | 09:06 |
| patersonc | Oh really? | 09:06 |
| patersonc | Do you know why? | 09:06 |
| sangorrin | no, I guess kobayashi-san will mention it in the next meetign | 09:07 |
| patersonc | Yep. | 09:08 |
| patersonc | iwanatsu___: Do you know anything more about the potential LTS v4.19? | 09:08 |
| patersonc | iwamatsu____ ^^ | 09:09 |
| *** iwamatsu____ has quit IRC | 09:11 | |
| szlin | sangorrin: do you have the commit id? | 09:15 |
| sangorrin | ccd5b32351 upstream | 09:16 |
| sangorrin | oh | 09:17 |
| sangorrin | i found a cve test in ltp that addresses that patch! | 09:17 |
| sangorrin | CVE-2017-17053 | 09:18 |
| szlin | sangorrin: I found that patch is marked as Cc: <stable@vger.kernel.org> [v4.6+] | 09:23 |
| sangorrin | thanks | 09:41 |
| szlin | sangorrin: This patch depends on 39a0526fb3f7d93433d146304278477eb463f8af, which is not in 4.4 | 10:07 |
| sangorrin | I can't check now, but i think it is in 4.4 because the patch that was merged assumes that init_new_context_ldt exists | 10:38 |
| sangorrin | I will check tomorrow | 10:38 |
| *** sangorrin has quit IRC | 10:39 | |
| *** tpollard has quit IRC | 11:02 | |
| * rajm sees that the lucj/kernelci-proxy:latest docker contains today's build but kernelci web i/f is not showing them (also that the docker still contains the builds from July - rather contradicting what I said last week! | 11:06 | |
| *** hungtran has quit IRC | 11:17 | |
| rajm | and now the web i/f does show today's build?! | 12:03 |
| rajm | sangorrin: I replaced a approp line in flask_settings with FILE_SERVER_URL = "http://127.0.0.1:8082/" and kernelci now retrieves the builds - doesn't look like a change from you :) | 12:39 |
| *** rajm has quit IRC | 14:16 | |
| *** rajm has joined #cip | 14:16 | |
| *** patersonc has quit IRC | 14:28 | |
| *** rajm has quit IRC | 14:30 | |
| *** rajm has joined #cip | 14:43 | |
| *** rajm has quit IRC | 15:45 | |
| *** toscalix has quit IRC | 18:01 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!