>>> * Puts back old-style fcntl locking, so that old a.out gdbm libraries
>>> won't explode and die.
>>
>> I thought this was taken out because it was a broken design and could
>> lead to data corruption?
Yes.
> Well, I'm not so sure about that, unless doing new-style flocking
> will also cause data corruption. Basically, all the patch with
> the locks does is to map SHLCK -> RDLCK and EXLCK -> WRLCK.
The software you have was written to use one API.
Old kernels did not provide that API.
Old libc used a similar API as a substitute.
Lock inheritance did not work as apps expected.
Stuff broke. People lost email and other data.
Now we have the desired API implemented correctly.
Anything using the old API is suspect.
Some old Linux-specific apps would work fine.
Apps that really needed what was asked for...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/