kernel programming donts

kernel programming donts

[J R]

Is there a list of kernel / driver development "donts" documented in 1
place. I'm looking for examples of coding errors that would lead to
leaks,  crashes or vulnerabilities - like using tainted data from
copy_from_user() in an unsafe way. Have these things been collected in 1 
place?

The only thing I could find was the coding style document - but I'm looking 
for more meaty problems than commenting style.

Thanks
-J


--
www.cqsat.com
jr at that domain

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

Re: kernel programming donts

[Bob Copeland]

On 1/4/06, J R <x-list-subscriptions@hotmail.com> wrote:
>
> Is there a list of kernel / driver development "donts" documented in 1
> place. I'm looking for examples of coding errors that would lead to
> leaks,  crashes or vulnerabilities - like using tainted data from
> copy_from_user() in an unsafe way. Have these things been collected in 1
> place?

There are some documents on kerneljanitors.org, for example:

http://kerneljanitors.org/drivers-dosdonts/index.html