From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Unhandled fault: page domain fault (0x81b) at 0x00e41008
Date: Fri, 22 Jan 2016 19:34:09 +0000 [thread overview]
Message-ID: <20160122193408.GE19062@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <56A27C00.5060004@free.fr>
On Fri, Jan 22, 2016 at 07:59:12PM +0100, Mason wrote:
> On 22/01/2016 18:48, Russell King - ARM Linux wrote:
> > No, you _must_ use the correct functions to access userspace.
> > Userspace accesses are marked in a special way that allows the kernel
> > to fix up non-present pages.
>
> Do you mean calling might_fault() ?
No, I explicitly listed the functions you should be using in my
original reply.
> > Normal accesses may appear to work but
> > will eventually oops the kernel when the page is unmapped or is marked
> > read-only and you try to write to it.
>
> I'll have to check again how the code was before I made
> my silly changes, but it's been in production for years,
> and we've never had any problem in that module...
> (But I suppose something broken can appear to work for
> months or years.)
>
> > Please don't think of using __copy_from_user() et.al. either - those
> > are there for code which knows what it's doing and has pre-validated
> > the accesses.
>
> I do call access_ok() before doing the copy.
It's possible to use access_ok() + __copy_from_user(), but that's
really frowned upon because it's _very_ easy to get it wrong - and
then you have a security bug.
> > Drivers and platform code should use copy_from_user()/copy_to_user()
> > to block-copy data to/from userspace, and get_user()/put_user() to
> > copy individual bytes, shorts and int/longs. (It doesn't matter
> > who you are, that's the official guidance.)
>
> The problem is that the kernel module's API is already set
> in stone, and it requires block copies with specific access
> sizes, e.g. block_copy8, block_copy16, block_copy32.
Rather than making these statements, you need to explain what, how
and why.
What do these "block_copy8, block_copy16, block_copy32" functions
do? Does the "8", "16" and "32" refer to the access size? Why do
they need to make accesses to userspace using these specific sizes?
What causes this restriction?
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-01-22 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 17:37 Unhandled fault: page domain fault (0x81b) at 0x00e41008 Mason
2016-01-22 17:48 ` Russell King - ARM Linux
2016-01-22 18:59 ` Mason
2016-01-22 19:34 ` Russell King - ARM Linux [this message]
2016-01-22 23:15 ` Mason
2016-01-22 23:57 ` Russell King - ARM Linux
2016-01-23 11:14 ` Mason
2016-01-23 11:34 ` Russell King - ARM Linux
2016-01-23 20:53 ` Mason
2016-01-23 22:46 ` Mason
2016-01-23 23:59 ` Russell King - ARM Linux
2016-01-24 13:27 ` Mason
2016-01-27 10:36 ` Mason
2016-01-27 10:48 ` Russell King - ARM Linux
2016-01-27 12:04 ` Mason
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=20160122193408.GE19062@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).