On Fri, Oct 22, 2010 at 07:21:33PM -0400, J. Bruce Fields wrote: > On Fri, Oct 22, 2010 at 07:01:12PM -0400, J. Bruce Fields wrote: > > On Fri, Oct 22, 2010 at 05:20:07PM -0400, J. Bruce Fields wrote: > > > On Fri, Oct 22, 2010 at 05:00:50PM +0200, Menyhart Zoltan wrote: > > > > J. Bruce Fields wrote: > > > > >On Tue, Oct 05, 2010 at 10:22:30AM +0200, Menyhart Zoltan wrote: > > > > >>Due to some race conditions, the reference count can become 0 > > > > >>while "xprt" is still on a "pool": > > > > > > > > > >Apologies, your email got buried in my inbox.... > > > > > > > > > >> > > > > >>WARNING: at lib/kref.c:43 kref_get+0x23/0x2d() > > > > >> [] kref_get+0x23/0x2d > > > > >> [] svc_xprt_get+0x12/0x14 [sunrpc] > > > > >> [] svc_recv+0x2db/0x78a [sunrpc] > > > > > > > > > >Which kernel exactly did you see this on? Is it reproduceable? > > > > > > > > I saw it on a 2.6.32. > > > > It has not been corrected for the 2.6.36-rc3 yet. Doh. Wait, when you say "has not been corrected on 2.6.36-rc3", do you mean you've actually *seen* the problem occur on 2.6.36-rc3? If not, it's more likely you're seeing the problem that was fixed by 1b644b6e6f6160ae35ce4b52c2ca89ed3e356e18, in 2.6.34-rc1. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
