[Ksummit-discuss] [TECH TOPIC] How to encourage driver authors to annotate integer endianness properly

Greg KH greg at kroah.com
Wed Oct 25 09:54:03 UTC 2017


On Wed, Oct 25, 2017 at 09:47:25AM +0000, Bart Van Assche wrote:
> 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. 

Driver subsystem maintainers should know this, and sparse reports should
be simple to run and notice these issues.  If you know of a subsystem
that is not paying attention to this, please let those maintainers know
and send patches to resolve the issues :)

thanks,

greg k-h


More information about the Ksummit-discuss mailing list