[00:51:12] --- Russ has left: Disconnected
[03:23:25] --- jaltman has become available
[03:26:22] --- jaltman has left: Disconnected
[03:51:02] --- jaltman has become available
[04:27:43] --- jaltman has left: Replaced by new connection
[04:27:46] --- jaltman has become available
[05:17:52] --- jaltman has left: Disconnected
[05:18:00] --- jaltman has become available
[05:20:32] --- jaltman has left: Disconnected
[05:20:41] --- jaltman has become available
[05:35:23] --- Simon Wilkinson has left
[06:57:30] --- jaltman has left: Disconnected
[06:57:46] --- jaltman has become available
[09:21:26] --- Russ has become available
[13:22:34] <kaduk@mit.edu/barnowl> I think I'm still confused by the distinction between FlushVCache and
TryEvictVCache ... FlushVCache seems to be "we need another struct
vcache and are going to get one from this mostly unused vcache/vnode",
and seems to basically just detach our stuff from the vnode.  But, I
think that the vnode does not necessarily get destroyed as part of
that, so the (freebsd) VFS may want to call VOP_INACTIVE/VOP_RECLAIM
on it, which attempt to call back into our stuff and would panic
trying to dereference NULL.
[14:34:18] --- jaltman/FrogsLeap has become available
[14:58:02] --- jakllsch has become available
[17:00:14] --- Derrick Brashear has left
[17:05:03] --- Derrick Brashear has become available
[19:20:08] --- abo has left
[19:25:18] --- abo has become available
[21:59:58] --- Russ has left: Disconnected