Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757053Ab2HYJ3C (ORCPT ); Sat, 25 Aug 2012 05:29:02 -0400 Received: from mail-we0-f174.google.com ([74.125.82.174]:56724 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753849Ab2HYJ24 (ORCPT ); Sat, 25 Aug 2012 05:28:56 -0400 Date: Sat, 25 Aug 2012 12:31:49 +0300 From: Shmulik Ladkani To: Huang Shijie , dedekind1@gmail.com Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] mtd: cmdlinepart: fix the wrong check condition Message-ID: <20120825123149.3fafa4f4@halley> In-Reply-To: <1345925210-7500-1-git-send-email-shijie8@gmail.com> References: <1345925210-7500-1-git-send-email-shijie8@gmail.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; i686-pc-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: 2287 Lines: 64 Hi Huang, Artem, On Sat, 25 Aug 2012 16:06:50 -0400 Huang Shijie wrote: > diff --git a/drivers/mtd/cmdlinepart.c b/drivers/mtd/cmdlinepart.c > index fc960a3..216d751 100644 > --- a/drivers/mtd/cmdlinepart.c > +++ b/drivers/mtd/cmdlinepart.c > @@ -322,13 +322,16 @@ static int parse_cmdline_partitions(struct mtd_info *master, > struct cmdline_mtd_partition *part; > const char *mtd_id = master->name; > > + if (!mtd_id) > + return 0; > + > /* parse command line */ > if (!cmdline_parsed) > mtdpart_setup_real(cmdline); > > for(part = partitions; part; part = part->next) > { > - if ((!mtd_id) || (!strcmp(part->mtd_id, mtd_id))) > + if (!strcmp(part->mtd_id, mtd_id)) > { > for(i = 0, offset = 0; i < part->num_parts; i++) > { This changes the behavior of cmdling parsing, which might affect users expecting the old behavior. According to the remark above 'parse_cmdline_partitions': * It returns partitions for the requested mtd device, or * the first one in the chain if a NULL mtd_id is passed in. I think the purpose of a NULL 'mtd_id' was to support simple systems where there's a single driver and a single chip. The driver could be dumb, not specifying its 'mtd_info->name' (thus, a NULL mtd_id is passed). In this case, since the system is simply configured (one driver, one chip), 'parse_cmdline_partitions' simply disregards the "mtd-id" name specified in the cmdline string, allowing the user to present some arbitrary string there. I quite remember seeing this pattern somewhere in the past, I don't know if it's still used, though. Obviously if you have many drivers (and many chips) in a system, that won't work; the drivers must initialize 'mtd_info->name' and the user should present a cmdline that has explicit 'mtd-id's. So question is, would we like to prohibit NULL mtd-id? If so, we must make sure all drivers are properly assigning their 'mtd_info->name', and all users correctly specifying 'mtd-id' in their "mtdparts" cmdline strings. Regards, Shmulik -- 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/