| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] don't allow / in class device names |
| From: | Greg KH <greg@xxxxxxxxx> |
| Date: | Fri, 13 Feb 2004 12:59:36 -0800 |
| Cc: | Tommi Virtanen <tv@xxxxxxxxxxxxx>, Leann Ogasawara <ogasawara@xxxxxxxx>, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <20040213124555.00cbf3d7@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <20040213102755.27cf4fcd.shemminger@xxxxxxxx> <20040213203448.GB14048@xxxxxxxxx> <20040213124555.00cbf3d7@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
On Fri, Feb 13, 2004 at 12:45:55PM -0800, Stephen Hemminger wrote: > > No, the "fix" is to just not do this in the driver. I'm not going to > > apply this patch, sorry. > > > > thanks, > > > > greg k-h > > Bah, kernel API's should check there arguments. One of my peeve's about > sysfs is > that it is far too lazy about checking it's inputs. Especially, when the > restrictions > are not well documented, the code needs to validate. But isn't a '/' character a valid character for a file or directory name? :) Yeah, it's pathalogical, but why burden the core from something that is instantly obvious to the developer as a "wrong" thing to do? It's much easier to see, "Oh, my driver created a stupid directory name because of the string I told it to use", than "why in the world is the driver core rejecting my register call when I _know_ it's a correct structure". thanks, greg k-h |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] propogate errors from misc_register to caller, Greg KH |
|---|---|
| Next by Date: | Re: gigabit ethernet, Nivedita Singhvi |
| Previous by Thread: | Re: [PATCH] don't allow / in class device names, Stephen Hemminger |
| Next by Thread: | Re: [PATCH] don't allow / in class device names, maximilian attems |
| Indexes: | [Date] [Thread] [Top] [All Lists] |