Re: [RFC] "Text file busy" when overwriting libraries

From: Alan Cox (
Date: Mon Oct 15 2001 - 06:54:19 EST

> Just to reiterate I see this as a solution to two problems
> 1) It adds an additional safety check that shared libraries won't
> mutate under you.

Which prevents a user with rights doing so deliberately.

> 2) It allows user space access to the security policy information
> regarding executables. Allowing to refust to
> execute binaries, and shared libaries on a filesystem mounted
> noexec.

Which is mostly useless anyway since anyone can write an ld-linux that
doesn't check providing the binary is readable. noexec is basically a weird
ancient unixism that is usless.

> My biggest unresolved issue is which numbers to choose for O_EXEC on
> every platform. As the DENYWRITE code is cleaner in open than in mmap.

And the fact that open has side effects.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Mon Oct 15 2001 - 21:00:57 EST