All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	greg@kroah.com, randy.dunlap@oracle.com, joe@perches.com
Subject: Re: [Oops 1/2]Something wrong with copy_from_user() function
Date: Sun, 1 May 2011 09:21:30 +0800	[thread overview]
Message-ID: <20110501012127.GA2378@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1104302311530.12035@pobox.suse.cz>

On Sat, Apr 30, 2011 at 11:13:10PM +0200, Jiri Kosina wrote:
> On Sat, 30 Apr 2011, Harry Wei wrote:
> 
> 
> wpa_set_keys() function (from staging drivers) in your kernel uses 
> copy_from_user() without proper bounds checking, and thus can overflow and 
> corrupt memory.
Hmmm, i see.

Thanks.
Harry Wei.
> 

  reply	other threads:[~2011-05-01  1:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30  6:13 [Oops 1/2]Something wrong with copy_from_user() function Harry Wei
2011-04-30 12:41 ` Andy Lutomirski
2011-04-30 21:13 ` Jiri Kosina
2011-05-01  1:21   ` Harry Wei [this message]
2011-05-01  2:39     ` Greg KH

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=20110501012127.GA2378@gmail.com \
    --to=jiaweiwei.xiyou@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=jkosina@suse.cz \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.