| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:49 | |
| *** Dr_Who <Dr_Who!~tgall@70.35.96.200> has quit IRC (Read error: Connection reset by peer) | 07:24 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Remote host closed the connection) | 08:59 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip | 08:59 | |
| *** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip | 12:57 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:4323:933a:5975:d650> has joined #cip | 12:58 | |
| *** jki <jki!~jki@195.145.170.178> has joined #cip | 12:59 | |
| jki | Hi all! | 13:01 |
|---|---|---|
| masami | hi | 13:01 |
| pave1 | Hi! | 13:01 |
| uli_ | hello | 13:01 |
| iwamatsu__ | hello | 13:01 |
| arisut | hi | 13:01 |
| patersonc | Hello | 13:01 |
| jki | let's go! | 13:05 |
| jki | #startmeeting CIP IRC weekly meeting | 13:05 |
| collab-meetbot` | Meeting started Thu Jan 16 13:05:23 2025 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:05 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:05 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:05 |
| jki | #topic AI review | 13:05 |
| jki | - prepare blog entry on SLTS kernel state and challenges [Jan] | 13:05 |
| *** jki <jki!~jki@195.145.170.178> has quit IRC (Remote host closed the connection) | 13:05 | |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:05 | |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:05 | |
| *** jki <jki!~jki@195.145.170.178> has joined #cip | 13:05 | |
| jki | ping | 13:06 |
| jki | am I online again? | 13:06 |
| pave1 | Yup, we see you. | 13:06 |
| jki | ok, what was last? | 13:06 |
| iwamatsu__ | AI review | 13:06 |
| jki | good, resuming: | 13:06 |
| jki | - prepare blog entry on SLTS kernel state and challenges [Jan] | 13:06 |
| jki | done, finally, post is public | 13:07 |
| jki | I have no other AIs recorded | 13:07 |
| jki | 5 | 13:07 |
| jki | 4 | 13:07 |
| jki | 3 | 13:07 |
| jki | 2 | 13:07 |
| jki | 1 | 13:07 |
| jki | #topic Kernel maintenance updates | 13:07 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:07 | |
| pave1 | I did some reviews, 6.1.120, .125. | 13:07 |
| masami | This week reported 103 new CVEs and 26 updated CVEs. | 13:07 |
| uli_ | i'm reviewing 6.1.125 | 13:07 |
| iwamatsu__ | I reviewed 6.1.123, 124. and reviewing .125. | 13:08 |
| jki | anything else? | 13:09 |
| jki | 5 | 13:09 |
| jki | 4 | 13:09 |
| jki | 3 | 13:10 |
| jki | 2 | 13:10 |
| jki | 1 | 13:10 |
| jki | #topic Kernel release status | 13:10 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:10 | |
| jki | all fine, except for 6.1-rt | 13:10 |
| jki | pavel: any news on that front? | 13:10 |
| pave1 | Yep, I'd really like matching 6.1-rt to proceed. | 13:10 |
| jki | last 6.1-rt was late last year - when might be the next? | 13:11 |
| pave1 | Let me take a look, but it is hard to guess, really. | 13:12 |
| jki | aren't you part of their community and can ask that? | 13:12 |
| pave1 | Yes, I can try to push them. | 13:13 |
| jki | good, thanks | 13:14 |
| jki | anything else regarding releases? | 13:14 |
| jki | 5 | 13:14 |
| jki | 4 | 13:14 |
| jki | 3 | 13:14 |
| jki | 2 | 13:14 |
| jki | 1 | 13:14 |
| jki | #topic Kernel testing | 13:14 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:14 | |
| patersonc | Hey | 13:14 |
| patersonc | I finally got around to looking into the merged x86 configs for SWG | 13:15 |
| patersonc | Got an MR created to start using it | 13:15 |
| patersonc | Do we want to use it instead of the device specific configs? Or in addition? | 13:15 |
| jki | the vision of the merged configs is to have one kernel per arch - if possible | 13:16 |
| patersonc | Okay | 13:16 |
| pave1 | We are catching bugs we would not catch with just one config. | 13:17 |
| pave1 | But I'm not sure benefit is worth the effort. | 13:17 |
| jki | we can't catch them all anyway, too many permutations | 13:17 |
| pave1 | It may be beneficial for -stable-rc testing. | 13:17 |
| patersonc | So keep stable pipelines as-is? And CIP use the merged configs? | 13:18 |
| jki | question is what kernelci could compensate | 13:18 |
| iwamatsu__ | I think it is necessary to listen to the opinions from the company that provides the reference HW. | 13:18 |
| patersonc | True | 13:18 |
| pave1 | Keep them for compile-only testing if that's not too much effort.../ | 13:18 |
| pave1 | ? | 13:18 |
| patersonc | Could do, although the compiling is where most of the cost is | 13:19 |
| pave1 | Each build takes 4 minutes on a server. That should not be that costly... | 13:21 |
| patersonc | Sure | 13:21 |
| pave1 | 0.02kWh :-) | 13:21 |
| jki | ok, do we have plan then? | 13:22 |
| patersonc | just about | 13:23 |
| jki | anything else on testing? | 13:23 |
| patersonc | I did see some boot issues with CIP 4.4 though: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1626448709 | 13:23 |
| patersonc | Specifically https://lava.ciplatform.org/scheduler/job/1238563 and https://lava.ciplatform.org/scheduler/job/1238564 | 13:24 |
| patersonc | All other CIP kernels were okay | 13:25 |
| patersonc | Anyway, can be looked at later | 13:25 |
| arisut | I'm probably going to release kci-dev 0.1.2 this week with the new `kci-dev results` command for getting kernelci information from a local checkout Linux repository | 13:25 |
| jki | missing features in the .config? | 13:25 |
| arisut | currently writing documentation | 13:25 |
| patersonc | Thanks arisut | 13:26 |
| pave1 | https://lava.ciplatform.org/scheduler/job/1238563 -- nfs root mount failure. | 13:26 |
| pave1 | ...but I can't see eth0 in the log, so maybe we need to enable ethernet driver? | 13:27 |
| arisut | This is the new release milestone if anyone is interested | 13:27 |
| patersonc | Actually - we don't support those platforms in 4.4 | 13:27 |
| patersonc | I shouldn't even be testing them | 13:28 |
| patersonc | Ignore me | 13:28 |
| patersonc | Ref: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware | 13:28 |
| pave1 | :-) That's likely easiest. | 13:28 |
| arisut | Also the KernelCI api are still under development | 13:28 |
| jki | arisut: as you may have seen, I stopped image deployment therefore | 13:28 |
| arisut | thanks, I will restart when we have a stable api | 13:29 |
| patersonc | Great | 13:29 |
| jki | more testings topics? | 13:30 |
| patersonc | Not from me | 13:30 |
| jki | 5 | 13:31 |
| jki | 4 | 13:31 |
| jki | 3 | 13:31 |
| jki | 2 | 13:31 |
| jki | 1 | 13:31 |
| jki | #topic AOB | 13:31 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:31 | |
| pave1 | I'll be travelling next week. | 13:32 |
| jki | ok | 13:32 |
| jki | I have one as well: | 13:33 |
| jki | security contact for cip kernels | 13:33 |
| jki | specifically but not only self-maintained ones | 13:33 |
| jki | alternative to security@kernel.org | 13:33 |
| pave1 | Fun :-). | 13:33 |
| jki | any suggestions, opinions etc.? | 13:34 |
| pave1 | Normally people expect secure communication on these with rather high requirements. | 13:34 |
| jki | well, anything is better than no communication channel | 13:35 |
| jki | well, anything but a public channel, obviously | 13:35 |
| jki | can be individual email addresses | 13:35 |
| pave1 | In that case, me, you, uli + iwamatsu? :-) Lets hope it is never used... | 13:35 |
| jki | for isar-cip-core, I've no proposed confidential issues | 13:35 |
| jki | what would the kernel maintainers prefer? | 13:36 |
| jki | and where should we document that? | 13:36 |
| jki | (see SECURITY.md patch for isar-cip-core) | 13:36 |
| pave1 | If we have someone in security team with security set up already, it may be actually best to point initial communication at them. | 13:37 |
| jki | I'm not aware of this, and I don't see this as first option at this stage | 13:37 |
| jki | that person would likely just be the moderator | 13:38 |
| pave1 | Will we want to do GPG for that or not? | 13:39 |
| jki | via email, this would be optimal | 13:39 |
| pave1 | If we are comfortable having an email address but not GPG key, feel free to point that at me. | 13:39 |
| jki | if we go for issue tracking, the mechanisms are different | 13:40 |
| jki | but we can still optmize that - I would like to have something at all first | 13:40 |
| pave1 | So -- alias somewhere at lf for a start? | 13:41 |
| jki | private mailing list on lists.cip-project.org | 13:41 |
| pave1 | That precludes GPG in the future. But yes, would work for a start. | 13:42 |
| jki | does security@kernel.org have a GPG key? | 13:42 |
| jki | not finding anything in Documentation/process/security-bugs.rst | 13:43 |
| jki | if we go for such a list, does the kernel WG want its own, or just security@lists.cip-project.org (covering isar-cip-core e.g. as well)? | 13:44 |
| pave1 | How much traffic do we expect there? | 13:45 |
| pave1 | I guess it will be email a year, so we could just use merged list...? | 13:45 |
| jki | yes, if spam filters continue to work | 13:46 |
| jki | then I would propose that to the TCP and also update my isar-cip-core proposal | 13:46 |
| jki | there, I added me and Kazu as alternative contacts so far | 13:46 |
| jki | anyway, topic for the next TSC as well | 13:46 |
| pave1 | Sounds good. | 13:46 |
| jki | just wanted to gather opinions of kernel WG beforehand | 13:47 |
| pave1 | I was under impression there's expectation of channel with higher security, but it does not seem security@kernel.org is that one. | 13:47 |
| pave1 | Mailing list is good equivalent of security@kernel.org . | 13:48 |
| jki | "This is a private list of security officers | 13:48 |
| jki | who will help verify the bug report and develop and release a fix" | 13:48 |
| jki | writes the kernel | 13:48 |
| jki | ok - other businesses for today? | 13:48 |
| jki | 5 | 13:49 |
| jki | 4 | 13:49 |
| jki | 3 | 13:49 |
| jki | 2 | 13:49 |
| jki | 1 | 13:49 |
| jki | #endmeeting | 13:49 |
| collab-meetbot` | Meeting ended Thu Jan 16 13:49:15 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:49 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/01/cip.2025-01-16-13.05.html | 13:49 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/01/cip.2025-01-16-13.05.txt | 13:49 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/01/cip.2025-01-16-13.05.log.html | 13:49 |
| *** 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 13: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:49 | |
| jki | thanks all! | 13:49 |
| arisut | thx | 13:49 |
| uli_ | thanks | 13:49 |
| pave1 | Thank you! | 13:49 |
| iwamatsu__ | thank you | 13:49 |
| masami | thank you | 13:49 |
| *** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:50 | |
| *** jki <jki!~jki@195.145.170.178> has quit IRC (Remote host closed the connection) | 13:50 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:4323:933a:5975:d650> has quit IRC (Quit: Client closed) | 14:06 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 18:52 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 252 seconds) | 20:12 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!