From: Greg KH <gregkh@linuxfoundation.org>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org, fmhess@users.sourceforge.net,
abbotti@mev.co.uk
Subject: Re: [PATCH v2] staging: comedi: remove __user annotation inside of struct's
Date: Wed, 9 May 2012 13:42:10 -0700 [thread overview]
Message-ID: <20120509204210.GA22184@kroah.com> (raw)
In-Reply-To: <201205090936.03921.hartleys@visionengravers.com>
On Wed, May 09, 2012 at 09:36:03AM -0700, H Hartley Sweeten wrote:
> Remove the __user annotations in the struct definitions in
> comedi.h.
>
> These structs are used to pass information from user-space
> to kernel-space. The copy_from_user and copy_to_user functions
> are used to transfer the data between the address spaces.
>
> The drivers then use the information internally under the
> assumption that they are kernel-space objects. Having the
> __user annotations inside the structs produces a number of
> sparse warnings of the type:
>
> warning: dereference of noderef expression
>
> According to Grek Kroah-Hartman:
>
> "When the kernel exports .h files, stuff like this should work
> "automatically", so there is no need to not put __user markings."
Wait, for some reason I thought you were adding __user markings, not
removing them from the structures. That is why I said the above
statement.
Why again are you removing them? Didn't you just cause more sparse
warnings to pop up?
confused,
greg k-h
next prev parent reply other threads:[~2012-05-09 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 16:36 H Hartley Sweeten
2012-05-09 20:40 ` Greg KH
2012-05-09 20:42 ` Greg KH [this message]
2012-05-09 21:21 ` H Hartley Sweeten
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=20120509204210.GA22184@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®