mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: musl@lists.openwall.com
Subject: Re: Re: Data structures defined by both linux and musl
Date: Fri, 18 Jan 2019 22:09:26 +0100	[thread overview]
Message-ID: <CAK8P3a0v9PNi21ED9kNarN9ZghEZjA4CT0n3N-fgP5+FzXX0NA@mail.gmail.com> (raw)
In-Reply-To: <e179210f-2010-3fb6-b324-b9c504610d26@adelielinux.org>

On Fri, Jan 18, 2019 at 8:48 PM A. Wilcox <awilfox@adelielinux.org> wrote:
>
> On 01/18/19 10:50, Arnd Bergmann wrote:
> > On Wed, 19 Dec 2018, Rich Felker wrote:
> >>> The takeaway is that we probably need to add new definitions for
> >>> flock64, statfs, stat, termios, {msg,sem,shm}{buf,info,id_ds}, ipc_perm,
> >>
> >> Not clear on how flock[64?] is affected.
> >
> > In my list, I had mentioned that the kernel's flock64 is different
> > from musl's flock structure on sparc64 (which has an extra
> > padding field) and on mips (I may have been mistaken there,
> > only flock differs on mips32, flock64 is apparently fine).
> >
> > If we don't care about musl on sparc, there may be no need to
> > do anything here.
>
> We have a sparc64 port in progress for musl.  It's in the planning
> stages, and the goal was to get something shipping in late 2019.
>
> As usual, I guess we're going to be too little, too late.

Have you thought about how to handle timeval and flock64 here?
In both cases, the generic structure definition is different between
sparc64 kernels and the rest of the world including all other 64-bit
architectures and the musl definition.

      Arnd


  reply	other threads:[~2019-01-18 21:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 19:41 Arnd Bergmann
2018-12-20  0:30 ` Rich Felker
2018-12-20 10:33   ` Szabolcs Nagy
2018-12-20 18:08     ` Rich Felker
2019-01-18 16:50 ` Arnd Bergmann
2019-01-18 19:48   ` A. Wilcox
2019-01-18 21:09     ` Arnd Bergmann [this message]
2019-01-18 17:06 ` Arnd Bergmann
2019-01-18 18:55   ` Rich Felker
2019-01-18 21:07     ` Arnd Bergmann

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=CAK8P3a0v9PNi21ED9kNarN9ZghEZjA4CT0n3N-fgP5+FzXX0NA@mail.gmail.com \
    --to=arnd@arndb.de \
    --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).