From: Stef B. <st...@gm...> - 2010-07-01 13:49:50
|
What interface you're using, lowlevel or high? Stef 2010/7/1 Paul Schutte <pa...@up...>: > That is why I say I think I stumbled onto a bug. > It looks like the lookup count (on the fuse side) does get incremented > even when the LINK request fails. > > Regards > Paul > > On Thu, 2010-07-01 at 15:34 +0200, Miklos Szeredi wrote: >> On Thu, 01 Jul 2010, Paul Schutte wrote: >> > This is how I understand it, but there is a problem if the filesystem >> > does not implement hardlinks. >> > >> > On the fuse side it does the N+1 thing when doing a hardlink and expects >> > you to do N+1 on the users space side as well. Except you can't because >> > you did'nt implement hardlinks, so in user space you still sit with N. >> > >> > Now in forget fuse want's you to forget (N+1) references. If you do that >> > you end up with N-(N+1)=-1 and there is the problem. >> >> I don't understand. If the filesystem doesn't implement hard links >> then the LINK request will fail and the lookup count will not be >> incremented. >> >> Thanks, >> Miklos > > > |