With my patch, fcntl will return -1 and set errno to EINVAL. It is up
to the mail proram to detect this condition and proceed accordingly.
BTW, it is requred by POSIX to return EINVAL if file locking is not
available for the file desrcriptor.
> you notice your mail spool will be full of corrupt mailboxes and your
> user base will hate you while your manager demands you change OS.
If it happens, it is caused by the broken mail proram.
> Use the "nolock" mount option. That tells Linux you know there is no
> file locking, you don't care there is no file locking, you aren't using
> remote file locking.
It is irrelevant to my patch. My patch fixes a POSIX bug.
-- H.J. Lu (firstname.lastname@example.org)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com Please read the FAQ at http://www.tux.org/lkml/