diff options
| author | Jeff Layton <jlayton@redhat.com> | 2014-03-04 10:30:23 -0500 |
|---|---|---|
| committer | Jeff Layton <jlayton@redhat.com> | 2014-03-31 08:24:43 -0400 |
| commit | 90478939dce096ed5b239cad16237dca0a59d66f (patch) | |
| tree | 743b3d825bc56bd1c0ab4d9487abba7b6883af86 /fs/qnx4 | |
| parent | 5d50ffd7c31dab47c6b828841ca1ec70a1b40169 (diff) | |
| download | linux-90478939dce096ed5b239cad16237dca0a59d66f.tar.gz linux-90478939dce096ed5b239cad16237dca0a59d66f.tar.bz2 linux-90478939dce096ed5b239cad16237dca0a59d66f.zip | |
locks: require that flock->l_pid be set to 0 for file-private locks
Neil Brown suggested potentially overloading the l_pid value as a "lock
context" field for file-private locks. While I don't think we will
probably want to do that here, it's probably a good idea to ensure that
in the future we could extend this API without breaking existing
callers.
Typically the l_pid value is ignored for incoming struct flock
arguments, serving mainly as a place to return the pid of the owner if
there is a conflicting lock. For file-private locks, require that it
currently be set to 0 and return EINVAL if it isn't. If we eventually
want to make a non-zero l_pid mean something, then this will help ensure
that we don't break legacy programs that are using file-private locks.
Cc: Neil Brown <neilb@suse.de>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Diffstat (limited to 'fs/qnx4')
0 files changed, 0 insertions, 0 deletions