| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:15 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 07:47 | |
| *** toscalix_ <toscalix_!~toscalix@84.78.245.184> has joined #cip | 08:00 | |
| *** uli <uli!~uli@55d4fd5d.access.ecotel.net> has joined #cip | 10:10 | |
| *** jki <jki!~jki@195.145.170.180> has joined #cip | 11:17 | |
| *** toscalix_ <toscalix_!~toscalix@84.78.245.184> has quit IRC (Quit: Konversation terminated!) | 11:17 | |
| *** toscalix_ <toscalix_!~toscalix@84.78.245.184> has joined #cip | 11:17 | |
| *** toscalix_ <toscalix_!~toscalix@84.78.245.184> has quit IRC (Ping timeout: 252 seconds) | 11:22 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip | 11:24 | |
| *** toscalix_ <toscalix_!~toscalix@84.78.245.184> has joined #cip | 11:26 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 11:32 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:40 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 12:00 | |
| jki | Hi all! | 12:00 |
|---|---|---|
| pave1 | Hi! | 12:00 |
| uli | hello | 12:00 |
| alicef | hi | 12:00 |
| masami | hello | 12:00 |
| jki | well, let's get started | 12:03 |
| jki | #startmeeting CIP IRC weekly meeting | 12:03 |
| collab-meetbot` | Meeting started Thu Jul 28 12:03:14 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 | flo sended a pull request | 12:03 |
| alicef | I did the review and testing process | 12:04 |
| alicef | gtucker will do the final check late today or tomorrow | 12:04 |
| jki | so, the direction makes sense for everyone so far? | 12:05 |
| alicef | the pull request looks filtering correctly the cip 4.4 errors | 12:05 |
| alicef | from the not needed builds | 12:05 |
| jki | ok, good | 12:05 |
| jki | I suppose we need some more PRs after that, right? | 12:06 |
| alicef | we had some error in test results that there wasn't on the previous builds would be nice to check on that | 12:07 |
| jki | pavel: are you aware of that already? | 12:07 |
| alicef | and some warnings from builds | 12:07 |
| pave1 | jki: No, I'm not following that closely. I'll be happy when I see kernelci results with 0 fails :-). | 12:08 |
| pave1 | jki: Plus, we'll likely want same work on 4.19 and 5.10. | 12:08 |
| jki | sure, one after the other I think though | 12:08 |
| pave1 | jki: Yes, one after the other. | 12:08 |
| jki | alicefm: can you point pavel to the new errors/warnings you saw? | 12:09 |
| alicef | we hav this warnings: | 12:10 |
| alicef | 149net/ipv4/inet_hashtables.c:608:68: warning: suggest parentheses around ‘+’ in operand of ‘&’ [-Wparentheses] | 12:10 |
| pave1 | Yep, that one is probably real, I've seen it before and uli pointed it out in the review. | 12:10 |
| alicef | https://gist.github.com/aliceinwire/6fdbe6e4269887f37f986e9771d63793/493c2b455ede3da9cd512fa1ce1cd7c95ac22de4 | 12:10 |
| alicef | 149 builds warnings about that | 12:11 |
| pave1 | Let's talk about that in the testing topic? | 12:11 |
| alicef | sure | 12:12 |
| jki | ok | 12:12 |
| jki | 2. Check cip devices on kernelci old pull request - patersonc | 12:12 |
| jki | no updates here according to chris | 12:12 |
| jki | other AIs? | 12:13 |
| jki | 3 | 12:13 |
| jki | 2 | 12:13 |
| jki | 1 | 12:13 |
| jki | #topic Kernel maintenance updates | 12:14 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:14 | |
| pave1 | I did 5.10.134 reviews, and -rt releases for 4.19 / 5.10. | 12:14 |
| masami | This week reported 5 new CVEs and 5 updated CVEs. no notable new CVEs. | 12:14 |
| uli | i'm backporting patches to 4.4 | 12:14 |
| pave1 | I believe we should do 4.4 release at this point. | 12:14 |
| jki | release before those backports? | 12:15 |
| jki | or after them? | 12:16 |
| uli | they are fixes for xen, not sure if those should hold the release back | 12:16 |
| pave1 | I'd vote for before. Those backports is some kind of Xen CVEs, and there's always more to backport. | 12:16 |
| jki | do we have Xen in support scope btw? | 12:17 |
| pave1 | (But maybe we should start tracking "what do we need to fix in 4.4" with CVE tracking). | 12:17 |
| pave1 | jki: We have XEN enabled in few configs. I'm not sure people are using it... | 12:20 |
| pave1 | qemu_arm64_defconfig:CONFIG_XEN=y | 12:20 |
| pave1 | arm64/renesas_defconfig:CONFIG_XEN=y | 12:20 |
| pave1 | x86/siemens_server_defconfig:CONFIG_NETXEN_NIC=m | 12:20 |
| pave1 | ...etc. | 12:20 |
| jki | but arm64 is not in scope for 4.4 | 12:20 |
| jki | and NETXEN != Xen | 12:22 |
| pave1 | Well, scripts marked it as "used" in 4.9 and I did not investigate further... | 12:23 |
| jki | please don't waste our time on Xen for 4.4 | 12:23 |
| pave1 | I'd need to take a look why scripts say it is enabled. | 12:24 |
| jki | at least from a quick scan of 4.4 configs, i don't see any reason | 12:25 |
| pave1 | Anyway I wish it was disabled in 4.19/5.10 too. If noone cares for 4.4, it is unlikely they care for later kernels. | 12:25 |
| jki | arm64 might be different - but let's bring that up on the list | 12:26 |
| jki | pavel: will you do? | 12:26 |
| pave1 | Ok, will do. | 12:26 |
| jki | thanks | 12:27 |
| jki | anything else kernel maintenance? | 12:27 |
| jki | 3 | 12:29 |
| jki | 2 | 12:29 |
| jki | 1 | 12:29 |
| jki | #topic Kernel testing | 12:29 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:29 | |
| alicef | I made a difference file with old build and new build differences here: | 12:29 |
| alicef | https://gist.github.com/aliceinwire/251b324fee1ce965d51db0b72f5dd011/revisions?diff=unified#diff-a92e01a033c084e6b1364a6737dd4c25de3a2905616d4e97b4b418d4fb67ab9b | 12:30 |
| alicef | in summary the previous build errors looks dissapeared and the new net/ipv4/inet_hashtables.c:608:68: warning: suggest parentheses around ‘+’ in operand of ‘&’ [-Wparentheses] build warning appeared | 12:30 |
| pave1 | Yes, so that's from "tcp: change source port randomizarion at connect() time". | 12:31 |
| pave1 | These are some kinds of tcp privacy fixes. | 12:31 |
| pave1 | WRITE_ONCE(table_perturb[index], READ_ONCE(table_perturb[index]) + (i + 2) & ~1); | 12:31 |
| pave1 | In particular, uli believes it should be "+ ((i + 2) & ~1)" and I'm more inclined to (READ_ONCE() + i + 2) & ~1 :-) | 12:32 |
| pave1 | So... more reviews would not bad. | 12:33 |
| alicef | there is a mail about this ? | 12:33 |
| pave1 | Also, running some kind of tests to ensure TCP still works with these and that the privacy issues are indeed closed would not be bad. | 12:33 |
| jki | doesn't kernelci do sufficient tcp tests for us? | 12:34 |
| pave1 | The mail was "4.4-st20 -- Re: [cip-dev] Failures in 5.10, 4.4 testing". | 12:34 |
| alicef | if the test can be included to kselftest or ltp KernelCI will pickup it | 12:35 |
| alicef | eventually | 12:35 |
| jki | so, there no such tests in any of them yet? | 12:36 |
| jki | or we are not running that yet? | 12:37 |
| alicef | we are not filtering out any test | 12:37 |
| alicef | so we are running everything kernelci have | 12:37 |
| alicef | that's mostly this https://staging.kernelci.org/test/job/cip/branch/linux-4.4.y-cip/kernel/v4.4.302-cip69-517-g92709d8ae585/ | 12:37 |
| alicef | at this time | 12:37 |
| pave1 | For reference, that is issues/CVE-2022-32296.yml and issues/CVE-2022-1012.yml AFAICT. | 12:38 |
| alicef | they are improving new tests frequently | 12:38 |
| alicef | spectre meltdown check script also had a some problems on one of the board https://staging.kernelci.org/test/plan/id/62e1181f97e5190630e19dcb/ and they are some kind of regression from 4.4 cip65 to cip 69 | 12:40 |
| pave1 | I don't see a TCP related test in the list, much less testing TCP privacy issues... | 12:41 |
| alicef | no just talking about 4.4 problems not related with tcp | 12:41 |
| alicef | but still regression | 12:41 |
| alicef | right in the list there is not a tcp related test or tcp privacy | 12:42 |
| alicef | is something probably that shoud be improved | 12:43 |
| alicef | kselftest have such tests ? | 12:43 |
| alicef | or ltp | 12:43 |
| alicef | if yes we can try to enable such test on kernelci | 12:43 |
| pave1 | I'm not familiar with kselftest or ltp. I guess wget in a loop would be basic test of tcp functionality. | 12:44 |
| pave1 | As for +https://staging.kernelci.org/test/plan/id/62e1181f97e5190630e19dcb/ , testing for spectre/meltdown on qemu... is not something I'd consider useful. | 12:45 |
| alicef | I see | 12:45 |
| pave1 | If we wanted to debug this further, standard questions would be "can you bisect it"? | 12:45 |
| alicef | sorry we mixed a bit problems togheter. which one are talking about ? | 12:46 |
| alicef | smc? | 12:47 |
| pave1 | smc. | 12:47 |
| pave1 | But the fact that it detect problems on qemu is kind of a hint that it is test that is broken. | 12:47 |
| alicef | smc test is broken? | 12:48 |
| alicef | smc test is the same used by gitlab only more updated | 12:48 |
| pave1 | Looks like so. It is hard to believe that qemu would have spectre/metdown problem. | 12:48 |
| alicef | https://github.com/speed47/spectre-meltdown-checker | 12:49 |
| jki | any other topics? | 12:51 |
| pave1 | If you are confident there's a problem in kernel, we can try to debug it. But qemu is not a place where I'd expect it to appear. | 12:51 |
| alicef | ok | 12:52 |
| uli | i find that a bit odd. a bug in the cpu emulation is the first thing i would suspect... | 12:52 |
| alicef | let's maybe recheck it after flo patch get merged upstream | 12:52 |
| alicef | and we get the results from kernelci stable | 12:53 |
| jki | ok, move on? | 12:54 |
| jki | 3 | 12:55 |
| jki | 2 | 12:55 |
| jki | 1 | 12:55 |
| jki | #topic AOB | 12:55 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:55 | |
| jki | any topcis for the upcoming eTSC meeting? | 12:55 |
| jki | seems like we are all happy... ;-) | 12:58 |
| pave1 | Happy :-). | 12:58 |
| jki | next CIP kernel and related efforts will likely be a topic again | 12:58 |
| jki | I would also use the chance to ask around for 4.4 usage of our members | 12:59 |
| jki | another call for more contributions to testing... | 12:59 |
| jki | anything else, in general? | 13:01 |
| jki | 3 | 13:01 |
| jki | 2 | 13:01 |
| jki | 1 | 13:01 |
| jki | #endmeeting | 13:01 |
| collab-meetbot` | Meeting ended Thu Jul 28 13:01:34 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:01 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/07/cip.2022-07-28-12.03.html | 13:01 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/07/cip.2022-07-28-12.03.txt | 13:01 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/07/cip.2022-07-28-12.03.log.html | 13:01 |
| *** 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:01 | |
| pave1 | Thank you! | 13:01 |
| uli | thanks | 13:01 |
| jki | thank you all! | 13:01 |
| alicef | thanks | 13:01 |
| masami | thanks | 13:01 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 13:01 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC (Remote host closed the connection) | 13:58 | |
| *** jki <jki!~jki@195.145.170.180> has quit IRC (Remote host closed the connection) | 14:07 | |
| *** uli <uli!~uli@55d4fd5d.access.ecotel.net> has left #cip (Leaving) | 14:25 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 14:34 | |
| *** toscalix <toscalix!~toscalix@90.167.254.146> has joined #cip | 14:50 | |
| *** toscalix_ <toscalix_!~toscalix@84.78.245.184> has quit IRC (Ping timeout: 245 seconds) | 14:53 | |
| *** toscalix_ <toscalix_!~toscalix@84.78.241.81> has joined #cip | 14:53 | |
| *** toscalix <toscalix!~toscalix@90.167.254.146> has quit IRC (Ping timeout: 244 seconds) | 14:56 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 15:25 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 15:28 | |
| *** toscalix_ is now known as toscalix | 15:35 | |
| *** toscalix <toscalix!~toscalix@84.78.241.81> has quit IRC (Quit: Konversation terminated!) | 16:06 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 252 seconds) | 21:44 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!