Date: Mon, 12 Jan 2004 16:13:36 -0800
From: Stephen Hemminger <shemminger@osdl.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] restrict class names to valid file names
Message-Id: <20040112161336.3e147996.shemminger@osdl.org>
In-Reply-To: <20040113000514.GA4848@kroah.com>
References: <20040112151357.5c9702b7.shemminger@osdl.org>
	<20040113000514.GA4848@kroah.com>
Organization: Open Source Development Lab
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1052
Lines: 22

On Mon, 12 Jan 2004 16:05:14 -0800
Greg KH <greg@kroah.com> wrote:

> On Mon, Jan 12, 2004 at 03:13:57PM -0800, Stephen Hemminger wrote:
> > It is possible to name network devices with names like "my/bogus" or "." or ".."
> > which leaves /sys/class/net/ a mess.  Since other subsystems could have the same
> > problem, it made sense to me to enforce some restrictions in the class device
> > layer.
> > 
> > A lateer patch fixes the network device registration path because the
> > sysfs registration takes place after the register_netdevice call has taken place.
> 
> Heh, so you will have already "scrubbed" the name before you submit it
> to the driver core?  If so, why add this patch?

Because name won't be scrubbed for the rename case, and other class devices
probably have the same possible problem
-
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/