Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758289AbYHFIEb (ORCPT ); Wed, 6 Aug 2008 04:04:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756138AbYHFIEH (ORCPT ); Wed, 6 Aug 2008 04:04:07 -0400 Received: from zone0.gcu-squad.org ([212.85.147.21]:12152 "EHLO services.gcu-squad.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756136AbYHFIEE (ORCPT ); Wed, 6 Aug 2008 04:04:04 -0400 Date: Wed, 6 Aug 2008 09:31:18 +0200 From: Jean Delvare To: Greg KH Cc: Milton Miller , Michael Ellerman , linux-kernel , Jesse Barnes , Andrew Morton , linux-pci@vger.kernel.org Subject: Re: [PATCH/RFC] pci: dynids.use_driver_data considered harmful Message-ID: <20080806093118.05396ad4@hyperion.delvare> In-Reply-To: <20080717070759.GE22090@kroah.com> References: <20080712041137.GA5933@kroah.com> <0a67ecbf69649dce778db1b463e59c3a@bga.com> <20080717070759.GE22090@kroah.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.10.6; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2055 Lines: 52 Hi Greg, On Thu, 17 Jul 2008 00:07:59 -0700, Greg KH wrote: > On Wed, Jul 16, 2008 at 05:18:18AM -0500, Milton Miller wrote: > > > > Greg, > > > > Please respond to this email and explain why the patch > > > > pci: dynids.use_driver_data considered harmful > > > > http://www.ussg.iu.edu/hypermail/linux/kernel/0807.1/index.html#2188 > > > > should not be applied. I am not arguing the correctness of > > the removed code, rather its utility and benefit to the linux > > community. > > (...) I'll try to get > to this by Monday, but my original point still stands, this was > implemented for a reason, Not a good enough argument, sorry. There have been many cases in the past where code has been withdrawn after some times because we realized that we got it wrong in the first place. So, please explain what the current code is good for. Honestly, my initial reaction to Milton's proposal was "what an idiot, this flag is there for an obvious safety reason and we don't want to remove it" but after reading both his arguments and the code, I found that I have nothing to backup my claim. If you do, please let us know your technical reasons. > saying that not enough drivers use it properly > does not make the need for it to go away. It is required for them, so > perhaps the other 419 drivers also need to have the flag set. That's > pretty trivial to do, right? If you are suggesting to blindly set the flag to all PCI drivers (or even just all the ones which make use of the driver_data field - doesn't make a difference), this simply shows how useless this flag is. If you don't, then one would have to check the code of all drivers and add validation code for the driver_data value; but then this no longer falls into the "trivial" category. Thanks, -- Jean Delvare -- 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/