Le vendredi 26 août 2011 à 20:02 -0400, J. Bruce Fields a écrit : > On Sun, Jul 31, 2011 at 08:58:54AM +0200, Eric Dumazet wrote: > > Le samedi 30 juillet 2011 à 08:23 +0200, Eric Dumazet a écrit : > > > Le samedi 30 juillet 2011 à 16:06 +1000, NeilBrown a écrit : > > > > umount /proc/fs/nfsd > > > > > > > > > > > > > > Thans a lot, this was the thing I missed ! > > > > > > > > > > Hmm, after this, I left things as the were (nfsd module loaded, but a 0 > > use count ) > > > > I got a BUG while updatedb was running, > > (I tried this on a debian machine/kernel) > > > > Same bug on : > > > > cat /proc/self/mounts > > Any luck figuring this out? > > I tried reproducing, by stopping everything to get nfsd refcount to > zero: > > # lsmod | grep '^nfsd' > nfsd 300025 0 > > then running 'cat /proc/self/mounts'. > > But I don't see any crash. > > This is only 3.1.0-rc1 plus some nfsd patches. > > --b. > > > > > I'll take a look at this issue later, after my vacations, unless someone > > wants to take a look before me ;) Unfortunately, latest linux tree doesnt even boot on my machine, so I cannot reproduce the problem right now. Last message displayed being "Switching to clocksource tsc" Previous kernels were continuing with : [ 4.448417] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 4.597727] Real Time Clock Driver v1.12b Might be a problem with latest tty changes -- 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
