mailing list of musl libc
 help / color / mirror / code / Atom feed
From: enh <enh@google.com>
To: musl@lists.openwall.com
Subject: [musl] preadv2/pwritev2
Date: Tue, 19 Oct 2021 19:24:26 -0700	[thread overview]
Message-ID: <CAJgzZoq2cEPCDfO7eDQXKqr4BKa=dnG0q=ouP+6yYaSxGaXKeg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

i've recently added preadv2(2) and pwritev2(2) wrappers to bionic, since we
had our first real prospective user come along, and they're mildly annoying
to use via syscall(3). unfortunately, this particular user also wants to be
able to compile for the host, and our glibc is years out of date, and our
current plan is to move to musl for the host[1].

anyway ... musl doesn't have preadv2/pwritev2. i couldn't see any
discussion on the mailing list, so i thought i'd ask whether this is just
because no-one's got round to it yet, or there's some policy[2] i'm not
aware of, or what? happy to send a patch if it's just a case of "we haven't
got round to/had a need for it yet".

____
1. TL;DR: being able to statically link without worrying about licensing is
very enticing, and gets us out of a lot of the compatibility issues we have
that made our last glibc update more trouble than it was worth, and means i
have no intention of getting us embroiled in another glibc update.
2. i've been maintaining bionic for years now, and don't think i've written
down our policy explicitly. this was definitely a borderline case from the
"number of users" perspective, but for me the "annoying to use with
syscall(2)" tipped me over the edge into adding them. amusingly [or not,
depending on how you feel about "bugs you get away with"], it also made me
realize that our pread/pwrite implementations for LP64 were wrong in that
they weren't zeroing the unused half of the register pair. so that was a
bonus :-)

[-- Attachment #2: Type: text/html, Size: 1710 bytes --]

             reply	other threads:[~2021-10-20  2:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  2:24 enh [this message]
2021-10-20 18:18 ` Rich Felker
2024-01-17 14:08   ` Leah Neukirchen
2024-01-18 15:54     ` Rich Felker

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='CAJgzZoq2cEPCDfO7eDQXKqr4BKa=dnG0q=ouP+6yYaSxGaXKeg@mail.gmail.com' \
    --to=enh@google.com \
    --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).