From: Bob Copeland <email@bobcopeland.com>
To: x-lists@cqsat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel programming donts
Date: Wed, 4 Jan 2006 12:29:50 -0500 [thread overview]
Message-ID: <b6c5339f0601040929jcbf2aadheec806fb453e58dd@mail.gmail.com> (raw)
In-Reply-To: <BAY7-F20B9964B2E040C06705307C52F0@phx.gbl>
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
prev parent reply other threads:[~2006-01-04 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 17:19 J R
2006-01-04 17:29 ` Bob Copeland [this message]
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=b6c5339f0601040929jcbf2aadheec806fb453e58dd@mail.gmail.com \
--to=email@bobcopeland.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®