Project

General

Profile

Bug #10959

intended nbmand locking functionality is confused

Added by Gordon Ross 5 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
2019-05-14
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

SMB should not tell the client they have a byte range lock unless the lock it takes in the file system is a real (mandatory) lock.

History

#1

Updated by Gordon Ross 5 months ago

Testing: In production since early 2017

#2

Updated by Electric Monk 5 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

git commit e3c4f75e6cff378e04fbbc3b01e48cc1ac546194

commit  e3c4f75e6cff378e04fbbc3b01e48cc1ac546194
Author: Gordon Ross <gwr@nexenta.com>
Date:   2019-05-17T20:29:13.000Z

    10959 intended nbmand locking functionality is confused
    Reviewed by: Matt Barden <matt.barden@nexenta.com>
    Reviewed by: Evan Layton <evan.layton@nexenta.com>
    Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
    Approved by: Joshua M. Clulow <josh@sysmgr.org>

Also available in: Atom PDF