diff options
| author | Miklos Szeredi <miklos@szeredi.hu> | 2006-06-23 02:05:12 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-06-23 07:43:02 -0700 |
| commit | 75e1fcc0b18df0a65ab113198e9dc0e98999a08c (patch) | |
| tree | 3ac0d0d3120cbca4ee9734494e2c9a4e0775ac4f /fs/locks.c | |
| parent | ff7b86b82083f24b8637dff1528c7101c18c7f39 (diff) | |
| download | kernel_samsung_smdk4412-75e1fcc0b18df0a65ab113198e9dc0e98999a08c.tar.gz kernel_samsung_smdk4412-75e1fcc0b18df0a65ab113198e9dc0e98999a08c.tar.bz2 kernel_samsung_smdk4412-75e1fcc0b18df0a65ab113198e9dc0e98999a08c.zip | |
[PATCH] vfs: add lock owner argument to flush operation
Pass the POSIX lock owner ID to the flush operation.
This is useful for filesystems which don't want to store any locking state
in inode->i_flock but want to handle locking/unlocking POSIX locks
internally. FUSE is one such filesystem but I think it possible that some
network filesystems would need this also.
Also add a flag to indicate that a POSIX locking request was generated by
close(), so filesystems using the above feature won't send an extra locking
request in this case.
Signed-off-by: Miklos Szeredi <miklos@szeredi.hu>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/locks.c')
| -rw-r--r-- | fs/locks.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/locks.c b/fs/locks.c index e588e1c265f..f8a634ac112 100644 --- a/fs/locks.c +++ b/fs/locks.c @@ -1907,7 +1907,7 @@ void locks_remove_posix(struct file *filp, fl_owner_t owner) return; lock.fl_type = F_UNLCK; - lock.fl_flags = FL_POSIX; + lock.fl_flags = FL_POSIX | FL_CLOSE; lock.fl_start = 0; lock.fl_end = OFFSET_MAX; lock.fl_owner = owner; |