> 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 /proc/apm, which only hits BIOS instead (and it's debateable what is better). > Security: don't you want CAP_RAW_IO or something before executing any of > these ioctls? Perhaps it's mode 600 in their distro... > bug: you can't hold a spinlock while you are sleeping in copy_from_user Yep... I meant to check for it but forgot. -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- [PATCH] support for Cobalt Networks (x86 only) systems (fo... Tim Hockin
- Re: [PATCH] support for Cobalt Networks (x86 only) sy... Jeff Garzik
- Re: [PATCH] support for Cobalt Networks (x86 only) sy... Alan Cox
- Re: [PATCH] support for Cobalt Networks (x86 only) sy... Pete Zaitcev
- Re: [PATCH] support for Cobalt Networks (x86 only... Bogdan Costescu
- Re: [PATCH] support for Cobalt Networks (x86 ... Jeff Garzik
- Re: [PATCH] support for Cobalt Networks (... Alan Cox
- Re: [PATCH] support for Cobalt Netwo... Jeff Garzik
- Re: [PATCH] support for Cobalt N... Alan Cox
- Re: [PATCH] support for Coba... Bogdan Costescu
- Re: [PATCH] support for Coba... Jeff Garzik
- Re: [PATCH] support for Coba... David S. Miller
- Re: [PATCH] support for Coba... Bogdan Costescu
- Re: [PATCH] support for Coba... Bogdan Costescu