Thursday, 2023-08-03

*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 246 seconds)04:52
*** tobsch <tobsch!~quassel@2a02:810d:603f:fe38:2be4:c5ca:c64:ee1d> has joined #cip05:26
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:50
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:04
*** shoragan_ <shoragan_!~shoragan@user/shoragan> has joined #cip07:02
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Ping timeout: 260 seconds)07:04
arisutSorry I cannot join today meeting11:22
*** uli <uli!~uli@2001:4091:a247:8440:bf3c:b417:b27b:4cb5> has joined #cip11:53
*** masami <masami!~masami@FL1-211-135-148-63.tky.mesh.ad.jp> has joined #cip11:53
*** tobsch <tobsch!~quassel@2a02:810d:603f:fe38:2be4:c5ca:c64:ee1d> has quit IRC (Ping timeout: 260 seconds)11:56
pave1arisut: no problem. Feel free to send an email if you have something to report.11:58
pave1Hi!12:01
masamihello12:01
iwamatsuhi12:02
ulihi12:02
pave1#startmeeting CIP IRC weekly meeting12:02
collab-meetbot`Meeting started Thu Aug  3 12:02:38 2023 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.12:02
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:02
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:02
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:02
pave1#topic AI review12:02
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:02
pave11. create kernelci pipeline for buster images (arisut)12:03
pave1Skip, as arisut is not here.12:03
pave12. draft press release on 6.1 release (jan)12:03
pave1Skip.12:03
pave1Anything else?12:03
pave1312:03
pave1212:03
pave1112:03
pave1#topic Kernel maintenance updates12:04
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:04
ulireviewing 6.1.3912:04
masamiThis week reported 3 new CVEs and 10 updated CVEs.12:04
iwamatsuI am reviewing 6.1.43.12:04
pave1I'm reviewing 6.1.40, 42, 43.12:04
pave1I'll be travelling next week.12:05
pave1312:05
pave1212:05
pave1112:05
pave1#topic Kernel release status12:06
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:06
pave1-4.412:06
ulii'll fix up the missing bits and then it's ready to release12:06
ulithanks for the reviews12:06
pave1Good. I should do -rt, too.12:06
pave1Thanks for the patches!12:07
pave1-4.1912:07
iwamatsuon track12:07
pave1-rt is still on track, but should do release when we get a match12:08
pave1-5.1012:08
iwamatsuon track12:08
pave1-rt is still on track12:08
pave1-6.112:08
pave1on track12:09
iwamatsuon track, lts and rt12:09
pave1-rt is on track, too.12:09
pave1good.12:09
pave1312:09
pave1212:09
pave1112:09
pave1#topic Kernel testing12:09
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:09
pave1If someone from testing team is here, speak up.12:09
pave1312:10
pave1212:10
pave1112:10
pave1#topic AOB12:10
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:10
masamiI joined CIP security team meeting to talk about cip-kernel-sec. I got some feedback from them.12:10
masamiI think some requests were reported from the team in the last TSC meeting.12:10
pave1I'll be travelling next week, but jki should be here to lead the meeting.12:11
pave1masami: Yes, there was some discussion there.12:11
pave1Thanks for doing this!12:11
pave1Is there anything we should be changing soon?12:12
pave1...with respect to security?12:13
masamipavel: It'd be nice to have document about patch back porting policy12:13
masamiSometimes we ask TSC to not backport pactches such as meltdown/spectre bugs.12:13
pave1masami: We are trying to follow -stable rules, but even those are poorly documented.12:14
pave1We are basically using -stable as our upstream, so if -stable drops the patch, we don't even review it.12:15
pave1Then we drop those that don't apply, unless it looks easy and critical.12:15
masamipavel: yes. -stable rule is one of our rule.12:15
masamiOne of important task would be polish document.12:17
pave1I guess someone could periodically check the CVE database we maintain to see if we missed something "really bad"12:17
pave1Yes, they'll want documentation and we don't have a good one.12:18
masamicip-kernel-sec uses debian and ubuntu's security tracker to get CVE information12:18
masamibut I found some CVEs (CVE-2022-3533 and CVE-2022-3606 ) are not tracked them12:19
pave1Fun :-(.12:19
masamilibbpf can be created from kernel source or libbpf's git repo.12:19
pave1I guess we should discuss it on cip-dev so that jki sees the discussion?12:20
masamiyes. move to mailing list.12:20
pave1Anything else?12:21
pave1512:21
pave1412:21
pave1312:21
pave1212:21
pave1112:21
masamiI'll be absent next week12:21
pave1Noted, thank you.12:22
pave1I may or may not be able to make it.12:22
pave1#endmeeting12:22
collab-meetbot`Meeting ended Thu Aug  3 12:22:29 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:22
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/08/cip.2023-08-03-12.02.html12:22
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/08/cip.2023-08-03-12.02.txt12:22
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/08/cip.2023-08-03-12.02.log.html12:22
*** collab-meetbot` changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"12:22
pave1Thank you, have a nice Summer!12:22
ulithanks12:22
masamithank you!12:22
iwamatsuthank you12:22
*** masami <masami!~masami@FL1-211-135-148-63.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:23
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)14:19
*** uli <uli!~uli@2001:4091:a247:8440:bf3c:b417:b27b:4cb5> has left #cip (Leaving)14:57
*** tobsch <tobsch!~quassel@2a02:810d:603f:fe38:3ec4:2fd6:e97c:3778> has joined #cip15:08
*** tobsch <tobsch!~quassel@2a02:810d:603f:fe38:3ec4:2fd6:e97c:3778> has quit IRC (Ping timeout: 246 seconds)15:22
*** tobsch <tobsch!~quassel@2a02:810d:603f:fe38:992e:f644:e2ba:d431> has joined #cip19:06
*** tobsch <tobsch!~quassel@2a02:810d:603f:fe38:992e:f644:e2ba:d431> has quit IRC (Ping timeout: 245 seconds)19:10
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip20:12
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 264 seconds)21:46

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!