From: Andrew Morton <akpm@linux-foundation.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix _IOC_TYPECHECK sparse error
Date: Fri, 9 May 2014 13:59:49 -0700 [thread overview]
Message-ID: <20140509135949.feac79f3cb0ed9b13afbfeb4@linux-foundation.org> (raw)
In-Reply-To: <536C873E.8060408@xs4all.nl>
On Fri, 09 May 2014 09:43:58 +0200 Hans Verkuil <hverkuil@xs4all.nl> wrote:
> Andrew, can you merge this for 3.15 or 3.16 (you decide)? While it fixes a sparse error
> for the media subsystem, it is not really appropriate to go through our media tree.
>
> Thanks,
>
> Hans
>
>
> When running sparse over drivers/media/v4l2-core/v4l2-ioctl.c I get these
> errors:
>
> drivers/media/v4l2-core/v4l2-ioctl.c:2043:9: error: bad integer constant expression
> drivers/media/v4l2-core/v4l2-ioctl.c:2044:9: error: bad integer constant expression
> drivers/media/v4l2-core/v4l2-ioctl.c:2045:9: error: bad integer constant expression
> drivers/media/v4l2-core/v4l2-ioctl.c:2046:9: error: bad integer constant expression
>
> etc.
>
> The root cause of that turns out to be in include/asm-generic/ioctl.h:
>
> #include <uapi/asm-generic/ioctl.h>
>
> /* provoke compile error for invalid uses of size argument */
> extern unsigned int __invalid_size_argument_for_IOC;
> #define _IOC_TYPECHECK(t) \
> ((sizeof(t) == sizeof(t[1]) && \
> sizeof(t) < (1 << _IOC_SIZEBITS)) ? \
> sizeof(t) : __invalid_size_argument_for_IOC)
>
> If it is defined as this (as is already done if __KERNEL__ is not defined):
>
> #define _IOC_TYPECHECK(t) (sizeof(t))
>
> then all is well with the world.
>
> This patch allows sparse to work correctly.
>
> --- a/include/asm-generic/ioctl.h
> +++ b/include/asm-generic/ioctl.h
> @@ -3,10 +3,15 @@
>
> #include <uapi/asm-generic/ioctl.h>
>
> +#ifdef __CHECKER__
> +#define _IOC_TYPECHECK(t) (sizeof(t))
> +#else
> /* provoke compile error for invalid uses of size argument */
> extern unsigned int __invalid_size_argument_for_IOC;
> #define _IOC_TYPECHECK(t) \
> ((sizeof(t) == sizeof(t[1]) && \
> sizeof(t) < (1 << _IOC_SIZEBITS)) ? \
> sizeof(t) : __invalid_size_argument_for_IOC)
> +#endif
> +
> #endif /* _ASM_GENERIC_IOCTL_H */
Can't we use BUILD_BUG_ON() here? That's neater, more standard and
BUILD_BUG_ON() already has sparse handling.
next prev parent reply other threads:[~2014-05-09 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 7:43 Hans Verkuil
2014-05-09 20:59 ` Andrew Morton [this message]
2014-05-12 13:17 ` Hans Verkuil
-- strict thread matches above, loose matches on Subject: below --
2014-04-01 7:04 Hans Verkuil
2014-04-01 14:28 ` Josh Triplett
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=20140509135949.feac79f3cb0ed9b13afbfeb4@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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
Powered by JetHome