lstat() and fstat()

[Andrew Tridgell]

Jeremy,

I just noticed something that could explain a couple of strange oplock
problems (though not all I suspect). We use a mixture of lstat() and
fstat() in Samba. We also use the inode/device to control oplocks. The
problem is that in the case of a symlink lstat() will return the
inode/device of the link and fstat() will return the inode/device of
the file that the link points to. So if we compare the dev/inode
during a oplock break we will get a mismatch.

I haven't fixed this, I just thought I should mention it before I
forget.