Messages in this thread | | | Subject | Re: Subtle MM bug | Date | Wed, 10 Jan 2001 19:40:49 +0000 (GMT) | From | Alan Cox <> |
| |
> Of course not by default, it would be a new clone flag (with default to on in > linuxthreads though, to not cause security holes in ported programs like today)
I've seen exactly nil cases where there are any security holes in apps caused by that pthreads api non adherance. There are also far too many overheads imposed by implementing something in kernel space that is nearly useless, not needed for any application 99.9999% of users (possibly 100%) have and can be done just as well in the pthreads library glue - where it will only be a penalty to pthread using apps.
Making everyone suffer for a bad standard corner case is bad. Especially when the 'security hole' is pure FUD
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |