Advertisement
Interested in hardware, diags, validation, Linux, C, ARM, Microcode and low level programming and blazing networks?
| |||||||||||||
|
| |||||||||||||
grsecurity 2.1.0 and kernel vulnerabilitiesgrsecurity 2.1.0 and kernel vulnerabilitiesPosted Jan 7, 2005 22:17 UTC (Fri) by iabervon (subscriber, #722)Parent article: grsecurity 2.1.0 and kernel vulnerabilities
It seems to me like sparse should be able to identify cases where copy_*_user() is called with a signed type as the size, since there's probably no cases where this would be desireable (it might be legitimate if the sign is checked beforehand, but any case where a negative number should be treated differently from a positive one is a sufficiently ugly interface that needing something explicit would serve to clarify what was going on).
(Log in to post comments)
|
|
||||||||||||