| *** rajm has joined #cip | 06:55 | |
| *** tpollard has joined #cip | 08:17 | |
| *** pavel1 has joined #cip | 08:49 | |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
|---|---|---|
| brlogger` | Meeting started Thu Aug 6 09:00:01 2020 UTC and is due to finish in 60 minutes. The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:00 |
| brlogger` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| brlogger` | The meeting name has been set to 'cip_irc_weekly_meeting' | 09:00 |
| *** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
| brlogger` | masashi910: Error: Can't start another meeting, one is in progress. Use #endmeeting first. | 09:00 |
| masashi910 | #topic rollcall | 09:00 |
| *** brlogger` changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| szlin | hi | 09:00 |
| masashi910 | please say hi if you're around | 09:00 |
| wens | hi | 09:00 |
| yoshidak[m] | hi | 09:00 |
| iwamatsu | hi | 09:00 |
| pavel1 | hi | 09:00 |
| masashi910 | #topic AI review | 09:00 |
| *** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| dineshk[m] | hi | 09:00 |
| masashi910 | 1. Combine root filesystem with kselftest binary - iwamatsu | 09:00 |
| iwamatsu | masashi910: no update | 09:01 |
| masashi910 | iwamatsu: Noted. | 09:01 |
| masashi910 | 2. Post LTP results to KernelCI - patersonc | 09:01 |
| masashi910 | patersonc: are you around? | 09:01 |
| masashi910 | Let's revisit if he joins. | 09:02 |
| patersonc | Hi sorry | 09:02 |
| patersonc | No updated :) | 09:02 |
| masashi910 | patersonc: Hi | 09:02 |
| *** hungtran has joined #cip | 09:02 | |
| masashi910 | patersonc: Noted. | 09:02 |
| masashi910 | Then, let's move to next. | 09:02 |
| masashi910 | #topic Kernel maintenance updates | 09:03 |
| *** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:03 | |
| wens | Fix for CVE-2020-14331 from last week is in linux-next, but not in Linus's tree. | 09:03 |
| pavel1 | I have reviewed patches for 4.19.136 and 137. | 09:03 |
| wens | New issues this week: CVE-2020-0255 (fixed), CVE-2020-16166 (fixed) | 09:03 |
| iwamatsu | I reviewed 4.4.233-rc. | 09:03 |
| masashi910 | wens: So, this week, there are no pending CVEs. Is it correct? | 09:05 |
| wens | correct. | 09:05 |
| masashi910 | wens: Thanks for your confirmation. | 09:05 |
| wens | for an old CVE, Debian reports that the fix was not completely backported to 4.19 | 09:05 |
| wens | CVE-2019-3874 | 09:06 |
| wens | this is DoS due to SCTP usage, classified as minor issue. | 09:06 |
| wens | that's all | 09:07 |
| masashi910 | wens: according to cip-kernel-sec, CVE-2019-3874 has two rows. One is ignored and one is fixed. | 09:08 |
| masashi910 | Do you mean the fixed one? 9a84bb13816f | 09:09 |
| iwamatsu | https://security-tracker.debian.org/tracker/CVE-2019-3874 | 09:09 |
| wens | looks like they are ignoring the issue as well. | 09:10 |
| masashi910 | Not two rows, but one row says "fixed by 9a84bb13816f" | 09:10 |
| masashi910 | Anyway, thanks for your report. | 09:10 |
| masashi910 | wens, pavel1, iwamatsu: Thanks for your works. | 09:11 |
| wens | 4.19 is missing 9dde27de3e5efa0d032f3c891a0ca833a0d31911 , the other half of the fix | 09:11 |
| masashi910 | wens: I see. Thanks for your explanation. | 09:11 |
| masashi910 | Any other topics? | 09:12 |
| wens | nope | 09:12 |
| masashi910 | Ok, then let's move on. | 09:12 |
| masashi910 | #topic Kernel testing | 09:12 |
| *** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:13 | |
| masashi910 | patersonc: the floor is yours. | 09:13 |
| masashi910 | patersonc: are you there? | 09:14 |
| patersonc | hi | 09:14 |
| patersonc | sorry | 09:14 |
| masashi910 | Let's revisit when he comes back. | 09:14 |
| patersonc | I've set up a specific lava master for the security working group to test/investigate multi-node support. Login details have been shared with Venkata. | 09:15 |
| patersonc | I've conencted a lava lab running at home to this master, with 2x qemu and 1x g2m board. | 09:15 |
| patersonc | I'll try and find time to activly try multi-node as well | 09:15 |
| patersonc | I think that's it from me this week | 09:15 |
| masashi910 | patersonc: Does KernelCI run LTP with CIP kernel now, or still in progress? | 09:16 |
| patersonc | I've submitted for them to boot test CIP Kernels | 09:16 |
| patersonc | But KCI doesn't support LTP yet | 09:17 |
| masashi910 | patersonc: I see. Thanks for your updates. | 09:17 |
| masashi910 | any other topics? | 09:17 |
| masashi910 | 3 | 09:17 |
| masashi910 | 2 | 09:17 |
| masashi910 | 1 | 09:18 |
| masashi910 | #topic Software update | 09:18 |
| *** brlogger` changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:18 | |
| masashi910 | Quote from Suzuki-san "SW Updates WG don't have any updates this week." | 09:18 |
| masashi910 | Let's move on. | 09:18 |
| masashi910 | #topic CIP Security | 09:18 |
| *** brlogger` changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)" | 09:18 | |
| yoshidak[m] | no major update this week, and we are trying to draft documents for the assessment w/ Exida. | 09:19 |
| masashi910 | Yoshida-san or Dinesh-san, any updates? | 09:19 |
| yoshidak[m] | That's is from me this week. Thanks. | 09:19 |
| dineshk[m] | OK plz wait | 09:19 |
| dineshk[m] | Investigation of IEC-62443-4-1 is completed | 09:19 |
| dineshk[m] | Investigation report of IEC-62443-4-1 is shared for exida review | 09:19 |
| dineshk[m] | Debugging of multi-node LAVA test failure is in progress | 09:20 |
| dineshk[m] | Verification of security packages in CIP tiny profile is in progress | 09:20 |
| dineshk[m] | Next IEC-62443-4-x gap assessment meeting with exida is planned on 24/Aug | 09:20 |
| dineshk[m] | These are some minor updates this week | 09:20 |
| masashi910 | yoshidak[m], dinesh[m]: Thanks for your updates. | 09:20 |
| masashi910 | Any queries? | 09:21 |
| masashi910 | 3 | 09:21 |
| masashi910 | 2 | 09:21 |
| masashi910 | 1 | 09:21 |
| masashi910 | #topic AOB | 09:21 |
| *** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:21 | |
| masashi910 | I have one query to IRC meeting members. | 09:21 |
| masashi910 | Next week is so called OBON in Japan and most Japanese people will be off. | 09:21 |
| masashi910 | Can we skip next IRC meeting? Any objections? | 09:21 |
| dineshk[m] | No objection from me | 09:22 |
| yoshidak[m] | no objection | 09:22 |
| pavel1 | I'd like to talk with Patersonc after the meeting. | 09:22 |
| pavel1 | No objections. | 09:22 |
| wens | No objection | 09:22 |
| masashi910 | Thanks. Then, the next meeting will be skipped. | 09:22 |
| masashi910 | Any other topics? | 09:22 |
| masashi910 | 3 | 09:23 |
| masashi910 | 2 | 09:23 |
| masashi910 | 1 | 09:23 |
| masashi910 | #endmeeting | 09:23 |
| brlogger` | Meeting ended Thu Aug 6 09:23:17 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:23 |
| brlogger` | Minutes: https://irclogs.baserock.org/meetings/cip/2020/08/cip.2020-08-06-09.00.html | 09:23 |
| brlogger` | Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/08/cip.2020-08-06-09.00.txt | 09:23 |
| brlogger` | Log: https://irclogs.baserock.org/meetings/cip/2020/08/cip.2020-08-06-09.00.log.html | 09:23 |
| *** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:23 | |
| masashi910 | Thanks! | 09:23 |
| patersonc | masashi910: Have a nice week off next week | 09:23 |
| iwamatsu | thanks | 09:23 |
| pavel1 | Thanks! | 09:23 |
| masashi910 | patersonc: Thanks! :) | 09:23 |
| pavel1 | patersonc -- do you have few minutes? | 09:23 |
| patersonc | pavel1: Sure | 09:24 |
| pavel1 | About kernel testing. | 09:24 |
| pavel1 | gitlab misses yellow mark. | 09:24 |
| patersonc | yea | 09:24 |
| pavel1 | Would it be possible to split kernel test into two steps? | 09:24 |
| pavel1 | 1) board boots and we get an uboot propmt | 09:25 |
| pavel1 | prompt | 09:25 |
| pavel1 | 2) actual kernel test. | 09:25 |
| pavel1 | If 1) fails, I know I'm not the one working on u-boot, so | 09:25 |
| pavel1 | can ignore the result rather easily....? | 09:26 |
| patersonc | Maybe, but a lot of the time tests fail due to infrastucture problems. This random. So it could fail for the u-boot case and not the Kernel test, or visa-versa | 09:26 |
| pavel1 | If we put the line at the right place, it should work... | 09:28 |
| pavel1 | If the u-boot loaded kernel/initrd/etc... then any failure is "real". | 09:28 |
| patersonc | So you're saying to have 2 test jobs. One just boots to u-boot, the second runs the Kernel. | 09:29 |
| pavel1 | For truly random failures, that will be harder. | 09:29 |
| pavel1 | patersonc -- yes. | 09:30 |
| patersonc | The first one could pass fine. But the second one could still fail before it hits u-boot, so you'd still have to check to see when the error occured | 09:30 |
| pavel1 | basically instead of yellow mark, have two marks. | 09:30 |
| pavel1 | One indicates testing infrastructure works, one indicates kernel under the test work. | 09:31 |
| patersonc | Also, the u-boot test could fail, but the Kernel test could pass? | 09:31 |
| patersonc | The problem is, just because the infrastructure worked for the first test case, it isn't guarenteed it would work for the second | 09:31 |
| pavel1 | I don't think so. If u-boot did not work, we can't really boot kernel. | 09:32 |
| patersonc | Especially given that the test jobs will more then likely be run at the same time on two seperate boards in two seperate labs | 09:32 |
| patersonc | The failure is never u-boot though - it doesn't change. It's usually because serial has stopped working on the board, or the internet connection at the lab fails | 09:32 |
| pavel1 | ok. if gitlab added yellow marks, would that be solution? | 09:32 |
| pavel1 | I propose using two green marks for everything working, one red mark instead of yellow, and other red mark instead of red... | 09:33 |
| patersonc | It would help in the case where tests weren't run because there were no boards available | 09:34 |
| patersonc | When we're integrated with KernelCI you'll be able to have a much better method to view the results | 09:34 |
| patersonc | KCI will also pick out test regressions etc. | 09:34 |
| pavel1 | well -- I believe it still works. if serial connection failed, you can't talk to uboot, so uboot will be marked failed, and I'll know it is not a real kernel problem... | 09:35 |
| patersonc | For example, if a test job runs okay at the moment we get a green tick. But the actual test case could have failed, e.g. the cyclictest latency could be huge. | 09:35 |
| patersonc | The specific test results aren't shown in GitLab at the moment | 09:35 |
| pavel1 | aha... well, it is still quite useful as lot of kernel problems will mean it crashes. | 09:36 |
| pavel1 | so yes, better presentation would be nice. | 09:36 |
| patersonc | yep | 09:40 |
| patersonc | It's nowhere near great atm ;) | 09:40 |
| patersonc | KCI should also pick up on dmseg errors etc as well which will be useful | 09:40 |
| patersonc | pavel1: Do you check the cyclicbenchmark times etc. at the moment? | 09:40 |
| *** pavel1 has quit IRC | 09:41 | |
| *** pavelm2 has joined #cip | 09:41 | |
| *** pavelm2 has quit IRC | 09:46 | |
| *** venkatap1 has joined #cip | 09:54 | |
| *** hungtran has quit IRC | 11:15 | |
| *** tpollard has quit IRC | 12:42 | |
| *** tpollard has joined #cip | 12:42 | |
| *** venkatap1 has left #cip | 13:51 | |
| *** tpollard has quit IRC | 17:06 | |
| *** rajm has quit IRC | 22:07 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!