IRC logs for #cip for Thursday, 2021-04-22

*** rajm has joined #cip06:27
*** samwilson has joined #cip07:22
*** masashi910 has joined #cip07:48
*** tpollard has joined #cip08:07
*** samwilson has quit IRC08:20
*** samwilson has joined #cip08:29
*** eduardas has joined #cip08:46
masashi910#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Apr 22 09:00:01 2021 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brloggerThe 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#topic rollcall09:00
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910please say hi if you're around09:00
wenshi09:00
patersonchi09:00
*** pave11 has joined #cip09:00
pave11hi09:00
masashi910Let's get started.09:00
masashi910#topic AI review09:00
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:00
masashi9101. Combine root filesystem with kselftest binary - iwamatsu09:01
masashi910== Quote from iwamatsu  ==09:01
masashi910It is progressing little by little. This is discussed on ML and gitlab.09:01
masashi910Simple operation has been tested and I have confirmed that it works with QEMU.09:01
masashi910====09:01
masashi9102. Do some experiment to lower burdens on CI - patersonc09:01
patersoncNo updates :)09:01
masashi910patersonc: Sure. Thanks.09:01
masashi9103. Monitor the status of CVE-2021-3444 and CVE-2021-20292 (3/25) - Kernel Team09:02
masashi9104. Monitor the status of CVE-2021-29650 (4/1) - Kernel Team09:02
wensNo updates for the first two.09:02
wensAs mentioned in this week's report, pave11's backport fix for CVE-2021-29650 didn't hit the stable ML09:02
pave11wens: Ok, I'll make a note to resend and cc you this time.09:03
wensGuenter Rock did a separate backport, but there were some issues and the series has been put on hold # https://lore.kernel.org/stable/1780f159-140b-231f-8af5-ccec049dc8b0@roeck-us.net/09:03
wenspave11: I think you used the wrong address for stable? I did get the patch you sent out last week after the meeting, but it's not on the list.09:04
pave11wens: I'll need to take a look... and also review the on-list discussion.09:05
wensOK.09:05
masashi910wens, pavel1: Thanks. So, for the moment, I will keep both AIs open.09:06
masashi9105. Update Testing table below with 5.10 info - patersonc09:06
masashi910https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/centalisedtesting/cioverview09:06
patersoncI haven't done this yet09:06
masashi910patersonc: Ok, I will keep this open.09:07
masashi910any other topics?09:07
masashi910309:07
masashi910209:07
masashi910109:07
masashi910#topic Kernel maintenance updates09:07
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:07
masashi910== Quote from iwamatsu  ==09:07
masashi910I reviewed 4.9.267 and 5.10.32.09:07
masashi910====09:08
wensThis week's report: https://lore.kernel.org/cip-dev/CAGb2v662tfa68d6areLEJV=RA3Gwn751-uT7t99uvRe3PN6KKg@mail.gmail.com/09:08
pave11I have reviewed patches queued for 5.10.32 & corresponding 4.19 queue.09:08
wensSeven CVEs this week: 3 ignored, 3 fixed, of them 1 needs backporting (CVE-2021-23133 [net/sctp: race in sctp_destroy_sock]), and last one has fixed queued for -next.09:09
wensalso for CVE-2021-29155, of all the fix commits, only 1 has a fixes tag.09:10
masashi910wens, pave11: Thanks for your works.09:11
wensseems CVE-2021-29155 only affects v5.8+09:12
wensthough I am not 100% certain09:12
masashi910Do we need time to check it?09:12
pave11wens: If you could push cip-kernel-sec changes, it would be easier to look the information up.09:12
wenspave11: right, now pushed09:13
pave11wens: Thank yoU!09:13
masashi910wens, pave11: For now, should both CVE-2021-23133 and CVE-2021-29155 be monitored?09:15
wensCVE-2021-29155 is bpf related, probably not worth the effort09:16
masashi910wens: Ok, thanks for your comment.09:16
wensand CVE-2021-23133 is SCTP related. Not sure who uses SCTP for what, but IIRC it's pretty niche.09:17
pave11Agreed about bpf.09:17
pave11We should really make sure untrusted users are not using BPF on our boxes.09:18
pave11SCTP seems to be enabled by at least ./4.19.y-cip/x86/plathome_obsvx2.config09:18
pave11Which does not mean they are using it...09:18
masashi910wens, pave11: Thanks for your comments. I will ask Minda-san@PlatHome about SCTP.09:19
pave11masashi910: It is in Siemens configurations, too.09:20
masashi910pave11: Then, I will ask Jan-san as well. Thanks!09:20
pave11Thank you!09:21
masashi910Any other topics?09:21
masashi910309:21
wensso before v5.8, bpf needed CAP_SYS_ADMIN, or root privs.. After v5.8, it changed to CAP_BPF, allowing non-root users to run bpf.09:21
masashi910wens: I see. Thanks for this background.09:22
wensI think that means we can ignore CVE-2021-29155. If the user is root they already can look at kernel memory.09:22
pave11wens: I'd say so.09:22
wens:)09:23
masashi910wens, pave11: So, we decided to ignore CVE-2021-29155. Thanks.09:23
masashi910209:23
masashi910109:23
masashi910#topic Kernel testing09:23
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:23
masashi910patersonc: The floor is yours.09:24
patersoncSorry I had a Q for the Kernel team09:24
patersoncDo we need to do anything with regards to the UMN reverts? (https://lwn.net/SubscriberLink/853717/333c1087131ab995/) Have any of the patches made it into CIP? Or do we just depend on stable reverting the relevant patches?09:24
pave11patersonc: We need to revert everything from Greg :-).09:25
patersoncha :P09:25
pave11He's wrong here.09:25
pave11Let me dig an explanation.09:25
pave1100~https://lore.kernel.org/lkml/20210422083850.GA5316@amd/01~09:26
pave11https://lore.kernel.org/lkml/20210422083850.GA5316@amd/0109:26
masashi910patersonc: BTW, revert patches are arriving:09:27
masashi910https://lore.kernel.org/stable/YIEVGXEoeizx6O1p@debian/T/#t09:27
masashi910patersonc: BTW do you have any updates?09:28
patersoncFrom the emails I've seen, a lot of the UDM patches do actually seem to fix issues09:28
pave11patersonc: Please speak up when you see that.09:28
patersoncI don't have anything particular to add, it's just a surprising story I just started reading on09:28
pave11patersonc: Because Greg is pushing revert without without proper review.09:29
pave11If that actually hits the stable, we may want to avoid those stable kernels for a while.09:29
pave11And yes, it is a big story.09:29
patersoncpave11: positive commits example: https://www.spinics.net/lists/kernel/msg3914800.html09:30
pave11UMN are not the bad guyes, see the email for explanation.09:31
masashi910patersonc, pave11: Thanks. If we need to discuss this issue, let's do that after the IRC.09:31
patersoncSure09:31
patersoncOnto the testing report...09:31
patersoncWork has resumed on getting kselftest working with CIP testing09:32
patersoncOur LAVA infrastructure has been behaving for a change09:32
patersoncThat's probably about it09:32
pave11Yes, so... Testing seems to be better now.09:33
masashi910patersonc: Thanks for your works.09:33
masashi910any other topics?09:33
pave11But I still got timeout.09:33
patersoncpave11: Dohs. For LAVA jobs? Or for gitlab runners?09:33
pave11When three kernels hit testing at the same time (4.4, 4.19, 5.10)... is 2 hours for a job enough?09:33
pave11I see it in gitlab. I'm not sure about the background.09:34
pave11It is easy to just hit retry, but I guess you should know :-).09:34
patersoncI can increase the timeout if you want. Now that we're only using "small" AWS instances for those test jobs the cost impact would be minimal09:35
patersoncAre the jobs timing out waiting for the LAVA jobs to run?09:35
patersoncOr is there another issue?09:35
pave11I'll grab the debug info next time it happens, ok?09:35
masashi910pave11: Thanks, yes please.09:36
masashi910Any other topics?09:36
masashi910309:36
masashi910209:36
masashi910109:36
masashi910#topic CIP Security09:37
*** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:37
masashi910Yoshida-san, are you here?09:37
masashi910Yoshida-san does not seem to be here, so let's skip.09:37
masashi910#topic AOB09:37
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:37
masashi9101. Next IRC meeting09:37
masashi910I cannot host the IRC meeting next week. Can we skip it?09:37
pave11I believe that makes sense.09:38
patersoncpave11: Thank you Pavel09:38
masashi910pave11: Thanks. Then, let's meet on May 6.09:39
wensmasashi910: happy golden week holidays :)09:39
masashi910wens: Exactly. :)09:39
masashi910Are there any business to discuss?09:39
masashi910509:39
patersoncEnjoy the holiday!09:39
masashi910patersonc: Oh, Thanks!! But I cannot go anywhere due to COVID19. :(09:40
masashi910409:40
masashi910309:40
masashi910209:40
masashi910109:40
masashi910So, let's close today's meeting.09:40
masashi910#endmeeting09:40
brloggerMeeting ended Thu Apr 22 09:40:42 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:40
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2021/04/cip.2021-04-22-09.00.html09:40
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2021/04/cip.2021-04-22-09.00.txt09:40
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2021/04/cip.2021-04-22-09.00.log.html09:40
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:40
masashi910Thanks, see you!09:40
wensThank you!09:41
pave11Thank you, good luck with Covid, and with us luck with Covid and Russia.09:41
wenstwo things to deal with, ouch09:41
pave11wens: We are in far better situation than Ukraine, but it is still not fun :-(.09:42
pave11patersonc: UMN situation: I'm not sure Greg got it right. I'll go through the LWN stuff, but I believe what was hit in review were simply honest mistakes.09:43
pave11patersonc: From my side I believe it simply shows that stable is _way_ too happy to accept patches.09:44
patersoncTricky job09:44
alicefo/09:45
pave11alicef: Go ahead.09:45
alicefjust wanted to say hi :) and that I'm also here.09:45
pave11patersonc: -stable rules say "known and bad bug" needs to be fixed... but noone really enforces that, so "hmm this is a tiny leak someone may hit, lets fix it" hits stable :-(.09:46
iwamatsuhi all, I am checking meeting log....09:46
patersoncevening09:47
wensalicef: Welcome :)09:47
pave11iwamatsu: hi!09:47
alicefI'm working with patersonc and iwamatsu in the kselftest implementation09:47
patersoncalicef: Hello!09:47
pave11alicef: Good luck :-). Testing can be a lot of fun.09:47
patersonc:)09:48
sudippave11: I think Greg is not going to revert all the patches, only the patches which does not get another re-review before its merged, and I do have the same concern like you that stable is accepting too many patches than it used to do before.09:48
pave11sudip: I hope/believe Linus will simply not take the series.09:48
sudiplets see, Greg is planning to send them during the merge window09:49
pave11sudip: If you believe stable is taking too many patches... I certainly share the concern. Please speak up on the mailing lists...09:51
sudippave11: but what Greg says is also true that those patches are fixing something09:56
pave11Well... One possibility would be to ask for stable-kernel-rules document to be fixed. Because according to that document, only subset of fixes is acceptable.09:57
pave11But what happens in -stable is that "as long as it is not obviously causing problems, it is acceptable".09:58
*** pave11 has quit IRC10:25
*** masashi910 has quit IRC11:28
*** monstr has joined #cip11:50
*** monstr has joined #cip11:50
sashalw.r.t the reverts: there's just no other way to trigger a mass review of those patches again. we suspect that the amount of reverts that'll actually go in will be much smaller12:49
sashalsome subsys maintainers err on the "doesn't look useful, so revert" side while others don't too12:49
*** samwilson has quit IRC13:15
*** samwilson has joined #cip13:39
*** samwilson has quit IRC15:12
*** samwilson has joined #cip15:33
*** samwilson has quit IRC15:40
*** samwilson has joined #cip15:52
*** eduardas has quit IRC15:58
*** samwilson has quit IRC16:28
*** tpollard has quit IRC17:02
*** monstr has quit IRC17:14
*** ltu86 has joined #cip17:40
*** ltu8 has quit IRC17:48
*** ltu86 is now known as ltu817:48
*** samwilson has joined #cip18:55
*** samwilson has quit IRC18:55
*** jwardy has quit IRC19:52
*** jwardy has joined #cip19:58
*** rajm has quit IRC22:01

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