09:00:00 #startmeeting CIP IRC weekly meeting 09:00:00 Meeting started Thu May 6 09:00:00 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:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:00 The meeting name has been set to 'cip_irc_weekly_meeting' 09:00:02 #topic rollcall 09:00:08 please say hi if you're around 09:00:14 hi 09:00:25 hi 09:00:28 hi 09:00:52 hi 09:00:57 Let's get started. 09:01:00 #topic AI review 09:01:06 1. Combine root filesystem with kselftest binary - iwamatsu 09:01:19 iwamatsu: are you around? 09:01:56 Let's come back later. 09:01:57 2. Do some experiment to lower burdens on CI - patersonc 09:02:01 * patersonc goes to answer front door (there are no updates for my AIs) 09:02:24 patersonc: Sure, thanks. 09:02:41 3. Monitor the status of CVE-2021-3444 and CVE-2021-20292 (3/25) - Kernel Team 09:02:46 4. Monitor the status of CVE-2021-29650 (4/1) - Kernel Team 09:03:15 No updates from me, sorry. 09:03:26 No updates on these issues. 09:03:46 pave1, wens: Thanks. Let's keep them open. 09:03:59 5. Update Testing table below with 5.10 info - patersonc 09:04:37 patersonc: according to your previous message, there is no update on this either. 09:04:48 6. Ask the needs to backport CVE-2021-23133 [net/sctp: race in sctp_destroy_sock] (4/22) 09:04:56 After the inquiry email, the fix was posted to both 4.4 and 4.19. So this AI is closed. 09:05:04 https://lore.kernel.org/stable/20210426072820.621580223@linuxfoundation.org/ 09:05:11 https://lore.kernel.org/stable/20210426072816.631201988@linuxfoundation.org/ 09:05:26 So, I will close this. 09:05:32 any other topics? 09:05:50 3 09:05:53 2 09:05:57 1 09:06:00 #topic Kernel maintenance updates 09:06:17 Three new issues from the past two weeks. 09:06:26 Report from 4/29: https://lore.kernel.org/cip-dev/CAGb2v64xbANytUSdzOowMh=wJVue3B6UmtDcvmjqtyh31Hcz2Q@mail.gmail.com/ 09:06:35 And 5/5: https://lore.kernel.org/cip-dev/CAGb2v65PfUtwZX8c+W2Yygk3XTOTxfXU0SoFUjXUAh2wYuHmyA@mail.gmail.com/ 09:07:39 I have reviewed patches queued for 5.10.33, 34, 35 and related 4.19. 09:08:05 As pave1 mentioned in his replies, backport fix for one of the new issues is trivial, while the fixes for the other is in the stable queue. 09:09:51 wens, pave1: Thanks for your updates. 09:11:09 pave1: Could you backport CVE-2021-31916? 09:12:14 masashi: Yes, I probably should. Backport is easy, but I can't really test it and have some issues getting patches to the mailing lists. 09:12:50 last time I think you used the wrong address 09:13:03 stable@kernel.org vs stable@vger.kernel.org 09:13:14 or is the former one an alias? 09:13:24 wens: Aha, ok, _that_ would explain stuff. Let me try to do better next time. 09:13:49 not sure when they are planning to move the vger lists to the new mailing list service though 09:14:41 I see both cc: stable@kernel.org and cc: stable@vger.kernel.org in the commits. 09:14:48 I guess that confused me. 09:15:02 doc says to use the vger one 09:15:51 patersonc: CVE-2021-31916 [md: dm_ioctl: out-of-bounds array access] . Do you think CIP Lab has a set to test it? 09:16:12 masashi910: What it needed? 09:16:37 pave1: Do you have specific requirement? 09:17:21 Passing crafted data to device mapper ioctl. 09:17:40 I doubt we have specific tests to do that, as usual for the CVE stuff :-(. 09:18:15 i guess usual way is to simply submit untested patch (again, as usual with CVEs), but... 09:19:27 Backporting the on liner is quite easy but testing is not. 09:19:37 one liner 09:20:59 pave1: Hmm. Do you know how was it dealt with on other stables? 09:21:31 they likely just apply it without additional testing 09:21:51 masashi910: I believe people simply hope it is simple enough not to need testing. 09:22:02 Hmmm. 09:22:50 to be honest, mainline developers probably don't care that much about stable kernels 09:23:15 We need to address this kind of issue when we enter the self maintenance phase. Let's me think about it. 09:23:31 Let me think about it. 09:24:02 So, at this moment, let me drop my request, Pavel-san. 09:24:27 Ok. 09:24:36 Any other topics? 09:24:46 3 09:24:49 2 09:24:52 1 09:24:55 #topic Kernel testing 09:25:17 I don't really have any updates this week 09:25:45 I got failures linked to the 2hour limit, again with 5.10.35 and friends. 09:26:00 I just resubmitted. 09:26:54 patersonc: Thanks for your report. 09:27:00 Any other topics? 09:27:13 3 09:27:16 2 09:27:19 1 09:27:22 #topic AOB 09:27:30 Are there any business to discuss? 09:27:32 hi 09:27:42 please, Wens-san. 09:28:13 due to changes in some personal circumstances, I likely won't be able to attend meetings in the future. Scheduling problem ... 09:28:29 (changes in a good way if anyone is wondering) 09:28:56 wens: We will miss you... 09:29:10 Hopefully I'll still be able to contribute. 09:29:44 wens: Your contributions have been great! I am hoping you can continue! 09:30:09 Thanks :) 09:30:35 Any other business? 09:30:52 3 09:30:57 2 09:31:00 1 09:31:03 So, let's close today's meeting. 09:31:10 #endmeeting