Re: find stuck in state "clock"

["Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>]

Simon 'corecode' Schubert wrote:
> Conclusion:
> [*] The fact that the namecache entry is locked, doesn't lead to the 
> deadlock, but it is the reason that dozens of find(1)s lock on /dev/ttyp5.

Why do we keep the namecache entry locked in e.g. kern_chown?  We just 
need the vnode (nlookup) and not the namecache, or am I wrong?

cheers
  simon

--
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low $$$ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \