From: Gary Thomas <gary@mlbassoc.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Fix stat64 on PPC
Date: Mon, 17 Mar 2008 11:11:11 -0600 [thread overview]
Message-ID: <47DEA62F.9030206@mlbassoc.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
Somehow, post 0.9.1, the stat64 structure on PPC got broken.
The attached patch fixes it.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1230 bytes --]
Index: linux-user/syscall_defs.h
===================================================================
--- linux-user/syscall_defs.h (revision 4115)
+++ linux-user/syscall_defs.h (revision 4116)
@@ -1131,18 +1131,19 @@
unsigned int st_uid;
unsigned int st_gid;
unsigned long long st_rdev;
- unsigned short pad0;
- long long st_size;
- int st_blksize;
- long long st_blocks; /* Number 512-byte blocks allocated. */
- int target_st_atime;
- unsigned int target_st_atime_nsec;
- int target_st_mtime;
- unsigned int target_st_mtime_nsec;
- int target_st_ctime;
- unsigned int target_st_ctime_nsec;
- unsigned int __unused4;
- unsigned int __unused5;
+ long long pad0;
+ long long st_size;
+ target_ulong st_blksize;
+ target_ulong pad1;
+ long long st_blocks; /* Number 512-byte blocks allocated. */
+ target_ulong target_st_atime;
+ target_ulong target_st_atime_nsec;
+ target_ulong target_st_mtime;
+ target_ulong target_st_mtime_nsec;
+ target_ulong target_st_ctime;
+ target_ulong target_st_ctime_nsec;
+ target_ulong __unused4;
+ target_ulong __unused5;
};
#elif defined(TARGET_M68K)
reply other threads:[~2008-03-17 17:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47DEA62F.9030206@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=qemu-devel@nongnu.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.