Date: Sat, 14 May 2016 20:04:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 206238] FUSE can't enter to DIRECT_IO mode during file create. Message-ID: <bug-206238-6-XDL41sNb2A@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206238-6@https.bugs.freebsd.org/bugzilla/> References: <bug-206238-6@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=3D206238 --- Comment #8 from commit-hook@freebsd.org --- A commit references this bug: Author: rmacklem Date: Sat May 14 20:03:22 UTC 2016 New revision: 299753 URL: https://svnweb.freebsd.org/changeset/base/299753 Log: Fix fuse to use DIRECT_IO when required. When a file is opened write-only and a partial block was written, buffered I/O would try and read the whole block in. This would result in a hung thread, since there was no open (fuse filehandle) that allowed reading. This patch avoids the problem by forcing DIRECT_IO for this case. It also sets DIRECT_IO when the file system specifies the FN_DIRECTIO flag in its reply to the open. Tested by: nishida@asusa.net, freebsd@moosefs.com PR: 194293, 206238 MFC after: 2 weeks Changes: head/sys/fs/fuse/fuse_file.c head/sys/fs/fuse/fuse_vnops.c --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206238-6-XDL41sNb2A>