linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [patch] posix_fallocate.3: Mention glibc emulation caveats.
Date: Wed, 7 Oct 2015 09:44:54 -0400	[thread overview]
Message-ID: <561521D6.50106@redhat.com> (raw)
In-Reply-To: <56123D86.9050601@gmail.com>

On 10/05/2015 05:06 AM, Michael Kerrisk (man-pages) wrote:
> Hi Carlos,
> 
> On 10/02/2015 05:17 AM, Carlos O'Donell wrote:
>> Michael,
>>
>> You're going to really enjoy reading this patch ;-)
> 
> Thanks for the patch. What a sad story :-{

I've gotten at least one hate mail for documenting how broken
it is when the underlying filesystem doesn't support it ;-)

Florian Weimer (Red Hat) started a rather long and interesting
discussion on libc-alpha about removing the emulation layer,
but we found that it was impossible to do without breaking a
lot of userspace applications that operate over NFS, are
single-threaded, and expect posix_fallocate to work correctly.

The best compromise was to document the behaviour, and wait
for everyone to use NFS 4.2, at which point the issue goes
away. Until then we need to help users cope.

The worst case scenario would be that we remove the fallback
and all the downstream users start implementing their own
incorrect and poorly tested fallback. One fallback
in one project, reviewed by a dozen people is sane.

> Thanks. I've applied. I tweaked the wording a bit in a further
> commit, and then made a further commit where I tried to fine tune
> the  technical details a little. Could you please check commit
> 624fbe44d9c1ef54eb3fd36328f59a5037b87986 and let me know if there
> ia any technical misstep there?

Looks perfect. The goal is to scare you into reviewing your code ;-)

Cheers,
Carlos.

  reply	other threads:[~2015-10-07 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  4:17 [patch] posix_fallocate.3: Mention glibc emulation caveats Carlos O'Donell
2015-10-05  9:06 ` Michael Kerrisk (man-pages)
2015-10-07 13:44   ` Carlos O'Donell [this message]
     [not found]     ` <561521D6.50106-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-08 21:10       ` Michael Kerrisk (man-pages)

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=561521D6.50106@redhat.com \
    --to=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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).