From: Trevor Woerner <mips081@vtnet.ca>
To: linux-mips@linux-mips.org
Subject: 64-bit sysinfo
Date: Thu, 12 Jun 2003 06:59:26 -0400 [thread overview]
Message-ID: <200306120659.26501.mips081@vtnet.ca> (raw)
Hi everyone,
(good to see some familiar and friendly faces from the PPC list! :-)
I ran into a problem yesterday and I just don't know how I'm going to
approach solving it.
I compiled a 64-bit MIPS kernel, then built a busybox-based ramdisk. At
first I couldn't get busybox's 'init' to work but later solved it by
disabling the 'check_memory()' call.
Further investigation into why the 'check_memory()' call was failing
revealed a problem with the 'sysinfo()' system call. The kernel is
64-bit, therefore when it fills in the 'struct sysinfo' (as it does
when 'sys_meminfo()' is called) unsigned int's are 64 bits. But back in
userspace, the 'struct sysinfo' that gets allocated thinks that
unsigned int's are 32 bits.
This causes a crash if the 'struct sysinfo' is allocated on the stack
back in userspace, and causes seg faults if it's allocated in the .data
section (globally).
I'm crossing my fingers and hoping that my solution is to build all
user-space apps with some switch that will set the sizes of data types
to be the same between user space and kernel space. Does some such
option exist?
Trevor
next reply other threads:[~2003-06-12 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 10:59 Trevor Woerner [this message]
2003-06-12 11:35 ` 64-bit sysinfo Ralf Baechle
2003-06-12 12:07 ` Trevor Woerner
2003-06-12 12:27 ` Ralf Baechle
2003-06-12 21:36 ` Andrew Clausen
2003-06-12 11:44 ` Ralf Baechle
2003-06-12 12:02 ` Trevor Woerner
-- strict thread matches above, loose matches on Subject: below --
2003-06-12 11:19 Tor Arntsen
2003-06-12 12:04 ` Trevor Woerner
2003-06-12 12:04 ` Trevor Woerner
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=200306120659.26501.mips081@vtnet.ca \
--to=mips081@vtnet.ca \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox