| *** hiromotai <hiromotai!~Thunderbi@KD124209157205.ppp-bb.dion.ne.jp> has joined #cip | 04:02 | |
| *** frieder <frieder!~frieder@i4DF67AE6.pool.tripleplugandplay.com> has joined #cip | 06:52 | |
| *** hiromotai <hiromotai!~Thunderbi@KD124209157205.ppp-bb.dion.ne.jp> has quit IRC (Quit: hiromotai) | 08:34 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has quit IRC (Quit: Konversation terminated!) | 11:11 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has joined #cip | 11:11 | |
| *** fbezdeka <fbezdeka!~flo@p200300cfc73709fc4f9250931d16037a.dip0.t-ipconnect.de> has joined #cip | 11:34 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 12:15 | |
| *** jki <jki!~jki@195.145.170.148> has joined #cip | 12:59 | |
| jki | hi, everyone! | 13:00 |
|---|---|---|
| *** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has joined #cip | 13:00 | |
| uli | hello | 13:00 |
| masami | hi | 13:00 |
| pave1 | Hi! | 13:01 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e310:9694:6a97:c2a3> has joined #cip | 13:02 | |
| iwamatsu__ | hello | 13:02 |
| jki | ok, time to start | 13:02 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot | Meeting started Thu Aug 22 13:02:33 2024 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:02 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:02 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:02 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | #topic AI review | 13:02 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | - prepare blog entry on SLTS kernel state and challenges [Jan] | 13:02 |
| jki | unfortunately still no news | 13:02 |
| jki | - look into CVE triage tool [iwamatsu-san] | 13:02 |
| iwamatsu__ | I have used this tool. | 13:03 |
| iwamatsu__ | This is a tool to identify the CVEs involved in a given kernel config. | 13:03 |
| jki | yes, or to rule CVEs out based on a config | 13:03 |
| iwamatsu__ | I think this is a good tool to determine which CVEs are related to our kernel configurations. However, it takes a long time to process and this needs to be improved. In my environment, it took about 25 minutes per run. | 13:03 |
| iwamatsu__ | The time can be reduced by having the program support parallel processing. | 13:04 |
| jki | I suppose there are ways to optmize its runtime | 13:05 |
| jki | did you also check the accuracy, at least for some examples? | 13:05 |
| iwamatsu__ | Yes, I have also checked some for accuracy. I have only checked three kernel versions, but so far I have not found any problems. | 13:06 |
| iwamatsu__ | And Since the results are output in JSON, the information can be filtered by processing the JSON. Currently, report-overview.py is provided as a simple tool for this. | 13:07 |
| iwamatsu__ | At this time, it is necessary to look at the JSON to see which CVEs have been fixed, so report-overview.py and others need to be improved. | 13:07 |
| jki | makes sense | 13:08 |
| jki | but this sounds to me like we should continue to drive this, improve useability and eventually actually hook it into our workflow, right? | 13:09 |
| iwamatsu__ | Yes, I agree. | 13:10 |
| jki | perfect, already informed Christoph :) | 13:10 |
| jki | then next item | 13:11 |
| jki | - clarify role of linux-6.1.y-cip-rebase tag [iwamatsu-san] | 13:11 |
| jki | was this resolved? | 13:11 |
| pave1 | Reference would be | 13:12 |
| pave1 | Date: Tue, 13 Aug 2024 17:47:59 +0200 | 13:12 |
| pave1 | Subject: Re: [cip-dev] [ANNOUNCE] v6.1.102-cip26 | 13:12 |
| pave1 | https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/tag/?h=linux-6.1.y-cip-rebase | 13:12 |
| pave1 | This is _tag_ linux-6.1.y-cip-rebase. We also have a branch | 13:12 |
| pave1 | linux-6.1.y-cip-rebase. IMO the tag is a mistake. | 13:12 |
| jki | iwamatsu__:? | 13:13 |
| iwamatsu__ | I am aware of this problem and try to erase it from the repository in my scripts every time. But I will check again. | 13:14 |
| jki | so, this tag is re-created by a release script? | 13:14 |
| iwamatsu__ | No, I don't think it was created by my script.... | 13:16 |
| iwamatsu__ | But I will recheck . | 13:16 |
| jki | ok, thanks | 13:16 |
| jki | would be good to understand if this is recurring | 13:16 |
| *** csteiger <csteiger!~csteiger@dslb-092-072-048-047.092.072.pools.vodafone-ip.de> has joined #cip | 13:16 | |
| jki | other AIs I don't have, so... | 13:17 |
| jki | 5 | 13:17 |
| jki | 4 | 13:17 |
| jki | 3 | 13:17 |
| jki | 2 | 13:17 |
| jki | 1 | 13:17 |
| jki | #topic Kernel maintenance updates | 13:17 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:17 | |
| masami | This week reported 187 new CVEs and 11 updated CVEs. | 13:17 |
| uli | been reviewing 6.1.103 | 13:17 |
| pave1 | I'm doing reviews, 6.1.103, .106 and AUTOSEL. | 13:17 |
| iwamatsu__ | I reviewed 6.1.106. | 13:18 |
| jki | anything else? | 13:19 |
| jki | 5 | 13:20 |
| jki | 4 | 13:20 |
| jki | 3 | 13:20 |
| jki | 2 | 13:20 |
| jki | 1 | 13:20 |
| jki | #topic Kernel release status | 13:20 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:20 | |
| jki | all green this time :) | 13:20 |
| arisut | nice | 13:20 |
| jki | any issues ahead? | 13:20 |
| arisut | kci-dev as became an official kernelci project | 13:20 |
| arisut | but no updates on terms of functionality | 13:21 |
| jki | you are already at "testing" :) | 13:21 |
| jki | so | 13:21 |
| jki | #topic Kernel testing | 13:21 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:21 | |
| arisut | sorry | 13:21 |
| pave1 | Sep 9th should see 3 -rt releases in 3 days. But no problem foreseen. | 13:21 |
| arisut | thanks | 13:21 |
| jki | arisut: congrats for the project promotion | 13:22 |
| arisut | jki, thanks :) | 13:22 |
| jki | now just finish it ;) | 13:22 |
| arisut | right :) | 13:22 |
| jki | we had some issues with the qemu runner in the siemens-lab, should be resolved now | 13:23 |
| arisut | thaks for fixing it | 13:23 |
| jki | seems it got quite some attention - unluckily | 13:23 |
| pave1 | It would be nice to monitor dmesg for any backtraces, | 13:23 |
| pave1 | in case it returns, | 13:24 |
| pave1 | or if similar issue should appear. | 13:24 |
| jki | should be possible, we did that in some other setup, but don't ask me for the details | 13:24 |
| jki | anything else on testing? | 13:26 |
| fbezdeka | The problem was on the host this time, quite hard to automatically monitor that from the test infrastructure / LAVA | 13:26 |
| arisut | why not using lava-docker ? | 13:27 |
| fbezdeka | how would that help in case the host has a problem? | 13:27 |
| jki | we are using that, but that does not protect you from hw issues of your host | 13:27 |
| arisut | having lava on docker should make errors better reproducibility | 13:28 |
| jki | despite rumors, you still need real hardware somewhere to run containers ;) | 13:28 |
| arisut | sure hw issue are a different beast | 13:28 |
| arisut | :D | 13:28 |
| arisut | despite rumors lol | 13:28 |
| jki | but are we catching kernel warnings of the target in lava already, or not? | 13:29 |
| jki | is kernelci filtering them out? I would expect that | 13:32 |
| arisut | you mean host errors? | 13:32 |
| arisut | or board errors? | 13:33 |
| jki | board errors | 13:33 |
| arisut | yes they are filtered with the testing system | 13:34 |
| jki | ok, good | 13:35 |
| arisut | mostly depends on which tests are executed | 13:35 |
| arisut | or allowed to be executed | 13:35 |
| jki | well, they should always be filtered and reported - unless the test case is to test WARN_ON | 13:35 |
| arisut | yes they should be reported | 13:36 |
| jki | good, then move on... | 13:36 |
| jki | 5 | 13:36 |
| jki | 4 | 13:37 |
| jki | 3 | 13:37 |
| jki | 2 | 13:37 |
| jki | 1 | 13:37 |
| jki | #topic AOB | 13:37 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:37 | |
| jki | anything else for today? | 13:37 |
| csteiger | I have some questions about the triage tool | 13:38 |
| csteiger | First of all thank you for checking it out :) | 13:38 |
| csteiger | What would you like to have in the overview tool? Which CVE the tool deemed relevant? | 13:38 |
| jki | iwamatsu__:? | 13:40 |
| iwamatsu__ | I would be happy to see a list of the CVEs involved and the status of the CVEs and commit ID. | 13:41 |
| csteiger | That can be done | 13:41 |
| jki | cool | 13:42 |
| iwamatsu__ | nice | 13:42 |
| csteiger | About the performance: did you cache the kmax formulas for each kernel version? | 13:43 |
| csteiger | Generating them takes about 5 to 10 minutes on my machine | 13:43 |
| csteiger | The checks can be parallelized too I think, which should give us some improvements too | 13:44 |
| iwamatsu__ | I create them every time. I do not use cache. I understand that using a cache can be mitigating. | 13:45 |
| jki | will those 15-25 min. run be per CVE? | 13:46 |
| iwamatsu__ | per a kernel config. | 13:47 |
| csteiger | No, once the kmax formulas are there, which only has to be done once for each kernel version, it takes about 10 seconds per CVE | 13:47 |
| csteiger | or shorter, when we do not need to run all checks | 13:47 |
| jki | ok, that is better | 13:47 |
| jki | anything else? | 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 Aug 22 13:49:30 2024 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/2024/08/cip.2024-08-22-13.02.html | 13:49 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/08/cip.2024-08-22-13.02.txt | 13:49 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/08/cip.2024-08-22-13.02.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 | thank you, see you next time! | 13:49 |
| pave1 | Thank you! | 13:49 |
| iwamatsu__ | Thank you. | 13:49 |
| masami | thank you | 13:49 |
| csteiger | Bye! | 13:49 |
| *** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:50 | |
| uli | thanks | 13:50 |
| arisut | thanks | 13:50 |
| *** csteiger <csteiger!~csteiger@dslb-092-072-048-047.092.072.pools.vodafone-ip.de> has left #cip (Leaving) | 13:50 | |
| *** jki <jki!~jki@195.145.170.148> has quit IRC (Quit: Leaving) | 13:53 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has quit IRC (Quit: Konversation terminated!) | 14:03 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e310:9694:6a97:c2a3> has quit IRC (Ping timeout: 256 seconds) | 14:54 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has joined #cip | 15:04 | |
| *** frieder <frieder!~frieder@i4DF67AE6.pool.tripleplugandplay.com> has quit IRC (Remote host closed the connection) | 15:13 | |
| *** fbezdeka <fbezdeka!~flo@p200300cfc73709fc4f9250931d16037a.dip0.t-ipconnect.de> has left #cip | 17:25 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 19:11 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!