From: Jens Axboe <axboe@kernel.dk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
Ramprasad Chinthekindi <rchinthekindi@stec-inc.com>,
Akhil Bhansali <abhansali@stec-inc.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch 1/4] skd: use regular version of copy_from_user()
Date: Fri, 13 Sep 2013 17:00:55 +0000 [thread overview]
Message-ID: <523344C7.60303@kernel.dk> (raw)
In-Reply-To: <20130913075523.GE19211@elgon.mountain>
On 09/13/2013 01:55 AM, Dan Carpenter wrote:
> The other __copy_from_user() calls have access_ok() checks so they are
> fine, but these two don't have the check.
Thanks Dan, applied this one and the other two. Did you miss sending one
out? I don't see a 3/4 patch.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
Ramprasad Chinthekindi <rchinthekindi@stec-inc.com>,
Akhil Bhansali <abhansali@stec-inc.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch 1/4] skd: use regular version of copy_from_user()
Date: Fri, 13 Sep 2013 11:00:55 -0600 [thread overview]
Message-ID: <523344C7.60303@kernel.dk> (raw)
In-Reply-To: <20130913075523.GE19211@elgon.mountain>
On 09/13/2013 01:55 AM, Dan Carpenter wrote:
> The other __copy_from_user() calls have access_ok() checks so they are
> fine, but these two don't have the check.
Thanks Dan, applied this one and the other two. Did you miss sending one
out? I don't see a 3/4 patch.
--
Jens Axboe
next prev parent reply other threads:[~2013-09-13 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 7:55 [patch 1/4] skd: use regular version of copy_from_user() Dan Carpenter
2013-09-13 7:55 ` Dan Carpenter
2013-09-13 17:00 ` Jens Axboe [this message]
2013-09-13 17:00 ` Jens Axboe
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=523344C7.60303@kernel.dk \
--to=axboe@kernel.dk \
--cc=abhansali@stec-inc.com \
--cc=dan.carpenter@oracle.com \
--cc=jmoyer@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rchinthekindi@stec-inc.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.