public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Don Raikes <don.raikes@oracle.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: RE: ot memory allocation question
Date: Sat, 20 Jul 2013 01:36:01 -0700 (PDT)	[thread overview]
Message-ID: <c70dd4df-3691-4e10-81f4-cbe6c501624d@default> (raw)
In-Reply-To: <8761w6wfrv.fsf@mushroom.PK5001Z>

Thanks for all the help.  Unfortunately my professor has been of limited help in the assignment.  So I have posted a message on the kernelnewbies list.
-----Original Message-----
From: Chris Brannon [mailto:chris@the-brannons.com] 
Sent: Friday, July 19, 2013 11:45 AM
To: Speakup is a screen review system for Linux.
Subject: Re: ot memory allocation question

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
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

  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
       ` Don Raikes [this message]
     ` 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=c70dd4df-3691-4e10-81f4-cbe6c501624d@default \
    --to=don.raikes@oracle.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).