From: Justin Cormack <justin@specialbusservice.com>
To: musl@lists.openwall.com
Subject: Re: stat64 on mips
Date: Mon, 30 Dec 2013 22:02:19 +0000 [thread overview]
Message-ID: <CAK4o1WzOU-RqvoYwDtsQV-wyi02d149iObhUmHsH4TTt8gTzRQ@mail.gmail.com> (raw)
In-Reply-To: <20131230212953.GL24286@brightrain.aerifal.cx>
On Mon, Dec 30, 2013 at 9:29 PM, Rich Felker <dalias@aerifal.cx> wrote:
> On Mon, Dec 30, 2013 at 06:20:46PM +0000, Justin Cormack wrote:
>> MIPS is the most confusing architecture, but as far as I can make out,
>> the definition of struct stat64 that Musl has is probably the right
>> one for mips n32 but wrong for mips o32 which should be
>>
>> struct stat {
>> unsigned long st_dev;
>> unsigned long __st_pad0[3];
>> unsigned long long st_ino;
>> mode_t st_mode;
>> nlink_t st_nlink;
>> uid_t st_uid;
>> gid_t st_gid;
>> unsigned long st_rdev;
>> unsigned long __st_pad1[3];
>> long long st_size;
>> time_t st_atime;
>> unsigned long st_atime_nsec;
>> time_t st_mtime;
>> unsigned long st_mtime_nsec;
>> time_t st_ctime;
>> unsigned long st_ctime_nsec;
>> unsigned long st_blksize;
>> unsigned long __st_pad2;
>> long long st_blocks;
>> };
>>
>> It does appear that the syscalls for the two ABIs differ in this...
>
> This structure is identical to the one in musl except that it has
> 32-bit dev_t plus padding in place of 64-bit dev_t, and the musl
> version has reserved space at the end. Can you check whether the dev_t
> issue is actually a problem (it might be, based on endianness, and if
> so I think it would require ugly fixups in userspace)?
Ah no, my mistake, you are right, the padding seems correct and I was
getting confused as usual by dev_t. However the 64 bit dev_t is a
problem on bigendian mips.
(Whats the reason for Musl using 64 bit dev_t? glibc compatibility?)
justin
next prev parent reply other threads:[~2013-12-30 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 18:20 Justin Cormack
2013-12-30 21:29 ` Rich Felker
2013-12-30 22:02 ` Justin Cormack [this message]
2013-12-30 22:03 ` Rich Felker
2013-12-30 22:10 ` Justin Cormack
2013-12-30 22:13 ` Rich Felker
2013-12-30 22:15 ` Justin Cormack
2013-12-30 22:53 ` Justin Cormack
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=CAK4o1WzOU-RqvoYwDtsQV-wyi02d149iObhUmHsH4TTt8gTzRQ@mail.gmail.com \
--to=justin@specialbusservice.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).