Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261751AbVDOHLP (ORCPT ); Fri, 15 Apr 2005 03:11:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261752AbVDOHLP (ORCPT ); Fri, 15 Apr 2005 03:11:15 -0400 Received: from gaz.sfgoth.com ([69.36.241.230]:36606 "EHLO gaz.sfgoth.com") by vger.kernel.org with ESMTP id S261751AbVDOHLM (ORCPT ); Fri, 15 Apr 2005 03:11:12 -0400 Date: Fri, 15 Apr 2005 00:26:00 -0700 From: Mitchell Blank Jr To: Ted Kremenek Cc: linux-kernel@vger.kernel.org, Bryan Fulton , mc@cs.stanford.edu Subject: Re: [CHECKER] possible missing capability check in ioctl function, drivers/net/cris/eth_v10.c, kernel 2.6.11 Message-ID: <20050415072600.GA45259@gaz.sfgoth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.2.2 (gaz.sfgoth.com [127.0.0.1]); Fri, 15 Apr 2005 00:26:00 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 691 Lines: 17 Ted Kremenek wrote: > Currently we are looking primarily into the > ioctls in drivers/net, Just as a small aside, a little over five years ago (wow does time fly!) I did a manual audit for mistakes like this: http://lkml.org/lkml/2000/3/7/156 Not sure if that's relevant to your work your not...I'm not sure how you would can catch most of these errors statistically since a lot of the dangerous ioctl's were only for a single device. -Mitch - 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/