Andi Kleen writes:
> On Thu, May 03, 2001 at 06:03:07PM -0700, Jeremy Allison wrote:
> > The only thing we need to fix (IMHO) is the close(dup(fd)) "bug",
> > which I have yet to see any application treat as anything other
> > than a spec. bug that must be worked around.
>
> I don't think it's a bug right now; not dropping them and keeping
> them around forever adds a quite lot of new problems: just see how
> unnatural sysv shared memory segments and semaphores fit into the
> rest of the mostly elegant unix model. You need to have special
> administration tools for them, you need to clean up after crashing
> applications that keep their resources around, you need special
> global resource limits to avoid users running amok etc. Persistent
> locks have similar problems. They probably can all be solved, but it
> won't be pretty or easy.
No, the broken behaviour they are referring to is close(dup(fd)) will
drop POSIX locks on fd. The behaviour they want is that the locks are
held until all references to the file are closed in the process that
owns the lock.
Regards,
Richard....
Permanent: [EMAIL PROTECTED]
Current: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]