From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "tytso@mit.edu" <tytso@mit.edu>
Cc: "leonro@mellanox.com" <leonro@mellanox.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: [Ksummit-discuss] [TECH TOPIC] How to encourage driver authors to annotate integer endianness properly
Date: Wed, 25 Oct 2017 09:47:25 +0000 [thread overview]
Message-ID: <1508924843.4165.6.camel@wdc.com> (raw)
Hello Ted,
As you most likely know endianness annotations like __be32 can be verified
by the static source code analyzer called sparse. These annotations are a
big help to verify whether endianness conversions in drivers are correct
(e.g. be32_to_cpu()). However, many driver authors either are not familiar
with sparse or do not use it to verify their work. I think we need a way
to encourage driver authors to pay attention to endianness annotations,
e.g. by letting the zero-day kernel test infrastructure verify endianness
annotations. Please consider to add this topic to the kernel summit agenda.
Thanks,
Bart.
next reply other threads:[~2017-10-25 9:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 9:47 Bart Van Assche [this message]
2017-10-25 9:54 ` [Ksummit-discuss] [TECH TOPIC] How to encourage driver authors to annotate integer endianness properly Greg KH
2017-10-25 10:06 ` Bart Van Assche
2017-10-25 10:13 ` greg
2017-10-25 10:16 ` Mark Brown
2017-10-25 12:56 ` Theodore Ts'o
2017-10-25 10:24 ` Leon Romanovsky
2017-10-25 10:38 ` greg
2017-10-25 12:11 ` Bart Van Assche
2017-10-25 10:18 ` Leon Romanovsky
2017-10-25 12:40 ` Alexey Dobriyan
2017-10-25 13:11 ` David Woodhouse
2017-10-25 16:16 ` Josh Triplett
2017-10-29 2:05 ` 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=1508924843.4165.6.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=leonro@mellanox.com \
--cc=tytso@mit.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).