Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis

2001-06-01 Thread Alan Cox
> Only some of them can be cached... (some of the MIIs in some drivers > are already cached, in fact) you can't cache stuff like what your link > partner is advertising at the moment, or what your battery status is at > the moment. I am sure that to an unpriviledged application reporting back

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis

2001-06-01 Thread Jeff Garzik
Alan Cox wrote: > > In both of these situations, calling the ioctls without priveleges is > > quite useful, so maybe rate-limiting for ioctls and proc files like this > > would be a good idea in general. > Many of them (like the MII and APM ones) the result can be cached Only some of them can

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis

2001-06-01 Thread Alan Cox
> In both of these situations, calling the ioctls without priveleges is > quite useful, so maybe rate-limiting for ioctls and proc files like this > would be a good idea in general. Many of them (like the MII and APM ones) the result can be cached - To unsubscribe from this list: send the line

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis time)

2001-06-01 Thread Jeff Garzik
Bogdan Costescu wrote: > > On Fri, 1 Jun 2001, Pete Zaitcev wrote: > > > > But, each time a user cats this proc file, the user is banging the > > > hardware. What happens when a malicious user forks off 100 processes to > > > continually cat this file? :) > > > > Nothing good, probably. Same

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis time)

2001-06-01 Thread Jeff Garzik
Bogdan Costescu wrote: On Fri, 1 Jun 2001, Pete Zaitcev wrote: But, each time a user cats this proc file, the user is banging the hardware. What happens when a malicious user forks off 100 processes to continually cat this file? :) Nothing good, probably. Same story as

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis

2001-06-01 Thread Alan Cox
Only some of them can be cached... (some of the MIIs in some drivers are already cached, in fact) you can't cache stuff like what your link partner is advertising at the moment, or what your battery status is at the moment. I am sure that to an unpriviledged application reporting back the

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis

2001-06-01 Thread Jeff Garzik
Alan Cox wrote: In both of these situations, calling the ioctls without priveleges is quite useful, so maybe rate-limiting for ioctls and proc files like this would be a good idea in general. Many of them (like the MII and APM ones) the result can be cached Only some of them can be

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis

2001-06-01 Thread Alan Cox
In both of these situations, calling the ioctls without priveleges is quite useful, so maybe rate-limiting for ioctls and proc files like this would be a good idea in general. Many of them (like the MII and APM ones) the result can be cached - To unsubscribe from this list: send the line

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis time)

2001-05-31 Thread Dax Kelson
Tim Hockin said once upon a time (Thu, 31 May 2001): > Aattached is a (large, but self contained) patch for Cobalt Networks suport > for x86 systems (RaQ3, RaQ4, Qube3, RaQXTR). Please let me know if there > is anything that would prevent this from general inclusion in the next > release. I

Re: [PATCH] support for Cobalt Networks (x86 only) systems (for realthis time)

2001-05-31 Thread Dax Kelson
Tim Hockin said once upon a time (Thu, 31 May 2001): Aattached is a (large, but self contained) patch for Cobalt Networks suport for x86 systems (RaQ3, RaQ4, Qube3, RaQXTR). Please let me know if there is anything that would prevent this from general inclusion in the next release. I can