From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13623 Path: news.gmane.org!.POSTED!not-for-mail From: Arnd Bergmann Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: Data structures defined by both linux and musl Date: Fri, 18 Jan 2019 22:09:26 +0100 Message-ID: References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1547845671 27437 195.159.176.226 (18 Jan 2019 21:07:51 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 18 Jan 2019 21:07:51 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-13639-gllmg-musl=m.gmane.org@lists.openwall.com Fri Jan 18 22:07:47 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1gkbMg-00071C-HR for gllmg-musl@m.gmane.org; Fri, 18 Jan 2019 22:07:46 +0100 Original-Received: (qmail 5270 invoked by uid 550); 18 Jan 2019 21:09:55 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 5249 invoked from network); 18 Jan 2019 21:09:55 -0000 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=S3muL4+9Oq/qGlc2psRmLNCWm1pUFEjysj3AX+Ko2mI=; b=jKj1NIfQwo6yv/2QnhqOpCI0VZDFeKJMxBgPQp0PONYRoqrxgCWRgSJNU24YjS62yA wme6Q6lPECnWNiZU6EwskTpwYP7NxSOWQg+nuwrzz2jaYdEgdnSids7Pku0wbZrDqLAF eU4A6qtxsVPzR8DANx38/OMA3pV9CIsSPuoufkMn4cdjDFhsFLh42wt59x+Oq7/aa7vu aKFxwWLINzfLItR4L3/NpR0RdzVazhSmd0Wg60ssOWdrm3ql+2qcyEIv4qTkaoxbCPIg sN2qzI2eGFnVfHdYjH3RLAFwCajuyS5PDZIPHGmnkHsDNp00svqAc2MmX/lsfeDHbRQZ Vocg== X-Gm-Message-State: AJcUukc8eBJu7CgLwujViEVKKpwLaOaiS6Gw5p6T+cRxmdtQD55G66lE yCFZoaLUaaz3kIVeBmE5fa+x7SD0zU4fMZviXKuMzA== X-Google-Smtp-Source: ALg8bN551XxiOR0Q2SRuStBPkH+HxNPBCQbb88ty7WqBmC2kt2Y4tEQZPUzj3aUK6168py6OchwLEGNBcLrEg/MYmPI= X-Received: by 2002:a0c:f50c:: with SMTP id j12mr16940171qvm.149.1547845783158; Fri, 18 Jan 2019 13:09:43 -0800 (PST) In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:13623 Archived-At: On Fri, Jan 18, 2019 at 8:48 PM A. Wilcox 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