09:00:00 <masashi910> #startmeeting CIP IRC weekly meeting
09:00:00 <brlogger> Meeting started Thu Apr 16 09:00:00 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:00 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:00 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting'
09:00:05 <masashi910> #topic rollcall
09:00:13 <masashi910> please say hi if you're around
09:00:18 <yoshidak[m]> hi
09:00:33 <fujita3> hi
09:00:34 <szlin> hi
09:00:37 <wens> hi
09:00:44 <iwamatsu> hi
09:00:44 <pavel1> hi
09:00:49 <masashi910> #topic AI review
09:00:57 <masashi910> 1. Combine root filesystem with kselftest binary - Iwamatsu-san
09:01:08 <iwamatsu> masashi910: no update
09:01:42 <masashi910> iwamatsu: Noted. Thanks.
09:01:49 <masashi910> 2. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
09:01:58 <masashi910> The current discussion among the kernel team is described in the following document.
09:02:06 <masashi910> https://docs.google.com/document/d/1U4-txCx_uofNH7YXc9LgKILdY-BPgb-nYm3DFrs-9Ns/edit?usp=sharing
09:02:19 <masashi910> Since last week, I added some statistics.
09:02:26 <masashi910> If you have any ideas, please write down to the document.
09:02:31 <masashi910> so, let me move on.
09:02:39 <masashi910> 3. Upload a guideline for reference hardware platform addition - masashi910
09:03:01 <masashi910> Regarding this one, updates can be reported around June timeframe.
09:03:08 <masashi910> so, let me move on.
09:03:13 <masashi910> 4. Identify target boards and configs for RT kernel testing (4.4rt and 4.19rt) - masashi910
09:03:20 <masashi910> I got responses from board owners and compiled the result to make a list.
09:03:53 <masashi910> I will talk with Chris-san later, because he is not joining this call.
09:04:07 <masashi910> 5. Clarify the requirement about sytem-backup - Yoshida-san
09:04:16 <pavel1> board configs...
09:04:37 <pavel1> for realtime. I believe we can use existing
09:04:46 <pavel1> non-rt configs for now.
09:05:11 <pavel1> Eventually we'll get realtime testing to work and can switch.
09:05:20 <pavel1> (that was for ai 4)
09:05:45 <masashi910> pavel1: rt-config is requested by Renesas, Chris-san.
09:06:13 <pavel1> I know. It makes sense to enb
09:06:19 <iwamatsu> we already have rt config in ci--kernel-config.
09:06:20 <iwamatsu> https://gitlab.com/cip-project/cip-kernel/cip-kernel-config
09:06:29 <pavel1> enable when we get rt testing to work.
09:07:34 <masashi910> pavel1: so you prefer to start with non-rt config on RZ/G[12]M as well?
09:08:24 <pavel1> if rt config is available it is better to use it.
09:08:48 <pavel1> but I dont see it as critical at the moment.
09:09:39 <masashi910> pavel1: ok. according to Iwamatsu-san, rt-config is already there. so if there are any issues, let's discuss.
09:09:46 <pavel1> ok.
09:09:55 <masashi910> pavel1: Thanks!
09:09:56 <iwamatsu> i see. I have a RZG1 for testing kernel. I will create rt-config for RZG1
09:10:17 <masashi910> iwamatsu: Thanks!
09:10:48 <masashi910> Yoshida-san, are you around?
09:10:51 <iwamatsu> masashi910: please add this to A.I.
09:11:03 <yoshidak[m]> masashi910: yes
09:11:07 <masashi910> iwamatsu: Sure! thanks again!
09:12:03 <masashi910> yoshidak[m]: do you have update on AI-5: Clarify the requirement about sytem-backup
09:12:36 <yoshidak[m]> I've updated the above docs.
09:13:05 * yoshidak[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/ihOcvquEmyrhfeeJybvoEQbh >
09:13:50 <yoshidak[m]> I'll eventually update the requirement sheet that I've sent, but would it be easier to understand if the bullet points were used like this?
09:14:28 <yoshidak[m]> the above docs means...
09:14:28 <yoshidak[m]> https://docs.google.com/document/d/1U4-txCx_uofNH7YXc9LgKILdY-BPgb-nYm3DFrs-9Ns/edit?usp=sharing
09:15:28 <masashi910> yoshidak[m]: this document is dedicated for the self-maintenance disucssion.
09:15:55 <yoshidak[m]> Oops, sorry.
09:15:55 <masashi910> yoshidak[m]: so, please find a different document for this update.
09:16:45 <masashi910> yoshidak[m]: anyway, thanks for your update.
09:16:54 <yoshidak[m]> OK. I'll reply to the mail. Anyway, those 4 functional requirements are needed to the system backup.
09:16:55 <masashi910> are there any queries?
09:17:44 <masashi910> If there is no query on AI-5, I will close this AI.
09:17:56 <masashi910> 3
09:18:00 <masashi910> 2
09:18:01 <masashi910> 1
09:18:18 <masashi910> #topic Kernel maintenance updates
09:18:44 <pavel1> I have reviewed 4.19.115 and released 4.4-rt.
09:19:04 <iwamatsu> I reviewed 4.4.220-rc.
09:19:31 <pavel1> I looked at 4.19-rt update, but suitable upstream -rt release was not available.
09:19:32 <wens> lots of CVEs last week. some need backports:
09:19:33 <wens> https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec/-/merge_requests/41/diffs#diff-content-688394c3c9d652ef383ebfe583666e47f0588e63
09:19:36 <wens> https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec/-/merge_requests/41/diffs#diff-content-d52debf2c0e92a95325d28279e835af2312f044b
09:19:39 <wens> https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec/-/merge_requests/41/diffs#diff-content-006800cc228ca8b171df6db79db48d27155ba375
09:19:58 <wens> one for btrfs, one for f2fs, four for ext4
09:21:37 <masashi910> wens: thanks very much. I will take a look.
09:22:01 <masashi910> pavel1, iwamatsu: thank you for your updates.
09:22:13 <wens> AFAIK these were found with fuzzer
09:22:13 <masashi910> any other topics?
09:22:43 <masashi910> wens: fuzzer seems to be doing a very good job finding many issues.
09:22:50 <wens> so probably not very critical, unless you have faulty hardware that does bitflips
09:23:13 <masashi910> wens: yes, thanks for this info.
09:23:25 <wens> masashi910: yeah. I suppose code is mostly written with the assumption that hardware does not do funny things
09:24:11 <masashi910> any other topics?
09:24:22 <wens> bwh: thanks for reviewing btw
09:24:51 <masashi910> 3
09:24:55 <masashi910> 2
09:24:58 <masashi910> 1
09:25:03 <masashi910> #topic Kernel testing
09:25:14 <masashi910> Quote from Chris-san "No major updates to report from the testing working group."
09:25:23 <masashi910> any other topics?
09:25:33 <masashi910> 3
09:25:38 <masashi910> 2
09:25:39 <masashi910> 1
09:25:44 <masashi910> #topic CIP Core
09:25:51 <masashi910> == Quote from punit ==
09:26:00 <masashi910> Discussion around projected EOL for CIP core support on cip-dev. Based on the comments in the TSC I will update the proposal to YYYY-MM  format.
09:26:01 <masashi910> Daniel to take over CIP Core activities going forward
09:26:10 <masashi910> ====
09:26:17 <masashi910> any other topics?
09:26:26 <masashi910> 3
09:26:30 <masashi910> 2
09:26:33 <masashi910> 1
09:26:35 <masashi910> #topic Software update
09:26:41 <masashi910> Suzuki-san, the floor is yours
09:27:22 <masashi910> Suzuki-san, are you around?
09:27:54 <masashi910> So, let's move on.
09:28:02 <masashi910> #topic CIP Security
09:28:08 <masashi910> Yoshida-san, the floor is yours
09:28:36 <yoshidak[m]> No major updates to report from the security working group in this week.
09:28:40 <iwamatsu> masashi910: Suzuki-san has take a holiday
09:28:57 <masashi910> iwamatsu: I see. Thanks.
09:29:32 <masashi910> yoshidak[m]: Noted. Thanks.
09:29:43 <masashi910> any other topics?
09:29:49 <masashi910> 3
09:29:52 <masashi910> 2
09:29:54 <masashi910> 1
09:29:57 <masashi910> #topic AOB
09:30:03 <masashi910> Are there any business matters to discuss?
09:30:12 <masashi910> 3
09:30:15 <masashi910> 2
09:30:17 <masashi910> 1
09:30:18 <masashi910> #endmeeting