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 09:08:49 -0700 (PDT) [thread overview]
Message-ID: <eb23fc6b-f2e8-47e3-b23f-a3ef8beb467d@default> (raw)
In-Reply-To: <87mwpjx3ae.fsf@mushroom.PK5001Z>
Thanks chris,
I will give that a try later today. I need to get some "real" work done today. This class has been consuming almost all of my time this week.
-----Original Message-----
From: Chris Brannon [mailto:chris@the-brannons.com]
Sent: Thursday, July 18, 2013 9:05 AM
To: Speakup is a screen review system for Linux.
Subject: Re: OT: kernel oops
Don Raikes <don.raikes@oracle.com> writes:
> The section of code that is having problems looks like this:
*SNIP*
> if (copy_from_user(&tbuf, buf, count))
This line is your problem. You are passing a pointer-to-pointer-to-character (char **) as the first argument to copy_from_user, but you should be passing char * instead. So ditch the ampersand, and all will be right with the world!
I could give you a thorough explanation of why this is failing, if you like, but to make a long story short, this line of code is smashing the stack!
I'm always happy to help.
-- Chris
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent 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 [this message]
` Don Raikes
` Jason White
` Don Raikes
` Jason White
` Don Raikes
` Jason White
` 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=eb23fc6b-f2e8-47e3-b23f-a3ef8beb467d@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).