From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Nottingham Subject: Re: bonding: cannot remove certain named devices Date: Wed, 16 Aug 2006 09:38:11 -0400 Message-ID: <20060816133811.GA26471@nostromo.devel.redhat.com> References: <6KfTz-OX-11@gated-at.bofh.it> <6KfTA-OX-15@gated-at.bofh.it> <20060815.171002.104028951.davem@davemloft.net> <44E2BC9C.1000101@debian.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Miller , 7eggert@gmx.de, 7eggert@elstempel.de, shemminger@osdl.org, mitch.a.williams@intel.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from mx1.redhat.com ([66.187.233.31]:13221 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1750983AbWHPNij (ORCPT ); Wed, 16 Aug 2006 09:38:39 -0400 To: "Giacomo A. Catenazzi" Content-Disposition: inline In-Reply-To: <44E2BC9C.1000101@debian.org> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Giacomo A. Catenazzi (cate@debian.org) said: > > Are you willing to work to add the special case code necessary to > > handle whitespace characters in the device name over all of the kernel > > code and also all of the userland tools too? > > But if you don't handle spaces in userspace, you handle *, ?, [, ], $, > ", ', \ in userspace? Should kernel disable also these (insane device > chars) chars? Don't forget unicode characters! Seriously, while it might be insane to use some of these, I'm wondering if trying to filter names is more work than fixing the tools. Bill