From: "Michael S. Tsirkin" <mst@redhat.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] linux/types.h: Restore the ability to disable sparse endianness checks
Date: Mon, 9 Oct 2017 16:22:35 +0300 [thread overview]
Message-ID: <20171009162008-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20171006172353.16758-1-bart.vanassche@wdc.com>
On Fri, Oct 06, 2017 at 10:23:53AM -0700, Bart Van Assche wrote:
> The purpose of patch "linux/types.h: enable endian checks for all
> sparse builds" was to encourage driver authors to annotate
> endianness correctly in their drivers. However, since that patch
> went upstream no endianness annotations in drivers have been fixed.
> I think that this shows that the followed approach does not work,
> probably because several driver authors do not use sparse. Restore
> the ability to disable sparse endianness checks such that it
> becomes again easy to review other sparse diagnostics for people
> who want to analyze drivers they are not the author of.
>
> References: commit 05de97003c77 ("linux/types.h: enable endian checks for all sparse builds")
> Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
I still think the new default is good. You probably want ability to
disable these checks selectively for the specific drivers though. Makes
it easier to spot what needs to be fixed.
> ---
> include/uapi/linux/types.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/include/uapi/linux/types.h b/include/uapi/linux/types.h
> index 41e5914f0a8e..d3dcb0764c45 100644
> --- a/include/uapi/linux/types.h
> +++ b/include/uapi/linux/types.h
> @@ -23,7 +23,11 @@
> #else
> #define __bitwise__
> #endif
> +#if !defined(__CHECK_ENDIAN__) || __CHECK_ENDIAN__ != 0
> #define __bitwise __bitwise__
> +#else
> +#define __bitwise
> +#endif
>
> typedef __u16 __bitwise __le16;
> typedef __u16 __bitwise __be16;
> --
> 2.14.2
next prev parent reply other threads:[~2017-10-09 13:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 17:23 [PATCH] linux/types.h: Restore the ability to disable sparse endianness checks Bart Van Assche
2017-10-06 17:35 ` Christoph Hellwig
2017-10-06 17:43 ` Bart Van Assche
2017-10-16 9:33 ` Javier González
2017-10-09 13:22 ` Michael S. Tsirkin [this message]
2017-10-09 15:07 ` Bart Van Assche
2017-10-09 17:42 ` Michael S. Tsirkin
2017-10-10 16:38 ` Bart Van Assche
2017-10-16 13:34 ` Michael S. Tsirkin
2017-10-16 13:57 ` Bart Van Assche
2017-10-16 15:27 ` Michael S. Tsirkin
2017-10-16 15:36 ` Bart Van Assche
2017-10-16 16:50 ` Michael S. Tsirkin
2017-10-16 17:36 ` Bart Van Assche
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=20171009162008-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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