Date: Mon, 28 Dec 2015 01:51:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 194293] FUSE program freezes when seeking pos > file size Message-ID: <bug-194293-3630-KxoAKtMvWI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-194293-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-194293-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D194293 rmacklem@uoguelph.ca changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmacklem@uoguelph.ca --- Comment #5 from rmacklem@uoguelph.ca --- Created attachment 164744 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D164744&action= =3Dedit patch fuse so that a WRONLY open becomes a RDWR open This patch modifies the FreeBSD Fuse fs (in sys/fs/fuse) so that it always does a RDWR open when a WRONLY open is requested. I believe this bug happens when a write of a partial block occurs when not doing DIRECT_IO. When this happens the buffer cache first reads the entire block in. Without a RDWR open, this read fails and leaves the block "stuck", making umount etc. fail. The problem I see w.r.t. this patch is that a WRONLY open will fail if the process doesn't have Read access to the file. An alternate way to patch this would be to force DIRECT_IO for WRONLY opens. Comments/opinions? Hopefully nishida@ can test this patch to determine if it fixes the problem? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194293-3630-KxoAKtMvWI>