On 09/09/2007, J. Bruce Fields <[EMAIL PROTECTED]> wrote: > > When accessing a directory inode from a single other client, NFSv4 > > callbacks catastrophically failed [1] on the NFS server with > > 2.6.23-rc4 (unpatched); clients are both 2.6.22 (Ubuntu Gutsy build). > > Seems not easy to reproduce, since this kernel was running smoothly > > for 7 days on the server. > > > > What information will help track this down, or is there a known > > failure mechanism? > > I haven't seen that before. > > > I can map stack frames to source lines with objdump, if that helps.
> If it's still easy, it might help to figure out exactly where in > xprt_reserve() it died, and why. If we've got some race that can lead > to freeing the client while a callback is in progress, then perhaps this > is on the first dereference of xprt? I've raised the bug report into bugzilla, added other observations from a second occurrence recently and disassembled xprt_reserve with line numbers. http://bugzilla.kernel.org/show_bug.cgi?id=9003 Ping me for any more detail/info and thanks! Daniel -- Daniel J Blueman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
