Hi Sam,
> Yeah and write some big warnings to the log about leaking cache > entries. Are there any interfaces to the kmem_cache that allow you > to query the entries you've allocated so that we don't have to do > that ourselves? Nope; I don't think there are. We have to do that I am afraid. I remember doing something like that for pvfs2 earlier for freeing some of the pvfs2 inode structures.. I don't know if I checked that in though.. Thanks, Murali > > > To find out where we are leaking we could store the return address > > of the caller > > of the alloc() function in the object and use that to find out the > > offending leaks.. > > What do you think? > > Sounds good to me. > -sam > > Thanks! > > Murali > > > >> > >> -sam > >> > >> > >> > >> On Aug 16, 2007, at 12:59 PM, Murali Vilayannur wrote: > >> > >>> Kevin, > >>> Instead of the call to d_add(), can you replace it by a > >>> pvfs2_d_splice_alias() with the same parameters as before and > >>> recompile/reload and see if that fixes the crash. > >>> Something like the attached.. > >>> thanks, > >>> Murali > >>> > >>> On 8/16/07, Kevin Harms <[EMAIL PROTECTED]> wrote: > >>>> Murali, > >>>> > >>>> i tried the patch. (applied it to 2.6.3 source) it get > >>>> crashes from > >>>> on one of the machines. > >>>> i send you an email with dmesg output. > >>>> > >>>> Kevin > >>>> > >>>> <dcache.patch> > >>> _______________________________________________ > >>> Pvfs2-developers mailing list > >>> [email protected] > >>> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers > >> > >> > >> > >> > > > > _______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
