Home
release-team@conference.openafs.org
Wednesday, October 12, 2016< ^ >
Room Configuration
Room Occupants

GMT+0
[00:11:43] mvita leaves the room
[00:22:03] mvita joins the room
[04:22:10] mvita leaves the room
[05:06:32] Jeffrey Altman leaves the room
[05:06:32] Jeffrey Altman joins the room
[11:52:31] mvita joins the room
[11:58:32] mvita leaves the room
[13:12:04] mvita joins the room
[13:18:10] meffie joins the room
[13:36:52] mvita leaves the room
[13:50:32] Jeffrey Altman leaves the room
[13:57:52] mvita joins the room
[13:58:57] Jeffrey Altman joins the room
[14:05:09] <meffie> hello kadukoafs, still working on NEWS. in a meeting atm.
[14:14:51] wiesand joins the room
[14:15:07] <wiesand> sorry
[14:16:30] <kadukoafs@gmail.com/barnowl9C09F4AA> I'm running late, myself.
[14:17:26] <wiesand> Any news on Linux 4.8?
[14:17:51] <wiesand> Or the 4.9 merge window stuff?
[14:18:55] <wiesand> gerrit 12415 seems harmless?
[14:19:23] <wiesand> 12413 had no review yet
[14:19:46] Jeffrey Altman leaves the room
[14:19:47] <meffie> no new news on 4.8 yet, planning on looking at 4.9 this week.
[14:19:47] Jeffrey Altman joins the room
[14:20:04] <wiesand> I updated the NEWS change (12395), assuming those two go into 1.6.19pre1
[14:20:40] <wiesand> mike: thanks
[14:21:31] <kadukoafs@gmail.com/barnowl9C09F4AA> 12415 poses no risk to the 1.6 release.
The story there is that posix specifies three time zone formats, one
of which is basically "implementation defined".
The implementation-defined one consults the tzdata, but apparently the
other two can be processed entirely within libc, so the tests will
work on a barebones debian system, since the debian packaging does not
declare a dependency on tzdata.
[14:22:14] <wiesand> thanks for the explanation
[14:22:57] <wiesand> I wish someone would spell out 12413 to me like this ;-)
[14:24:14] <wiesand> So, do we want to issue pre1 soon, or wait until someone actually tested with the new Linux kernel?
[14:24:16] <kadukoafs@gmail.com/barnowl9C09F4AA> Well, I didn't actually do the full level of research on 12413, but
my understanding is that basically, the vfs calls our routine with a
bunch of parameters, including how much was requested to be written
and how much was actually written.  When we call back into the vfs to
commit the write, we should only claim the bytes that were actually
written.
[14:24:24] <meffie> btw, i'm finding some interesting things with the gcc on fedora 25.  the gcc there is picker about indentation, etc.
[14:24:40] <wiesand> "good" ;-)
[14:24:44] <kadukoafs@gmail.com/barnowl9C09F4AA> (They presumably also give the length requested to be written since it
might be useful in locating the request or something like that.)
[14:25:11] <meffie> * pickier
[14:27:00] <wiesand> ben: thanks. Otherwise, random kernel memory content may appear in the file?
[14:27:46] <kadukoafs@gmail.com/barnowl9C09F4AA> More likely zeros, I think.
[14:28:18] <meffie> yes, i think they said zeros were found
[14:28:20] <wiesand> Another potential source for 4k holes?
[14:29:33] <wiesand> Anyway, I need +1s on it. And I haven't run a test build including it yet, but that's easier to get…
[14:29:53] <kadukoafs@gmail.com/barnowl9C09F4AA> Yeah.
I think I just +1'd it.
[14:30:33] <wiesand> so, 12413 + 12415 + NEWS + "make pre1" = 1.6.19pre1 ?
[14:31:38] <kadukoafs@gmail.com/barnowl9C09F4AA> No objections here.
[14:31:50] <wiesand> Thanks.
[14:32:13] <wiesand> I think this concludes the 1.6 topics today.
[14:32:20] <wiesand> On to 1.8?
[14:33:17] <kadukoafs@gmail.com/barnowl9C09F4AA> I think the main question I have for 1.8 is what the status is of the
getcwd-fix stuff.
[14:34:24] <meffie> i dont think mark has an update at moment. but we can schedule time this week.
[14:35:18] <wiesand> we could still revert "shake harder" on master too, until someone finds the time for it
[14:36:05] <meffie> i'd rather not revert that fix ;)
[14:36:31] <kadukoafs@gmail.com/barnowl9C09F4AA> Me, too :)
[14:38:04] <wiesand> what's the comparative of "sad" ? ;-)
[14:38:56] <wiesand> But the question is whether this should block 1.8 progress. After all, it could be pulled in again later.
[14:39:02] <wiesand> I mean before 2.0…
[14:40:15] <kadukoafs@gmail.com/barnowl9C09F4AA> I think it sounded like we were pretty close to what we wanted and
just needed a couple tweaks.  But I could be wrong.
[14:41:14] <meffie> got to go. have a good day
[14:41:26] <kadukoafs@gmail.com/barnowl9C09F4AA> you, too
[14:42:14] <wiesand> we also have two new entries in RT
[14:42:34] <wiesand> 133465 looks scary
[14:42:51] <wiesand> 133467 looks bad too
[14:43:16] <kadukoafs@gmail.com/barnowl9C09F4AA> Anyone feel like trying to replicate 133467?
[14:43:37] <mvita> looking
[14:44:58] <wiesand> I can do either that or work on pre1 :-(
[14:46:26] <mvita> it looks familiar, actually, but I can't look at it right now, I'm in company mtg
[14:46:34] <mvita> I will look closer later today.
[14:46:52] <kadukoafs@gmail.com/barnowl9C09F4AA> Thanks!
[14:48:26] <wiesand> I guess that's it for today?
[14:48:56] <Jeffrey Altman> hi.  133465 is one of the issues I brought up last week.
[14:49:07] <kadukoafs@gmail.com/barnowl9C09F4AA> Probably.
You already listed anything I need to be doing that's 1.6-related, I
think.
[14:49:08] <wiesand> That was my guess.
[14:51:03] <wiesand> It seems unlikely that openafs will have the resources to fix these RX protocol issues.
[14:51:27] <wiesand> Wasn't the foundation looking for items they could pay developers for?
[14:54:07] <wiesand> Ok, things are sad these days. Anything else to discuss today?
[14:55:35] <wiesand> It seems not. Thanks everyone! Please have a look at NEWS.
[14:55:47] <wiesand> And review review review…
[14:55:52] <wiesand> Bye
[14:55:53] wiesand leaves the room
[14:56:31] <kadukoafs@gmail.com/barnowl9C09F4AA> thanks
[15:04:25] mvita leaves the room
[15:30:06] mvita joins the room
[16:13:08] mvita leaves the room
[16:17:47] meffie leaves the room
[16:25:12] meffie joins the room
[17:07:13] meffie leaves the room
[17:21:09] Jeffrey Altman leaves the room
[17:26:25] mvita joins the room
[17:36:49] Jeffrey Altman joins the room
[18:09:25] mvita leaves the room
[19:05:35] mvita joins the room
[19:07:56] mvita leaves the room
[19:07:57] mvita joins the room
[19:13:58] mvita leaves the room
[19:27:30] mvita joins the room
[19:33:08] mvita leaves the room
[19:33:08] mvita joins the room
[19:48:03] mvita leaves the room
[19:48:04] mvita joins the room
[20:37:16] mvita leaves the room
[20:39:50] mvita joins the room
[20:56:38] mvita leaves the room
[21:14:19] mvita joins the room
[21:20:21] mvita leaves the room
[22:07:22] mvita joins the room
[22:15:12] mvita leaves the room
Powered by ejabberd Powered by Erlang Valid XHTML 1.0 Transitional Valid CSS!