From: Maynard Johnson <maynardj@us.ibm.com>
To: linuxppc-dev@ozlabs.org
Subject: copy_from_user problem
Date: Mon, 25 Feb 2008 19:47:38 -0600 [thread overview]
Message-ID: <47C36FBA.1030600@us.ibm.com> (raw)
Hi,
I'm developing a kernel module that needs to parse the in-memory ELF
objects for a shared library (libc, to be specific). When running my
test on a 32-bit library, it works fine, but for a 64-bit library, the
very first copy_from_user() fails:
Elf64_Ehdr ehdr;
copy_from_user(&ehdr, location_of_lib, sizeof(Elf64_Ehdr);
I talked this over a bit with Will Schmidt. He determined that
access_ok (being done as a result of copy_from_user) was failing, but we
don't know why. I have 32-bit and 64-bit testcases that start up and
then pause, waiting for input. We look at the entry for libc in
/proc/<pid>/maps, and the permissions are the same for both 32-bit and
64-bit.
I've run this test on both a stock SLES 10 SP1 kernel and on 2.6.24.
I'm sure this is a user error, but for the life of me, I don't know what
I'm doing wrong.
Can anyone out there help?
Thanks.
Maynard Johnson
LTC POWER Toolchain
next reply other threads:[~2008-02-26 1:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 1:47 Maynard Johnson [this message]
2008-02-26 2:56 ` copy_from_user problem Benjamin Herrenschmidt
2008-02-26 14:49 ` Maynard Johnson
2008-02-26 15:01 ` Nathan Lynch
2008-02-26 15:30 ` Nathan Lynch
2008-02-26 15:36 ` Maynard Johnson
2008-02-26 23:22 ` Benjamin Herrenschmidt
2008-02-27 12:27 ` Maynard Johnson
2008-02-27 12:40 ` Arnd Bergmann
2008-02-27 20:24 ` Benjamin Herrenschmidt
2008-02-26 5:29 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 2:52 V MURAHARI
2005-08-11 11:02 ` Clemens Koller
2005-08-11 14:29 ` T Michael Turney
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=47C36FBA.1030600@us.ibm.com \
--to=maynardj@us.ibm.com \
--cc=linuxppc-dev@ozlabs.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.