- Thursday, March 17, 2022

release-team@conference.openafs.org

Thursday, March 17, 2022< ^ >

kaduk@jabber.openafs.org/barnowl has set the subject to: openafs release team

Room Configuration

Room Occupants

GMT+0
[15:55:38] meffie joins the room
[15:57:25] <meffie> hello all.
[16:00:24] wiesand joins the room
[16:00:49] <wiesand> Hello
[16:01:25] Cheyenne joins the room
[16:02:12] <Cheyenne> Hello all
[16:03:07] <meffie> thank you for the vos release wiesand
[16:03:52] <wiesand> you're welcome
[16:04:41] <wiesand> I made some progress with preparing the pullup of 14387
[16:05:19] <meffie> excellent news!
[16:05:55] <wiesand> There are a few trivial changes to include first (14469 14470 14471 14219 13390)
[16:06:57] <wiesand> the can of worms opens with 14274 and 14623 - I'm interested in opinions on including those in 1.8.x
[16:08:00] kaduk@jabber.openafs.org/barnowl joins the room
[16:09:06] <kaduk@jabber.openafs.org/barnowl> Hi, sorry I'm late (getting breakfast took longer than expected)
[16:10:00] <wiesand> guess you're still suffering through the dst lag…
[16:10:55] <kaduk@jabber.openafs.org/barnowl> :)
[16:10:56] <meffie> i think those are ok to include in 1.8.x
[16:11:01] <Cheyenne> re the cleanup commits.. I'm trying to remember what compiler level the lastest Mac os is using
[16:12:51] <kaduk@jabber.openafs.org/barnowl> I think I see those two as okay to include but not critical to include
(based on their own functionality).  Removing kdump makes things
exciting if subsequent cleanup on master would have needed to touch
kdump if it was still around
[16:15:21] <meffie> yes, thank make sense
[16:15:29] <meffie> s/thank/that/
[16:15:35] <wiesand> "remove kdump" crosses paths with 14791 (Linux 5.15) which we pulled up and merged already - does make things more interesting, let's include and forget it…
[16:15:37] <Cheyenne> The kdump removal was pretty "mechanical"  I know it it rx.h, but that change was mostly indentation due to removing the need for a large "#if KDUMP..#endif" block
[16:18:55] <Cheyenne> I'm still getting clean builds with master against Linux-5.17-rc8+
[16:18:58] <wiesand> That's about what I have for today.
[16:19:24] <wiesand> Thanks for checking 5.17
[16:19:58] <kaduk@jabber.openafs.org/barnowl> Yes, thanks for checking the latest linux
[16:20:18] <kaduk@jabber.openafs.org/barnowl> On slightly older linux, I think we may be able to reenable
--enable-checking now that I merged 14770
[16:20:41] <meffie> woot!
[16:21:18] <Cheyenne> yay!!!
[16:21:24] <meffie> thank you ben
[16:21:49] <kaduk@jabber.openafs.org/barnowl> it took me long enough :-/
[16:23:06] <kaduk@jabber.openafs.org/barnowl> Anyway, I have six days left as IETF Security AD and there's a lot
left to do before that ends, so I haven't been doing much with openafs
this week.
[16:23:16] <kaduk@jabber.openafs.org/barnowl> Oh, and also there was that OpenSSL bug, that was "fun".
[16:23:24] <wiesand> and 14770 has a path conflict with 14387…
[16:24:15] <wiesand> which one? I think this hasn't trickled down to the distros yet?
[16:24:23] <kaduk@jabber.openafs.org/barnowl> It should be a path conflict only, though (not a real conflict)
[16:24:35] <kaduk@jabber.openafs.org/barnowl> 14387 has a lot of path conflicts, seeing as it touches so many
files...
[16:25:08] <wiesand> that's why I want to pull it up a.s.a.p.
[16:28:25] <kaduk@jabber.openafs.org/barnowl> The OpenSSL bug was announced on tuesday -- an infinite loop in the
modular arithmetic square root subroutine, which is called (in certain
cases) during X.509 certificate parsing.  So a client connecting to a
malicious TLS server will hand, and a TLS server that asks for client
certificates is vulnerable to a malicious TLS client.
[16:29:14] <wiesand> ouch
[16:29:54] <meffie> fun times
[16:32:51] <wiesand> Anything else to discuss today?
[16:33:23] <kaduk@jabber.openafs.org/barnowl> Just a quick memory check for me:
[16:33:24] <meffie> i have nothing.
[16:33:48] <kaduk@jabber.openafs.org/barnowl> There are a couple changes early in the "apple-silicon" topic that are
required for new versions of macOS even on x86 chips, is that right?
[16:34:29] <meffie> i think so, but i've lost track of all the mac changes. marcio would know
[16:34:51] <kaduk@jabber.openafs.org/barnowl> ok
[16:35:05] <Cheyenne> I believe so.. but Marcio would have the answer on that
[16:35:06] <kaduk@jabber.openafs.org/barnowl> I will keep that in mind during the whirlwind of the next couple
weeks.
[16:35:41] <kaduk@jabber.openafs.org/barnowl> I may not be able to join next week, as I think the IETF sessions run
pretty close to this time.
[16:35:43] <wiesand> weeks?
[16:36:14] <meffie> oh, and mark and i have been getting some general questions for people for GSoC projects. it's pretty exciting
[16:36:37] <Cheyenne> Oh.. with some pullups for the 5.17 patches,  1.8.x builds against Linux-5.17-rc8+ as well
[16:36:42] <wiesand> I hope that next week we'll be bus discussing boring 1.8.x pullups ;-)
[16:36:51] <kaduk@jabber.openafs.org/barnowl> weeks, week and a bit, roughly the same
[16:36:57] <wiesand> busy
[16:37:06] <kaduk@jabber.openafs.org/barnowl> :)
[16:38:16] <Cheyenne> on the weather front.. it's still snowing here :)
[16:38:24] <meffie> ok, have a good day all.
[16:38:59] <Cheyenne> have a good week everyone
[16:39:32] <wiesand> you have my envy - I'll stow my shovel away tomorrow
[16:39:57] <wiesand> Let's adjourn then. Thanks a lot everybody!
[16:40:02] wiesand leaves the room
[16:40:29] <kaduk@jabber.openafs.org/barnowl> Thanks everyone!
[18:12:50] meffie leaves the room
[18:29:30] kaduk@jabber.openafs.org/barnowl leaves the room
[22:07:52] mvitale joins the room
[23:05:07] kaduk@jabber.openafs.org/barnowl joins the room