From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: ot memory allocation question
Date: Fri, 19 Jul 2013 11:44:52 -0700 [thread overview]
Message-ID: <8761w6wfrv.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <444275b3-63df-4577-835c-04ebc2830eb3@default> (Don Raikes's message of "Fri, 19 Jul 2013 09:00:18 -0700 (PDT)")
Don Raikes <don.raikes@oracle.com> writes:
> Chris,
>
> I gave that code segmentthat I sent a try, and it gives me an error in
> the copy_to_user call. It looks like none of the bytes were copied to
> the userspace buffer.
To be honest, this is way out of my league. I can give you another
pointer to more reading. I had to really dig for this one.
http://www.linux.it/kerneldocs/ksys/
Intercepting syscalls isn't (yet) part of my experience, so I can't be
of much further help.
-- Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Don Raikes
` Chris Brannon
` covici
` Chris Brannon
` covici
` Brian Buhrow
` Don Raikes
` Don Raikes
` Don Raikes
` Chris Brannon [this message]
` Don Raikes
` Jason White
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=8761w6wfrv.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--cc=speakup@linux-speakup.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 read-only IMAP folder(s) and NNTP newsgroup(s).