diff options
author | Csaba Henk <csaba@gluster.com> | 2009-12-06 14:27:57 +0000 |
---|---|---|
committer | Anand V. Avati <avati@dev.gluster.com> | 2009-12-06 12:39:15 -0800 |
commit | 76d6f3fbe993dddd72540f461090803636fa2dc5 (patch) | |
tree | 6f5573d88eb296b153aed466a505d3f3fe3c2c1e /ChangeLog | |
parent | 33f3abffe4f0de929d3732a472ad3df766d575b7 (diff) |
fuse-bridge: make use of lock owner data in a protocol adherent way.
No need for pid fallback, for those cases where we use it,
it's always available.
It appears conditionally in read/write/truncate (related to mandatory
locking). There just get it for demonstrative purposes.
Discard it from release, there locking data exists only as a
portability hack, no use of it on Linux.
Signed-off-by: Csaba Henk <csaba@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336
Diffstat (limited to 'ChangeLog')
0 files changed, 0 insertions, 0 deletions