From: Mike Snitzer <snitzer@redhat.com>
To: Scotty Bauer <sbauer@eng.utah.edu>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org, agk@redhat.com
Subject: Re: dm ioctl: Access user-land memory through safe functions.
Date: Tue, 5 Jan 2016 16:13:10 -0500 [thread overview]
Message-ID: <20160105211310.GC30512@redhat.com> (raw)
In-Reply-To: <20160105201649.GA30512@redhat.com>
On Tue, Jan 05 2016 at 3:16pm -0500,
Mike Snitzer <snitzer@redhat.com> wrote:
> On Tue, Dec 08 2015 at 1:26pm -0500,
> Scotty Bauer <sbauer@eng.utah.edu> wrote:
>
> > Friendly ping, is anyone interested in this?
>
> The passed @user argument is flagged via __user so it can be
> deferenced directly. It does look like directly deferencing
> user->version is wrong.
>
> But even if such indirect access is needed (because __user flag is only
> applicable to @user arg, not the contained version member) we could more
> easily just do something like this no?:
>
> uint32_t __user *versionp = (uint32_t __user *)user->version;
> ...
> if (copy_from_user(version, versionp, sizeof(version)))
> return -EFAULT;
>
> I've staged the following, thanks:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.5&id=bffc9e237a0c3176712bcd93fc6a184a61e0df26
Alasdair helped me understand that we do need your original fix.
I've staged it for 4.5 (and stable@) here:
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.5&id=ead3db62bf10fe143bec99e7b7ff370d7a6d23ef
Thanks again,
Mike
next prev parent reply other threads:[~2016-01-05 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 18:11 [PATCH] " Scotty
2015-12-08 18:26 ` Scotty Bauer
2016-01-05 20:16 ` Mike Snitzer
2016-01-05 21:13 ` Mike Snitzer [this message]
2016-01-07 1:22 ` Scotty Bauer
2016-01-07 2:07 ` Mike Snitzer
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=20160105211310.GC30512@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sbauer@eng.utah.edu \
/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
Powered by JetHome