IRC logs for #cip for Thursday, 2018-08-23

*** darknighte_ has joined #cip02:22
*** darknighte has quit IRC02:29
*** darknighte_ is now known as darknighte02:30
*** yp has joined #cip02:40
*** HoloIRCUser2 has joined #cip06:16
*** HoloIRCUser2 is now known as iwamatsu___06:16
*** iwamatsu___ has quit IRC06:21
*** patersonc has joined #cip07:04
*** iwamatsu_ has joined #cip07:56
*** jki has joined #cip07:59
*** szlin has quit IRC08:00
*** szlin has joined #cip08:01
szlin._./08:01
patersoncMornin08:01
jkihi all, this is Jan08:02
iwamatsu_hi08:02
patersoncHello!08:02
szlin#topic kernel maintenance updates08:03
*** sangorrin has joined #cip08:03
szlinI've sent a patch to 4.4-stable to fix kernel oops issue with brctl tool in CIP kernel08:04
szlinhttps://www.spinics.net/lists/stable/msg252391.html08:04
szlinit's a known issue in current CIP kernel, please see above link and reproducible steps.08:05
sangorrinnice szlin08:06
szlinBesides, I will start to send "overlayfs" patches to 4.4-stable in these days.08:06
sangorrinbrctl tests were added recently to fuego by fujitsu08:06
szlingot it.08:07
sangorrinI will check if i can reproduce the failure and the fixed version this week08:07
sangorrinoverlayfs version 2?08:08
szlinsangorrin: I will backport bugfix patch first08:09
sangorrinok, thanks. How do you reproduce it? is there a test in LTP that raises it?08:10
szlinand next step is to backport features patches (sync, Overlay over overlay, and NFS etc..)08:10
szlinsangorrin: these issues are reported by our QA and customers, I will list the reproducible steps in the description of patch content.08:11
*** hungtran has joined #cip08:12
szlinsangorrin: it's a good point to add (if it's necessary) test case in LTP08:12
sangorrinok, thanks. Was overlayfs and nfs in the list of maintained subsystems?08:12
szlinIIRC, there is a discussion thread related to overlayfs08:14
szlinhttps://lists.cip-project.org/pipermail/cip-dev/2017-June/000284.html08:14
jkibtw, where is that set of subsystems documented ATM?08:14
szlinbwh: are you around?  ^08:15
szlinjki: this is what I have. https://paste.baserock.org/noqafihoqa08:15
szlinbut we still need to ask Ben for it.08:16
jkiI was wondering if we could put that into the wiki, when in doubt with "tbd" tags08:17
sangorrinnice list, where did you get it from? I only remember the discussion thread here: https://lists.cip-project.org/pipermail/cip-dev/2017-July/08:17
jkioh, that list is actually a blacklist. do we also have a whitelist?08:18
jkinevertheless very valuable08:18
szlinjki: IIRC, Ben lists the blacklist instead of white list.08:18
szlinbwh: please correct me if I am wrong.08:19
sangorrinI think that Ben is using the configs that we sent to him and what we discussed in the thread: https://gitlab.com/cip-project/cip-kernel/cip-kernel-config08:19
*** toscalix_ has joined #cip08:21
szlinjki: Do you think we need to list whitelist in wiki?08:21
jkiok, that repo should be linked from the wiki then08:21
szlinany other point?08:22
szlin308:22
szlin208:22
szlin108:22
szlin#topic kernel testing08:22
jkiszlin: next planned cip release (roughly) - maybe that still falls under the previous topic08:23
szlintoscalix_: do you have any update for kernel testing08:24
jkithe gap is increasing, and L1TF is making people nervous08:24
toscalix_szlin: no I don't. Sorry, just joined08:24
szlin#topic AOB08:25
szlinjki: I see there're lots of fixes for kernel 4.4.15008:26
toscalix_o/08:26
sangorrinL1TF is another spectre bug isn't it? I was out in summer ;)08:26
toscalix_summer is not over :-)08:26
jkiyes, it's at least as big as meltdown08:27
szlinjki: from 4.4.148 to 4.4.150, there're many fixes related to L1TF08:27
jkimostly affecting VM setups, but also normal OS configuration08:27
toscalix_my point: where will the new kernel repo be hosted ?08:27
jkitoscalix_: good question...08:27
jkican we get a group on kernel.org?08:28
jkiwould also allow to move the -rt kernel over from daniel account08:28
toscalix_jkl I do not think so. kernel.org I believe are personal accounts08:28
jkibtw, is the mirroring to gitlab.com automatically done?08:29
toscalix_which is why we did not have one in the first place08:29
toscalix_jkl it is automatically done08:29
patersoncThere are some generic accounts on kernel.org, such as next08:29
jkiyes, there are08:29
patersoncIt's work asking at least08:29
patersoncWorst case, could we just use our own GitLab with no mirror?08:30
patersoncs|work|worth08:30
szlinLTSI is using http://git.linuxfoundation.org/?p=ltsi-kernel.git08:30
patersoncThe Xen project have a kernel.org repo: https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/08:31
jkiwe should clarify that soon as the risk is that people may start considering cip kernel dead when there is no update on kernel.org08:31
jkiremove it from there and point to gitlab.com only, or have a group on kernel.org, I would say08:32
szlinjki: perhaps we need to ask Jeff for creating a group on kernel.org?08:34
jkiwho has good contacts to kernel.org and could ask for that?08:35
patersoncMaybe ask GregKH?08:35
jkiszlin: maybe, though there might also be different channels involved for this topic08:35
jkiyes, it might be asked from developer to developer08:36
iwamatsu_and we need GPG keysign with other linux kernel developer.08:36
iwamatsu_if we create group / repository on kernel.org.08:36
jkisure, that applies to the person(s) that will own the group08:36
*** jki has quit IRC08:40
szlinwe can send the request to cip-dev.08:40
*** jki has joined #cip08:41
szlinIMHO, we can ask yoshi - TSC chair to contact Greg for this08:42
szlinDo you have any suggestions?08:42
toscalix_szlin: it is more effective kernel hacker to kernel hacker08:43
jkiI'll also ask Daniel W. later what his suggestion is08:43
sangorrinAnother option is to consult it with Ben, maybe in the next irq meeting...08:43
sangorrinWhat are the disadvantages of having everything in gitlab?08:44
szlin#action Jan will ask Daniel W. for suggestion of creating a group on kernel.org08:44
toscalix_I will ask him08:44
toscalix_should I put CC to cip-dev?08:45
szlin#action Agustín will ask Ben for suggestion of creating a group on kernel.org08:45
szlinyes, please.08:45
szlinany other point?08:45
szlin308:46
szlin208:46
szlin108:46
szlin#endmeeting08:46
szlinthank you all08:46
sangorrin:) thank you!08:46
*** iwamatsu has joined #cip08:47
iwamatsu_thank you08:47
*** sangorrin has left #cip08:48
*** jki has quit IRC08:48
*** jki has joined #cip08:49
*** iwamatsu has quit IRC08:50
*** iwamatsu_ has quit IRC08:51
*** iwamatsu has joined #cip08:51
*** hungtran has quit IRC08:52
*** iwamatsu has quit IRC08:53
*** iwamatsu has joined #cip08:53
*** tpollard has quit IRC09:05
*** CTtpollard has quit IRC09:06
*** tpollard has joined #cip09:09
*** toscalix_ has quit IRC09:12
*** toscalix_ has joined #cip09:13
*** toscalix_ is now known as toscalix09:21
*** toscalix_ has joined #cip09:39
*** toscalix has quit IRC09:39
*** toscalix has joined #cip09:47
*** toscalix has quit IRC09:47
*** toscalix has joined #cip09:47
*** toscalix_ has quit IRC09:48
*** tpollard has quit IRC10:01
*** tpollard has joined #cip10:03
*** toscalix_ has joined #cip11:49
*** toscalix has quit IRC11:49
*** toscalix_ has quit IRC12:10
*** toscalix_ has joined #cip12:11
*** toscalix_ is now known as toscalix12:12
*** toscalix has joined #cip12:12
*** toscalix has joined #cip12:13
*** toscalix_ has joined #cip14:16
*** toscalix has quit IRC14:16
*** toscalix_ has quit IRC14:46
*** toscalix_ has joined #cip14:46
*** toscalix_ is now known as toscalix14:47
*** toscalix has joined #cip14:48
*** ironfoot_ is now known as ironfoot14:53
*** patersonc has quit IRC15:07
*** mungaip has quit IRC16:09
*** tpollard has quit IRC16:49
*** toscalix has quit IRC17:05
*** iwamatsu has quit IRC22:26
*** iwamatsu has joined #cip22:28
*** iwamatsu_ has joined #cip22:36
*** iwamatsu_ has quit IRC22:52
*** iwamatsu has joined #cip22:53
*** iwamatsu has quit IRC22:56
*** iwamatsu has joined #cip22:57
*** iwamatsu has quit IRC23:01

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!