From: Viacheslav Dubeyko <slava@dubeyko.com>
To: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] hfsplus: fix return value of hfsplus_get_block()
Date: Thu, 11 Oct 2018 17:38:35 -0700 [thread overview]
Message-ID: <1539304715.3094.4.camel@slavad-ubuntu-14.04> (raw)
In-Reply-To: <20181011194020.pwowja3onmqall4c@eaf>
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?
Thanks,
Vyacheslav Dubeyko.
next prev parent reply other threads:[~2018-10-12 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 18:23 [PATCH 1/2] hfsplus: fix return value of hfsplus_get_block() Ernesto A. Fernández
2018-10-10 18:24 ` [PATCH 2/2] hfs: fix return value of hfs_get_block() Ernesto A. Fernández
2018-10-20 1:56 ` Viacheslav Dubeyko
2018-10-11 18:05 ` [PATCH 1/2] hfsplus: fix return value of hfsplus_get_block() Viacheslav Dubeyko
2018-10-11 19:40 ` Ernesto A. Fernández
2018-10-12 0:38 ` Viacheslav Dubeyko [this message]
2018-10-12 0:48 ` Ernesto A. Fernández
2018-10-12 18:43 ` Viacheslav Dubeyko
2018-10-12 21:00 ` Ernesto A. Fernández
2018-10-20 1:55 ` Viacheslav Dubeyko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1539304715.3094.4.camel@slavad-ubuntu-14.04 \
--to=slava@dubeyko.com \
--cc=akpm@linux-foundation.org \
--cc=ernesto.mnd.fernandez@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).