Hey RobL,

Hi Murali,
Tell you what, I'll take care of the configure tests (did you know the
return type for kmem_cache_destroy has now been changed to void?)

Oh really. So how do we know if there were any leaked objects remaining then?
We still have those cases btw. Since I added the cleanup code to free
all the heap
objects, we don't panic nowadays but it is a bug nonetheless.
There is something wrong with either the vfs or our contract with vfs
since it does not seem to release references on some objects.. weird.

if you
want to fix the actual code this weekend.  That would be great -- I'm
pretty slow with the kernel stuff, and I also need to prepare for SC.

I will fix the code and the configure scripts together then..
when is the scheduled date for the next pvfs2 release?

2.6.19-rc5 is out now.  Guess that's the one to test against.

gotcha.. thanks,
Murali


==rob

_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers

Reply via email to