From: Jonathan Corbet <corbet@lwn.net>
To: Scotty Bauer <sbauer@eng.utah.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Accessing user-land memory without safe functions
Date: Thu, 3 Dec 2015 17:12:37 -0700 [thread overview]
Message-ID: <20151203171237.73877893@lwn.net> (raw)
In-Reply-To: <5660AC06.8080300@eng.utah.edu>
On Thu, 3 Dec 2015 13:54:30 -0700
Scotty Bauer <sbauer@eng.utah.edu> wrote:
> Since I've seen this a couple times now I'm wondering if my
> understanding of touching user-land memory is flawed.
>
> For the above example Ioctl, the proper way to get access to those fields
> through the safe copy_from_user or get_user() functions, correct?
>
> I'm wondering if I should submit patches to fix the issues I've found,
> but now I'm doubting whether they're really issues at all.
They sound like bugs to me, though it would be easier to say for sure with
a pointer to a specific function in the kernel source. Please point
something out, or, perhaps better, send a patch fixing one of them.
Thanks,
jon
next prev parent reply other threads:[~2015-12-04 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 20:54 Accessing user-land memory without safe functions Scotty Bauer
2015-12-04 0:12 ` Jonathan Corbet [this message]
2015-12-04 0:32 ` Scotty Bauer
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=20151203171237.73877893@lwn.net \
--to=corbet@lwn.net \
--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