Re: [PATCH] driver core: Add the ability to unbind drivers to devices from userspace

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > > It is not a work around. These are text attributes meant for human
> > > use.  Humans have a hard time cleaning up things they can't see. And
> > > the failure mode for this is awful, your attribute won't set but
> > > everything on the screen looks fine.
> > 
> > Kernel is not a place to be user friendly. Or do you propose stripping whitespace
> > for open(), too? File called "foo.txt    " certainly *is* going to be confusing, but it should be allowed at kernel level.
> 
> open is not made for human use, it is used by programs and only
> indirectly by humans. sysfs variables are used by directly humans.

Both are kernel interfaces; I can use open() by hand just fine...

> > Now... echo foo > /sys/var does not properly report errors. Thats bad, but it needs to
> > be fixed in bash.
> 
> It is going to take a lot more code to return an error that a
> parameter didn't match because of extra white space that it would take
> to simply remove the whitespace.

I believe we do correctly report errors in write() calls already. Bash
not reporting them to the user is different problem.
								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address
-
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/