From: Greg KH <gregkh@linuxfoundation.org>
To: Andrey Utkin <andrey.krieger.utkin@gmail.com>
Cc: "Dilger, Andreas" <andreas.dilger@intel.com>,
OSUOSL Drivers <devel@driverdev.osuosl.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Drokin, Oleg" <oleg.drokin@intel.com>,
"HPDD-discuss@ml01.01.org" <HPDD-discuss@ml01.01.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: lustre/lnet/lnet/lib-move.c: memcpy with (struct iovec*)->iov_base, which is __user
Date: Sat, 17 Jan 2015 23:54:58 +0000 [thread overview]
Message-ID: <20150117235458.GA23280@kroah.com> (raw)
In-Reply-To: <CANZNk83Y5T75H86VZ4dMVigPiaVADZB60yc6QWWCWdJ=SdT+sQ@mail.gmail.com>
On Wed, Jan 07, 2015 at 02:28:12PM +0200, Andrey Utkin wrote:
> 2015-01-07 13:32 GMT+02:00 Dilger, Andreas <andreas.dilger@intel.com>:
> > On 2015/01/07, 1:36 AM, "Dan Carpenter" <dan.carpenter@oracle.com> wrote:
> >> 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.
> >
> > A patch was sent by Al on Dec 2 to replace iovec with kvec, in a thread
> > titled "[PATCH] staging:lustre:lnet: Incorrect type in assignment". Greg
> > replied on Dec 10 in another thread (also fixing this same warning) titled
> > "[PATCH] staging: lustre: Fix the warning messages about casting without
> > __user macro" that Al's patch was in the staging tree for 3.19-rc1.
>
> In current linux-next, I see none of the mentioned patches. Also I
> don't see them mentioned in GKH's merge commit "Merge tag
> 'staging-3.19-rc1'..."
> Is it ok?
Al's patch is now merged.
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Andrey Utkin <andrey.krieger.utkin@gmail.com>
Cc: "Dilger, Andreas" <andreas.dilger@intel.com>,
OSUOSL Drivers <devel@driverdev.osuosl.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Drokin, Oleg" <oleg.drokin@intel.com>,
"HPDD-discuss@ml01.01.org" <HPDD-discuss@ml01.01.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: lustre/lnet/lnet/lib-move.c: memcpy with (struct iovec*)->iov_base, which is __user
Date: Sat, 17 Jan 2015 15:54:58 -0800 [thread overview]
Message-ID: <20150117235458.GA23280@kroah.com> (raw)
In-Reply-To: <CANZNk83Y5T75H86VZ4dMVigPiaVADZB60yc6QWWCWdJ=SdT+sQ@mail.gmail.com>
On Wed, Jan 07, 2015 at 02:28:12PM +0200, Andrey Utkin wrote:
> 2015-01-07 13:32 GMT+02:00 Dilger, Andreas <andreas.dilger@intel.com>:
> > On 2015/01/07, 1:36 AM, "Dan Carpenter" <dan.carpenter@oracle.com> wrote:
> >> 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.
> >
> > A patch was sent by Al on Dec 2 to replace iovec with kvec, in a thread
> > titled "[PATCH] staging:lustre:lnet: Incorrect type in assignment". Greg
> > replied on Dec 10 in another thread (also fixing this same warning) titled
> > "[PATCH] staging: lustre: Fix the warning messages about casting without
> > __user macro" that Al's patch was in the staging tree for 3.19-rc1.
>
> In current linux-next, I see none of the mentioned patches. Also I
> don't see them mentioned in GKH's merge commit "Merge tag
> 'staging-3.19-rc1'..."
> Is it ok?
Al's patch is now merged.
next prev parent reply other threads:[~2015-01-17 23:54 UTC|newest]
Thread overview: 12+ 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-06 22:48 ` Andrey Utkin
2015-01-07 8:36 ` Dan Carpenter
2015-01-07 8:36 ` Dan Carpenter
2015-01-07 11:00 ` Andrey Utkin
2015-01-07 11:00 ` Andrey Utkin
2015-01-07 11:32 ` Dilger, Andreas
2015-01-07 11:32 ` Dilger, Andreas
2015-01-07 12:28 ` Andrey Utkin
2015-01-07 12:28 ` Andrey Utkin
2015-01-17 23:54 ` Greg KH [this message]
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=20150117235458.GA23280@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=andrey.krieger.utkin@gmail.com \
--cc=dan.carpenter@oracle.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 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.