Date: Tue, 25 Nov 2003 23:38:44 +0000 From: Ian Dowse <iedowse@maths.tcd.ie> To: Erez Zadok <ezk@cs.sunysb.edu> Cc: fs@freebsd.org Subject: Re: vnode refcnt bug? Message-ID: <200311252338.aa05451@salmon.maths.tcd.ie> In-Reply-To: Your message of "Tue, 25 Nov 2003 16:22:27 EST." <200311252122.hAPLMRfE018534@agora.fsl.cs.sunysb.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200311252122.hAPLMRfE018534@agora.fsl.cs.sunysb.edu>, Erez Zadok wr ites: >Hmmm, yes I think that could be a serious problem (esp. since fbsd doesn't >have autofs yet). And I think it deviates from "norms" where a cwd is >essentially occupying a vnode within the mounted f/s and therefore the f/s >shouldn't be unmounted! This is rather bad for users who sit on an nfs mnt >point, ls'ing files happily, and then the kernel unmounts the mnt pt, moves >their cwd down to the covered (typically empty) vnode, and the poor user's >next /bin/ls shows nothing. Yes, I agree completely - however the question of what to do with references to about-to-be-covered vnodes at mount time still remains. I'll have to look in more detail at why the checkdirs() approach was needed in the first place to see if simply removing it is an option. Any other approaches I can think of right now for solving this issue appear to either extend the original checkdirs() hack, or else just replace one kind of undesirable behaviour with another. Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311252338.aa05451>