| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 04:14 | |
| *** toscalix_ <toscalix_!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has joined #cip | 07:33 | |
| *** toscalix_ is now known as toscalix | 08:12 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 08:55 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 09:12 | |
| *** uli <uli!~uli@55d43a3b.access.ecotel.net> has joined #cip | 10:54 | |
| *** toscalix <toscalix!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has quit IRC (Quit: Konversation terminated!) | 10:54 | |
| *** toscalix_ <toscalix_!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has joined #cip | 10:58 | |
| *** alicefm <alicefm!~alicefm@user/alicefm> has quit IRC (Quit: Bridge terminating on SIGTERM) | 11:18 | |
| *** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has quit IRC (Quit: Bridge terminating on SIGTERM) | 11:18 | |
| *** alicefm <alicefm!~alicefm@user/alicefm> has joined #cip | 11:25 | |
| *** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has joined #cip | 11:53 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:56 | |
| *** jki <jki!~jki@195.145.170.149> has joined #cip | 12:00 | |
| jki | Hi all! | 12:00 |
|---|---|---|
| alicef | hi | 12:00 |
| masami | hi | 12:01 |
| uli | hello | 12:01 |
| pave1 | hi! | 12:01 |
| iwamatsu | hi | 12:02 |
| jki | #startmeeting CIP IRC weekly meeting | 12:03 |
| collab-meetbot | Meeting started Thu Oct 13 12:03:17 2022 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:03 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:03 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:03 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| jki | #topic AI review | 12:03 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| jki | 1. Resolve/ignore failures of KernelCI on 4.4-cip - alicefm | 12:03 |
| alicef | no news on this | 12:03 |
| jki | 2. Add qemu-riscv to cip-kernel-config - patersonc | 12:03 |
| patersonc[m] | Hello | 12:04 |
| jki | ah, there you are | 12:04 |
| patersonc[m] | Hello | 12:04 |
| jki | yes, we can read you | 12:05 |
| jki | we are at "Add qemu-riscv to cip-kernel-config - patersonc" | 12:05 |
| patersonc[m] | I started experimenting with qemu-riscv in LAVA, but not defconfig added to cip-kernel-config yet | 12:05 |
| patersonc[m] | martix bridge is being a bit slow for me today | 12:05 |
| alicef | I don't think we need a AI for 1 I will just give updates on the testing meeting part when the kernelci 4.4 issues get updates | 12:05 |
| *** patersonc <patersonc!~patersonc@pc.renesas.eu> has joined #cip | 12:05 | |
| patersonc | I've switched clients. Hopefully this works better. | 12:06 |
| patersonc | w.r.t AI: I started experimenting with qemu-riscv in LAVA, but not defconfig added to cip-kernel-config yet | 12:06 |
| jki | ok | 12:06 |
| jki | regarding 1 then: is kernelci for 4.4-cip now usable for the maintainer? | 12:07 |
| jki | or what do you mean with "we don't need an AI"? | 12:07 |
| alicef | that we can discuss about it on the testing topic part of this meeting when there updates on 4.4-cip | 12:09 |
| jki | ok | 12:09 |
| jki | then move on | 12:09 |
| jki | 3. Report retpoline situation and plans to TSC - jki | 12:10 |
| jki | just to quickly inform you that I reported, asking for feedback, not yet receiving any negative one | 12:10 |
| jki | but also no real "yeah, fully agree" | 12:10 |
| jki | any other AIs? | 12:11 |
| jki | 3 | 12:11 |
| jki | 2 | 12:11 |
| jki | 1 | 12:11 |
| pave1 | I believe | 12:11 |
| pave1 | it will be ok. | 12:11 |
| jki | I do so as well | 12:11 |
| pave1 | OTOH we might want to make it clear | 12:11 |
| pave1 | than not every hw issue can be worked around. | 12:12 |
| jki | how to do that best in your opinion? | 12:12 |
| jki | do we have the related fixes in a 5.10-cip release already? | 12:12 |
| patersonc | Do we list the issues like retpoline that we haven't backported mitigations for? e.g. on the wiki? | 12:13 |
| pave1 | I assume e have it in 5.100, would have to check. | 12:13 |
| jki | wiki would be good place for prominent non-fixes, otherwise our CVE tracker | 12:14 |
| masami | patersonc: I like the idea. | 12:15 |
| pave1 | I'd suggest having a README in the source tree. | 12:15 |
| pave1 | This information may change with the sources, and wiki would answer uestion | 12:16 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 12:16 | |
| pave1 | what is the status in HEAD, but not what was the status in this version. | 12:16 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 12:16 | |
| pave1 | 'README.cip'? | 12:18 |
| iwamatsu | +1 for README in source code. I think reasonable to manage of source code with the source code. | 12:18 |
| patersonc | Agreed. With a link to the readme in the wiki? | 12:18 |
| jki | sounds good to me as well | 12:19 |
| alicef | me too | 12:19 |
| jki | who will start with creating such a README first of all? | 12:19 |
| pave1 | I guess link is easy to do. | 12:19 |
| jki | I would take over the "create the link" task then ;) | 12:19 |
| pave1 | Let me do it for 4.4-st. | 12:20 |
| pave1 | Hmm and let me decide the name, README.cip may not be suitable for 4.4-st. | 12:21 |
| jki | we should find a name that is likely to remain collision-free | 12:21 |
| pave1 | README.st? | 12:22 |
| jki | that is not very telling | 12:22 |
| jki | and would not help for 4.19, would it? | 12:22 |
| pave1 | README.backports? | 12:22 |
| jki | that sounds more like feature backports that bug-fix backports, but maybe only to me | 12:24 |
| jki | do we really need the README in -st as well? in the CIP branches, a README.cip would be well placed and could explain even more | 12:25 |
| pave1 | We can make it KNOWN-BUGS. That will get attention :-). | 12:25 |
| patersonc | It depends - if we _were_ to backport fixes for something like reptoline, would they hit -st? Or only -cip? | 12:25 |
| patersonc | Although I guess the current LTS branches don't list everything they didn't backport from upstream... | 12:26 |
| pave1 | Backports should happen in -st, -cip is for additional features. | 12:26 |
| jki | "UNFIXED-CVEs" :) | 12:27 |
| pave1 | Greg does not do that, true -- but their process is more open and we can do better. | 12:28 |
| pave1 | I'd avoid CVEs. I'd use it for regular bugs, too. | 12:28 |
| pave1 | Like we did not backport /dev/random rewrite. That does not have good CVE to reference. | 12:29 |
| jki | ok, makes sense, but that would clearly limit the file to such a topic - fine with me as well | 12:29 |
| *** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has left #cip (Leaving) | 12:30 | |
| pave1 | ok. | 12:31 |
| * patersonc will be back in 2 mins | 12:31 | |
| jki | ok - anything else on this topic? | 12:32 |
| jki | looks to me like we have a rough plan at least | 12:32 |
| jki | 3 | 12:33 |
| jki | 2 | 12:33 |
| jki | 1 | 12:33 |
| jki | #topic Kernel maintenance updates | 12:33 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:33 | |
| uli | no reviews this week, looked into ldconfig crash on rz/five | 12:34 |
| pave1 | reviewing 5.10.148 and AUTOSEL patches. | 12:34 |
| masami | This week reported 4 new CVEs and 1 updated CVEs. new CVEs are not critical issue. | 12:34 |
| iwamatsu | I did not review for 5.10.y tree. | 12:35 |
| jki | anything else here? | 12:37 |
| jki | 3 | 12:39 |
| jki | 2 | 12:39 |
| jki | 1 | 12:39 |
| jki | #topic Kernel testing | 12:39 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:39 | |
| alicef | no news from me this time | 12:39 |
| patersonc | I've added support to build risc-v in our GitLab CI setup. This MR needs to go through to enable builds: https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/merge_requests/32 | 12:39 |
| patersonc | I've also added GitLab CI support for our -st branch. See patch on cip-dev | 12:40 |
| patersonc | I'm also debugging some remaining issues with our gitlab-runners | 12:40 |
| pave1 | ci support for -st. That would certainly make my life easier. | 12:41 |
| patersonc | risc-v MR is targeting defconfig on 5.10-stable-rc and 5.10-cip. if everyone is happy with that I'll merge | 12:41 |
| patersonc | Or we can hold off until we "officially" support risc-v | 12:42 |
| pave1 | It kind of ''does not belong there' because -st tree is upstream and this is -cip specific... but I guess we can do that. | 12:42 |
| jki | well, what is missing for "official" support? | 12:42 |
| patersonc | pave1: Yea, that's the reason I hesitated with st support | 12:43 |
| iwamatsu | patersonc: I will review it if necessary. | 12:43 |
| patersonc | jki: Nothing for building I guess. Testing needs work | 12:43 |
| jki | ok | 12:44 |
| alicef | we should enable -st also on kernelci | 12:44 |
| patersonc | yea | 12:45 |
| jki | any other testing topics? | 12:46 |
| pave1 | -st on kernelci -- we don't need it till 4.4 is clear of false-positives. | 12:47 |
| pave1 | I don't know how precious their cpu resources are... | 12:47 |
| patersonc | jki: Nope | 12:47 |
| jki | so AI #1 is still valid...` | 12:47 |
| alicef | ? | 12:48 |
| jki | AI 1 is about resolving false-positives for 4.4, at least 4.4-cip, in kernelci | 12:49 |
| alicef | I see ok | 12:50 |
| jki | alicef: can you help moving this forward, or does someone else need to look into that? | 12:51 |
| alicef | I have no problem if someone can help out | 12:52 |
| jki | I can ask Florian again | 12:53 |
| alicef | ok | 12:53 |
| jki | move on? | 12:54 |
| alicef | yes | 12:54 |
| jki | #topic AOB | 12:54 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:54 | |
| jki | I have one topic, more a reminder | 12:54 |
| jki | I already mailed to the maintainers that we need to provide an effort estimate for next year | 12:55 |
| jki | if (likely yes) and how much we need to ramp up the maintenance efforts | 12:55 |
| jki | I need your input here, otherwise there will be no extra budget planned for now | 12:56 |
| jki | rough estimates are fine | 12:57 |
| pave1 | I believe I sent a reply over email. | 12:57 |
| jki | right, but maybe you can also help together with uli to answer the other half | 12:58 |
| uli | i don't really have a good grasp on how much effort 4.4 is in total, i think pave1 needs to answer that | 12:59 |
| jki | please, you two, "sit" together and try to figure this out | 13:00 |
| jki | I can join if it may help :) | 13:00 |
| pave1 | Ok. I'd say it is low compared to the reviews, but it is maybe 4 times more work than doing releases on other branches. | 13:02 |
| jki | 4*x = y | 13:02 |
| pave1 | And we have been lucky so far and only did very little backporting. | 13:02 |
| jki | still two variables ;) | 13:02 |
| *** patersonc10 <patersonc10!~patersonc@pc.renesas.eu> has joined #cip | 13:03 | |
| *** patersonc <patersonc!~patersonc@pc.renesas.eu> has quit IRC (Ping timeout: 268 seconds) | 13:03 | |
| *** patersonc10 <patersonc10!~patersonc@pc.renesas.eu> has quit IRC (Client Quit) | 13:03 | |
| pave1 | Ok so... Id count 2 hours for 5.10-rt release. | 13:03 |
| pave1 | And maybe 2 hours a week for 4.4x maintainence. | 13:04 |
| pave1 | It is more like 16 hours every two months when the release cycle gets quiet. | 13:05 |
| jki | uli: does this help to get a feeling? please share it with me once you got it. with same safety margine for raming up | 13:06 |
| uli | yeah, i think that helps already | 13:07 |
| pave1 | What do we do with 4.4-rt? | 13:07 |
| jki | was for me in the package, to free more time for you - or does it come with different variables? | 13:08 |
| pave1 | Ok works for me. So far I did not have to do any work there as there were no -rt speciic changes in 4.9-rt. | 13:09 |
| pave1 | So that's kind of terra incognita. | 13:09 |
| jki | uli: works for you as well? | 13:11 |
| uli | i think so | 13:12 |
| jki | ok, great | 13:13 |
| jki | anything else for today? | 13:13 |
| jki | 3 | 13:14 |
| jki | 2 | 13:14 |
| jki | 1 | 13:14 |
| jki | #endmeeting | 13:14 |
| collab-meetbot | Meeting ended Thu Oct 13 13:14:35 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:14 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/10/cip.2022-10-13-12.03.html | 13:14 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/10/cip.2022-10-13-12.03.txt | 13:14 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/10/cip.2022-10-13-12.03.log.html | 13:14 |
| *** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"" | 13:14 | |
| alicef | thanks you | 13:14 |
| jki | thank you all, have a nice day/evening/night! | 13:14 |
| iwamatsu | thank you | 13:14 |
| uli | thanks | 13:14 |
| masami | thank you | 13:14 |
| pave1 | thank you! | 13:15 |
| patersonc[m] | Thanks al | 13:17 |
| patersonc[m] | * Thanks all | 13:17 |
| *** jki <jki!~jki@195.145.170.149> has quit IRC (Quit: Leaving) | 13:20 | |
| *** uli <uli!~uli@55d43a3b.access.ecotel.net> has left #cip (Leaving) | 13:46 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 13:56 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 14:10 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 16:04 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 16:13 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 16:22 | |
| *** toscalix_ <toscalix_!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has quit IRC (Quit: Konversation terminated!) | 16:57 | |
| *** toscalix_ <toscalix_!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has joined #cip | 18:58 | |
| *** toscalix_ <toscalix_!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has quit IRC (Client Quit) | 18:58 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 23:42 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!