David Holland wrote:
> If something in fuse is causing these cases to share the same open and
> thus the same struct file, fuse is broken. Fix fuse first.
>
> If that isn't what's happening, the next possible problem is that
> puffs/refuse/whatnot is the losing IO_NDELAY flag of VOP_WRITE. If so
On Sat, Apr 23, 2016 at 09:20:28PM +0200, Emmanuel Dreyfus wrote:
> > If something in fuse is causing these cases to share the same open and
> > thus the same struct file, fuse is broken. Fix fuse first.
>
> The NetBSD VFS interface does not let underlying filesystem distinguish
> different s
David Holland wrote:
> If something in fuse is causing these cases to share the same open and
> thus the same struct file, fuse is broken. Fix fuse first.
The NetBSD VFS interface does not let underlying filesystem distinguish
different struct file for a given vnode. That information is just not
On Fri, Apr 22, 2016 at 09:10:23AM +, Emmanuel Dreyfus wrote:
> I talked to the glusterFS developer that hit the problem about the
> requirement. This is to iplement mandatory locks, a feature not available
> in UFS.
UFS isn't relevant.
> Quooted below is the scenario chere the problem
Joerg Sonnenberger writes:
> On Fri, Apr 22, 2016 at 10:42:10AM -0400, Greg Troxel wrote:
>> I still don't understand why this is about FUSE. What if a file were
>> opened without O_NONBLOCK and then the same file were opened with?
>
> O_NONBLOCK is pretty much pointless for regular files. It o
