virtiofsd: do not always set FUSE_FLOCK_LOCKS
Right now we always enable it regardless of given commandlines. Fix it by setting the flag relying on the lo->flock bit. Signed-off-by: Peng Tao <tao.peng@linux.alibaba.com> Reviewed-by: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com> Reviewed-by: Sergio Lopez <slp@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
This commit is contained in:
parent
c241aa9457
commit
e468d4af5f
@ -546,9 +546,14 @@ static void lo_init(void *userdata, struct fuse_conn_info *conn)
|
||||
fuse_log(FUSE_LOG_DEBUG, "lo_init: activating writeback\n");
|
||||
conn->want |= FUSE_CAP_WRITEBACK_CACHE;
|
||||
}
|
||||
if (lo->flock && conn->capable & FUSE_CAP_FLOCK_LOCKS) {
|
||||
fuse_log(FUSE_LOG_DEBUG, "lo_init: activating flock locks\n");
|
||||
conn->want |= FUSE_CAP_FLOCK_LOCKS;
|
||||
if (conn->capable & FUSE_CAP_FLOCK_LOCKS) {
|
||||
if (lo->flock) {
|
||||
fuse_log(FUSE_LOG_DEBUG, "lo_init: activating flock locks\n");
|
||||
conn->want |= FUSE_CAP_FLOCK_LOCKS;
|
||||
} else {
|
||||
fuse_log(FUSE_LOG_DEBUG, "lo_init: disabling flock locks\n");
|
||||
conn->want &= ~FUSE_CAP_FLOCK_LOCKS;
|
||||
}
|
||||
}
|
||||
|
||||
if (conn->capable & FUSE_CAP_POSIX_LOCKS) {
|
||||
|
Loading…
Reference in New Issue
Block a user