mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: statx syscall support
Date: Wed, 13 Dec 2017 15:20:09 -0500	[thread overview]
Message-ID: <20171213202009.GD1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPLrYESp6FZAOqo7FkjJ2J1UWLVdQ-B9YH5gMMP=NGjqYRA5wA@mail.gmail.com>

On Wed, Dec 13, 2017 at 10:54:07AM +0100, Daniel Cegiełka wrote:
> hi,
> is there any plan for statx syscall support in musl?
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/stat.h?h=v4.15-rc3
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/samples/statx/test-statx.c?h=v4.15-rc3

Nothing specific right now. The syscall number will of course be added
to syscall.h and available for direct use, but not much use without a
header defining the type. Of course <linux/statx.h> or whatever should
work assuming they don't define types that clash with libc.

In the long term, the statx interfaces may be useful for implementing
the POSIX stat function, especially on some archs (mainly mips) where
the existing stat syscalls are broken and need patching-up in
userspace. There's a vague future idea for a "musl 2 ABI" somewhere
down the line with clean, extensible, arch-independent definitions for
all the structs (and translation to/from kernel definitions in
wrappers) and using statx would certainly be helpful for that (but of
course would need fallbacks for older kernels unless this happens so
far in the future that older kernels are not relevant). All this would
be "under the hood", though, not as the primary public interface.

Rich


      reply	other threads:[~2017-12-13 20:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  9:54 Daniel Cegiełka
2017-12-13 20:20 ` 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=20171213202009.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).