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: kernel oops
Date: Thu, 18 Jul 2013 23:07:09 -0700 (PDT)	[thread overview]
Message-ID: <0da38b23-f8a4-42ba-8f26-94b1e69a549a@default> (raw)
In-Reply-To: <20130719055130.GA13329@jdc.jasonjgw.net>

I agree that a good knowledge of c is a prerequisite for this kind of programming, but this is my first semester in theis masters program, and they threw us into the deep end pretty quickly.

I had a c class about 8 years ago and have forgotten a lot of it.
I am also taking a c++ class this summer, but it isn't getting into any of this stuff yet.
-----Original Message-----
From: Jason White [mailto:jason@jasonjgw.net] 
Sent: Thursday, July 18, 2013 10:51 PM
To: speakup@linux-speakup.org
Subject: Re: OT: kernel oops

Don Raikes <don.raikes@oracle.com> wrote:
> Ok so I get it, but the problem is that I am hooking into the sys_write systemcall, and it is by default cast to a const.
> 
> If I leave it as is, and cast the buf in my copy_to_user to a (char*) should that work?
> 

Try (void __user *)
which according to Linux Device Drivers is the correct type for copy_to_user.
> Sorry my knowledge of c is very limited :)

I would suggest reading a good book on the subject in that case.

A good knowledge of C is a prerequisite for what you are doing.

_______________________________________________
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
 ` Jason White
 ` Chris Brannon
   ` Don Raikes
   ` Don Raikes
   ` Jason White
     ` Don Raikes
       ` Jason White
         ` Don Raikes
           ` Jason White
             ` 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=0da38b23-f8a4-42ba-8f26-94b1e69a549a@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).