From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: ENOSYS/EOPNOTSUPP fallback?
Date: Mon, 12 Jun 2017 14:07:40 -0400 [thread overview]
Message-ID: <20170612180740.GD1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170612175520.GF1214367@wirbelwind>
On Mon, Jun 12, 2017 at 07:55:20PM +0200, Joakim Sindholt wrote:
> On Sun, Jun 11, 2017 at 02:57:59PM -0600, Benjamin Slade wrote:
> > Thank you for the extensive reply.
> >
> > Just to be clear: I'm just an end-user of flatpak, &c. As far as I can
> > tell, flatpak is making use of `ostree` which assumes that the libc will
> > take care of handling `dd` fallback (I got the impression that flatpak
> > isn't directly calling `fallocate` itself).
>
> I don't think it's fair to say that they depend on the fallback. POSIX
> is very clear that posix_fallocate doesn't fail in the way musl fails
> here[1]. They (hopefully) expect it to behave as described in the
> standard and there's not much musl can do to alleviate the problem.
I don't follow what you mean by "POSIX is very clear...". Any
interface that has defined errors is permitted by POSIX to fail for
other implementation-defined reasons as long as the error codes used
for those reasons don't clash with the standard errors. In any case
there is no way musl can implement posix_fallocate if the underlying
kernel/filesystem does not support it.
I followed up on the flatpak bug tracker thread with some additional
info. But I'm not clear what functionality they actually need from
posix_fallocate because I don't even know what they're doing with it.
Rich
prev parent reply other threads:[~2017-06-12 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 3:22 Benjamin Slade
2017-06-05 12:46 ` Joakim Sindholt
[not found] ` <b6bc4261.dNq.dMV.B.pUrCBw@mailjet.com>
2017-06-11 20:57 ` Benjamin Slade
2017-06-12 17:55 ` Joakim Sindholt
2017-06-12 18:07 ` Rich Felker [this message]
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=20170612180740.GD1627@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).