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