From: Tobias Klauser <tklauser@distanz.ch>
To: Anil Belur <askb23@gmail.com>
Cc: dan.carpenter@oracle.com, bjorn@mork.no, silvio.fricke@gmail.com,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] staging: vt6655: ioctl.c - missing __user annotation
Date: Wed, 30 Jul 2014 13:32:46 +0200 [thread overview]
Message-ID: <20140730113246.GF10301@distanz.ch> (raw)
In-Reply-To: <1406716919-13595-1-git-send-email-askb23@gmail.com>
On 2014-07-30 at 12:41:59 +0200, Anil Belur <askb23@gmail.com> wrote:
> From: Anil Belur <askb23@gmail.com>
This line is only necessary if you're sending the patch on behalf of
someone else. Also there is no need to have the 1/1 in the Subject line
as you're only sending one patch, not an entire series.
> v2:
> - private_ioctl() internally calls copy_{to,from}_user() and does
> not use '__user' which gives out several sparse warnings
> - this patch adds __user annotation to the data member of struct
> tagSCmdRequest as suggested by tklauser@distanz.ch
Patch history should go below the '---' as it doesn't need to be
included in the commit message.
> - sparse warnings fixed:
> drivers/staging/vt6655/ioctl.c:78:51: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:78:51: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:78:51: got void *data
It's sufficient to only show one instance of the sparse warning in the
commit message, since they're all the same.
> drivers/staging/vt6655/ioctl.c:117:55: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:117:55: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:117:55: got void *data
> drivers/staging/vt6655/ioctl.c:149:46: warning: incorrect type in argument 1 (different address spaces)
> drivers/staging/vt6655/ioctl.c:149:46: expected void [noderef] asn:1>*to
> drivers/staging/vt6655/ioctl.c:149:46: got void *data
> drivers/staging/vt6655/ioctl.c:166:51: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:166:51: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:166:51: got void *data
> drivers/staging/vt6655/ioctl.c:212:50: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:212:50: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:212:50: got void *data
> drivers/staging/vt6655/ioctl.c:276:38: warning: incorrect type in argument 1 (different address spaces)
> drivers/staging/vt6655/ioctl.c:276:38: expected void [noderef] asn:1>*to
> drivers/staging/vt6655/ioctl.c:276:38: got void *data
> drivers/staging/vt6655/ioctl.c:292:38: warning: incorrect type in argument 1 (different address spaces)
> drivers/staging/vt6655/ioctl.c:292:38: expected void [noderef] asn:1>*to
> drivers/staging/vt6655/ioctl.c:292:38: got void *data
> drivers/staging/vt6655/ioctl.c:300:48: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:300:48: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:300:48: got void *data
> drivers/staging/vt6655/ioctl.c:344:38: warning: incorrect type in argument 1 (different address spaces)
> drivers/staging/vt6655/ioctl.c:344:38: expected void [noderef] asn:1>*to
> drivers/staging/vt6655/ioctl.c:344:38: got void *data
> drivers/staging/vt6655/ioctl.c:353:38: warning: incorrect type in argument 1 (different address spaces)
> drivers/staging/vt6655/ioctl.c:353:38: expected void [noderef] asn:1>*to
> drivers/staging/vt6655/ioctl.c:353:38: got void *data
> drivers/staging/vt6655/ioctl.c:360:38: warning: incorrect type in argument 1 (different address spaces)
> drivers/staging/vt6655/ioctl.c:360:38: expected void [noderef] asn:1>*to
> drivers/staging/vt6655/ioctl.c:360:38: got void *data
> drivers/staging/vt6655/ioctl.c:401:49: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:401:49: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:401:49: got void *data
> drivers/staging/vt6655/ioctl.c:424:49: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:424:49: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:424:49: got void *data
> drivers/staging/vt6655/ioctl.c:440:49: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:440:49: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:440:49: got void *data
> drivers/staging/vt6655/ioctl.c:457:49: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:457:49: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:457:49: got void *data
> drivers/staging/vt6655/ioctl.c:479:54: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:479:54: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:479:54: got void *data
> drivers/staging/vt6655/ioctl.c:563:38: warning: incorrect type in argument 1 (different address spaces)
> drivers/staging/vt6655/ioctl.c:563:38: expected void [noderef] asn:1>*to
> drivers/staging/vt6655/ioctl.c:563:38: got void *data
> drivers/staging/vt6655/ioctl.c:571:52: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:571:52: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:571:52: got void *data
> drivers/staging/vt6655/ioctl.c:615:38: warning: incorrect type in argument 1 (different address spaces)
> drivers/staging/vt6655/ioctl.c:615:38: expected void [noderef] asn:1>*to
> drivers/staging/vt6655/ioctl.c:615:38: got void *data
> drivers/staging/vt6655/ioctl.c:631:53: warning: incorrect type in argument 2 (different address spaces)
> drivers/staging/vt6655/ioctl.c:631:53: expected void const [noderef] asn:1>*from
> drivers/staging/vt6655/ioctl.c:631:53: got void *data
>
> Signed-off-by: Anil Belur <askb23@gmail.com>
> ---
> drivers/staging/vt6655/iocmd.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/vt6655/iocmd.h b/drivers/staging/vt6655/iocmd.h
> index e499f1b..dd12498 100644
> --- a/drivers/staging/vt6655/iocmd.h
> +++ b/drivers/staging/vt6655/iocmd.h
> @@ -100,7 +100,7 @@ typedef enum tagWZONETYPE {
> #pragma pack(1)
> typedef struct tagSCmdRequest {
> u8 name[16];
> - void *data;
> + void __user *data;
> u16 wResult;
> u16 wCmdCode;
> } SCmdRequest, *PSCmdRequest;
> --
> 1.9.1
prev parent reply other threads:[~2014-07-30 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 10:41 [PATCH v2 1/1] staging: vt6655: ioctl.c - missing __user annotation Anil Belur
2014-07-30 11:32 ` Tobias Klauser [this message]
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=20140730113246.GF10301@distanz.ch \
--to=tklauser@distanz.ch \
--cc=askb23@gmail.com \
--cc=bjorn@mork.no \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=silvio.fricke@gmail.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