From: Christoph Hellwig <hch@infradead.org>
To: Richard Weinberger <richard@nod.at>
Cc: user-mode-linux-devel@lists.sourceforge.net, dxld@darkboxed.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] hostfs: Use noop_fsync for directories
Date: Tue, 13 Jan 2015 14:19:58 -0800 [thread overview]
Message-ID: <20150113221958.GA27739@infradead.org> (raw)
In-Reply-To: <1421187358-32600-1-git-send-email-richard@nod.at>
On Tue, Jan 13, 2015 at 11:15:58PM +0100, Richard Weinberger wrote:
> Daniel reported that dpkg(1) dies if the root filesystem is a hostfs
> because it does not expect fsync(2) to fail with EINVAL on directories.
> While fsync(2) is allowed to fail with EINVAL if the filesystem does not
> support it we can do better and use noop_fsync() to not confuse userspace
> further.
Shouldn't hostfs pass the fsync through to the host filesystem?
next prev parent reply other threads:[~2015-01-13 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 22:15 [PATCH] hostfs: Use noop_fsync for directories Richard Weinberger
2015-01-13 22:19 ` Christoph Hellwig [this message]
2015-01-13 22:26 ` Richard Weinberger
2015-01-14 8:39 ` Christoph Hellwig
2015-01-14 8:43 ` Richard Weinberger
2015-01-18 1:08 ` Daniel Gröber
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=20150113221958.GA27739@infradead.org \
--to=hch@infradead.org \
--cc=dxld@darkboxed.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).