From: Dan Carpenter <dan.carpenter@oracle.com>
To: Andrey Utkin <andrey.krieger.utkin@gmail.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
HPDD-discuss@ml01.01.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
OSUOSL Drivers <devel@driverdev.osuosl.org>,
kernel-janitors@vger.kernel.org
Subject: Re: lustre/lnet/lnet/lib-move.c: memcpy with (struct iovec*)->iov_base, which is __user
Date: Wed, 07 Jan 2015 08:36:54 +0000 [thread overview]
Message-ID: <20150107083654.GK15033@mwanda> (raw)
In-Reply-To: <CANZNk80SoQZU994psVKuuGRGGHnGgO7bcFpPBQoGyg=CjW77xw@mail.gmail.com>
Didn't Al change these to kvec instead of iovec? You have to look at
the callers to figure out if it's actually a user space pointer or a
kernel pointer.
regards,
dan carpenter
next prev parent reply other threads:[~2015-01-07 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 22:48 lustre/lnet/lnet/lib-move.c: memcpy with (struct iovec*)->iov_base, which is __user Andrey Utkin
2015-01-07 8:36 ` Dan Carpenter [this message]
2015-01-07 11:00 ` Andrey Utkin
2015-01-07 11:32 ` Dilger, Andreas
2015-01-07 12:28 ` Andrey Utkin
2015-01-17 23:54 ` 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=20150107083654.GK15033@mwanda \
--to=dan.carpenter@oracle.com \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=andrey.krieger.utkin@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.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 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 NNTP newsgroup(s).