mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J R" <x-list-subscriptions@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernel programming donts
Date: Wed, 04 Jan 2006 09:19:36 -0800	[thread overview]
Message-ID: <BAY7-F20B9964B2E040C06705307C52F0@phx.gbl> (raw)


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/


             reply	other threads:[~2006-01-04 17:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 17:19 J R [this message]
2006-01-04 17:29 ` Bob Copeland

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=BAY7-F20B9964B2E040C06705307C52F0@phx.gbl \
    --to=x-list-subscriptions@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x-lists@cqsat.com \
    /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

all inboxes | Powered by JetHome®