On Fri, Oct 12, 2018 at 11:43:06AM -0700, Viacheslav Dubeyko wrote: > On Thu, 2018-10-11 at 21:48 -0300, Ernesto A. Fernández wrote: > > On Thu, Oct 11, 2018 at 05:38:35PM -0700, Viacheslav Dubeyko wrote: > > > On Thu, 2018-10-11 at 16:40 -0300, Ernesto A. Fernández wrote: > > > > On Thu, Oct 11, 2018 at 11:05:36AM -0700, Viacheslav Dubeyko wrote: > > > > > On Wed, 2018-10-10 at 15:23 -0300, Ernesto A. Fernández wrote: > > > > > > Direct writes to empty inodes fail with EIO. The generic direct-io code > > > > > > is in part to blame (a patch has been submitted as "direct-io: allow > > > > > > direct writes to empty inodes"), but hfsplus is worse affected than the > > > > > > other filesystems because the fallback to buffered I/O doesn't happen. > > > > > > > > > > > > > > > > Could you please share more detailed explanation of the patch that > > > > > affects the HFS+ behavior? It's hard to follow what patch you mean. > > > > > > > > It was sent to linux-fsdevel: "direct-io: allow direct writes to empty > > > > inodes." > > > > > > > > > > The git provides the commit ID and the annotation for every commit. It > > > will be great to see these details. Could you please share this > > > information? > > > > The patch hasn't been merged yet. > > > > I am not completely sure how to review the patch in such case. I believe > that the best strategy is to wait till the mentioned patch will be > merged and to resend this patch again. You can just ignore the direct-io patch if you find it confusing. It's a separate issue, and the hfs/hfsplus patches are actually easier to test by themselves. > Thanks, > Vyacheslav Dubeyko. > > >
