13:00:06 <alicef> #startmeeting CIP IRC weekly meeting
13:00:06 <brlogger> Meeting started Thu Dec 23 13:00:06 2021 UTC and is due to finish in 60 minutes.  The chair is alicef. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:06 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:06 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting'
13:00:18 <alicef> hello everyone!
13:00:25 <iwamatsu> hi
13:00:50 <patersonc[m]> Hello
13:01:01 <masami> hi
13:04:29 <alicef> ok I think we are everyone
13:04:45 <alicef> let's get started
13:04:54 <alicef> #topic AI review
13:05:05 <alicef> 1. Combine root filesystem with kselftest binary (finishing) - alicef
13:06:01 <alicef> I'm just now re writing the cover letter for the isar-cip-core patch. hope to close this action in this week.
13:06:39 <alicef> 2. Propose tweet on KernelCI-CIP collaboration progress - alicef
13:06:50 <alicef> not worked on this yet
13:07:05 <alicef> patersonc[m]: do you have any suggestion on this topic ?
13:07:38 <patersonc[m]> Was there a specific feature/topic?
13:07:45 <patersonc[m]> I think CIP retweeted KernelCI recently
13:07:55 <alicef> oh nice :)
13:08:28 <alicef> my suggestion was to tweet at least about the domain cip.kernelci.org and kernelci.cip.org
13:08:55 <alicef> and maybe also about the kernelci cip dashboard with the work we are doing
13:09:08 <patersonc[m]> okay
13:09:13 <alicef> https://github.com/orgs/kernelci/projects/11
13:09:22 <patersonc[m]> https://twitter.com/cip_project/status/1458873920329814018
13:09:59 <alicef> :)
13:10:32 <alicef> any other suggestion on this ?
13:10:36 <alicef> 3
13:10:40 <alicef> 2
13:10:57 <alicef> 1
13:11:09 <alicef> 3. Clarify with KernelCI whether CIP maintainers can get accounts - alicef
13:12:49 <alicef> I talked a bit yesterday at the TSC. KernelCI will try to enable it on staging and than depending on the traffic deciding further actions. still not sure about the time schedule that need to take for enabling it.
13:13:59 <alicef> iwamatsu: can you give me the repositories and branches where this need to be enabled ?
13:14:46 <alicef> something like for-kernelci
13:15:29 <iwamatsu> OK, I and Pavel will create.
13:15:54 <alicef> thanks, just send a mail to me with it when you have time :)
13:16:35 <alicef> 3
13:16:40 <alicef> 2
13:16:51 <iwamatsu> o/
13:16:58 <alicef> 1
13:17:07 <alicef> #topic Kernel maintenance updates
13:17:08 <patersonc[m]> I'm sorry guys but I'm going to have to go - the office is shutting early :P
13:17:18 <patersonc[m]> Have a good Christmas etc.
13:17:19 <iwamatsu> we need to decide which gcc to support for each kernel.
13:17:30 <masami> This week reported 12 new CVEs. Some of them aren't fixed yet.
13:17:31 <alicef> patersonc[m]: i see, merry christmas
13:18:00 <iwamatsu> patersonc: Happy holiday and new year.
13:18:19 <masami> patersonc[m]: happy holidays!
13:18:20 <alicef> iwamatsu: oh yes I read the mail about gcc, currently kernelci is using gcc 10 afair
13:19:20 <iwamatsu> 4.19.y and 5.10.y can be matched to cip-core (Debian), but 4.4.y will probably be Debian 8 (Jessie) 's gcc.
13:19:47 <alicef> oh because of debian compatibility, i see
13:20:25 <alicef> what gcc is using cip-core ?
13:21:09 <iwamatsu> maybe current cip-core is using gcc-8
13:21:26 <iwamatsu> this based on debian 10.
13:21:59 <iwamatsu> current developing cip-core is using gcc-10.
13:22:17 <iwamatsu> We are now using one container and gcc from kernel.org, so we need each container.
13:22:51 <iwamatsu> Building this is not that difficult.
13:23:24 <alicef> i see
13:23:25 <iwamatsu> and Debian 8's gcc is gcc-4.9
13:23:46 <alicef> wow
13:25:24 <alicef> so we will freeze a gcc version for each cip version?
13:25:43 <alicef> minor version
13:26:11 <alicef> s/minor/major/
13:26:40 <alicef> like 5.10 will have a gcc version and 4.4 will have a different one
13:26:50 <iwamatsu> probably, yes.
13:27:57 <alicef> maybe just adding revision updates to the freezed gcc version
13:28:16 <alicef> that should not break compability i hope
13:28:40 <alicef> iwamatsu: you will work on this ?
13:29:33 <iwamatsu> I dont have a plan now, but I can do this
13:29:58 <iwamatsu> (maybe I will work with patersonc)
13:30:22 <alicef> sure, thanks :)
13:30:29 <iwamatsu> So, I don't make any conclusions now, but I think it's better to decide at IRC meeting that will be held before the next TSC.
13:30:49 <alicef> right, i agree
13:31:04 <alicef> but still nice to know the current situation, thanks
13:31:16 <alicef> masami: thanks for the report on the CVE
13:31:29 <alicef> anything you want to add ?
13:31:49 <iwamatsu> Perhaps the Jessie-based environment is difficult. This is old so he needs to build a cross environment.....
13:31:54 <masami> alicef: no problems.
13:32:31 <iwamatsu> BTW, I am reviewing 5.10.88.
13:32:59 <alicef> I see, from KernelCI point there should no problem to build with gcc 8 and gcc 10. no idea about gcc-4.9 that's antiquate
13:33:46 <iwamatsu> hehe
13:33:57 <alicef> currently we are building cip 4.4 also with gcc 10. I'm surprised it works
13:34:19 <pav31> hi!
13:34:27 <alicef> pav31: hi
13:34:40 <iwamatsu> hi, Pavel.
13:34:45 <pav31> I was reviewing 5.10.88 and renesas patches.
13:34:46 <masami> hi!
13:34:50 <alicef> we are talking about cip-core using different gcc versions
13:35:06 <pav31> And .... sorry for being late.
13:35:19 <alicef> emh cip kernel been build on different gcc versions
13:35:42 <alicef> pav31: no problem :)
13:36:10 <iwamatsu> some years ago, I created docker file for Jessie cross compile environment.
13:36:17 <iwamatsu> https://github.com/iwamatsu/docker-jessie-cross-toolchain
13:36:34 <pav31> Yes. 5.10.87 or so will break gcc 8 plugins in our config.
13:39:46 <alicef> anything else to add ?
13:40:30 <alicef> pav31: will break gcc_plugins like been forcibly disabled ?
13:41:39 <pav31> I'm not sure I understand.
13:42:02 <pav31> We see broken builds on 5.10.88.
13:42:23 <alicef> oh yes i see
13:42:30 <pav31> Likely we could fix it with changes to config or to build environment.
13:43:26 <iwamatsu> CONFIG_GCC_PLUGINS
13:44:23 <pav31> Yes, that one.
13:44:45 <pav31> Could we simply disable it for now?
13:45:38 <iwamatsu> probably yes. but we need to confirm.
13:46:21 <pav31> Do we have separate configs for cip and stable?
13:47:33 <iwamatsu> current cip-kernel-config's config does not have CONFIG_GCC_PLUGINS.
13:48:07 <alicef> i see, so that is disabled by default ?
13:49:59 <iwamatsu> pav31: some builds use defconfg in kernel.
13:50:30 <pav31> Ay. Aha....
13:51:37 <iwamatsu> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/1911267343
13:52:10 <iwamatsu> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/1911267343#L911
13:52:38 <alicef> we have something to decide here? or can we move on and move back this to the mailing list ?
13:53:09 <iwamatsu> This uses the config of cip-kernel-config, but I'm getting an error.
13:53:10 <iwamatsu> A little resea
13:53:33 <iwamatsu> research is needed.
13:55:04 <pav31> So probably better discussed on the list.
13:55:15 <iwamatsu> +1
13:55:18 <alicef> yes, thanks
13:55:26 <alicef> can we go on ?
13:55:35 <alicef> 3
13:55:38 <alicef> 2
13:55:49 <alicef> 1
13:56:14 <alicef> #topic Kernel testing
13:56:26 <iwamatsu> aha, some config included CONFIG_HAVE_GCC_PLUGINS.
13:56:53 <iwamatsu> This is the cause.
13:57:00 <alicef> oh i see, that could cause the problem even without config_gcc_Plugins
13:58:25 <alicef> about kernel testing we already discussed this. iwamatsu will send me the list of repo and branch that are for development and each commit will be tested by kernelci
13:58:50 <alicef> I have nothing more to add, at now
13:58:56 <alicef> 3
13:59:00 <alicef> 2
13:59:03 <alicef> 1
13:59:10 <alicef> #topic AOB
13:59:20 <alicef> vacations and lockdowns?
13:59:51 <alicef> any vacation schedule ?
14:00:15 <pav31> Heh. Our government decided covid is not dangerous...
14:00:51 <pav31> So likely extended lockdown in january.
14:00:57 <alicef> i see. we will have a meeting also 30 december ?
14:01:04 <iwamatsu> Perhaps Japanese will be on vacation next week and next next week.
14:01:25 <pav31> I believe we decided not to at the last meeting.
14:01:50 <alicef> right, so next meeting will be 6 january
14:02:02 <alicef> 2022!...
14:02:13 <iwamatsu> s/next next/week after next/
14:02:46 <alicef> is ok for 6 january ? or is better to move it later ?
14:03:01 <masami> 6th is ok for me
14:03:03 <pav31> 6 is ok.
14:03:08 <iwamatsu> me too.
14:03:20 <alicef> is ok also for me
14:03:33 <alicef> have a nice new year!
14:04:07 <alicef> and let's close the meeting for today
14:04:12 <alicef> 3
14:04:16 <alicef> 2
14:04:19 <alicef> 1
14:04:37 <alicef> #endmeeting