Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964818AbWADRTr (ORCPT ); Wed, 4 Jan 2006 12:19:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965070AbWADRTj (ORCPT ); Wed, 4 Jan 2006 12:19:39 -0500 Received: from bay7-f20.bay7.hotmail.com ([64.4.11.45]:14573 "EHLO hotmail.com") by vger.kernel.org with ESMTP id S964844AbWADRTh (ORCPT ); Wed, 4 Jan 2006 12:19:37 -0500 Message-ID: X-Originating-IP: [82.22.224.216] X-Originating-Email: [x-list-subscriptions@hotmail.com] Reply-To: x-lists@cqsat.com From: "J R" To: linux-kernel@vger.kernel.org Subject: kernel programming donts Date: Wed, 04 Jan 2006 09:19:36 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 04 Jan 2006 17:19:36.0923 (UTC) FILETIME=[09B19AB0:01C61153] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 889 Lines: 27 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/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/