On 04/21/2014 03:45 PM, Jeff Layton wrote: [...]
> - * These cmd values will set locks that conflict with normal POSIX locks, but > - * are "owned" by the opened file, not the process. This means that they are > - * inherited across fork() like BSD (flock) locks, and they are only released > - * automatically when the last reference to the the open file against which > - * they were acquired is put. > + * These cmd values will set locks that conflict with process-associated > + * record locks, but are "owned" by the opened file description, not the > + * process. This means that they are inherited across fork() like BSD (flock) > + * locks, and they are only released automatically when the last reference to > + * the the open file against which they were acquired is put. (Pre-existing) typo: s/the the/the/ -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
