Re: bonding: cannot remove certain named devices

From: Giacomo A. Catenazzi
Date: Wed Aug 16 2006 - 02:33:03 EST

David Miller wrote:
> From: Bodo Eggert <7eggert@xxxxxxxxxxxx>
> Date: Wed, 16 Aug 2006 02:02:03 +0200
>> Stephen Hemminger <shemminger@xxxxxxxx> wrote:
>>> IMHO idiots who put space's in filenames should be ignored. As long as the
>>> bonding code doesn't throw a fatal error, it has every right to return
>>> "No such device" to the fool.
>> Maybe you should limit device names to eight uppercase characters and up to
>> three characters extension, too. NOT! There is no reason to artificially
>> impose limitations on device names, so don't do that.
> 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?

> No? Great, I'm glad that's settled.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at