Problem recurrence：
    On the server side, a process opens a file in a shared directory and adds a POSIX write lock. For example, use WPS to open 123.xls.
    On the client side, an error (NT_STATUS_FILE_LOCK_CONFLICT) will be reported when using smbclient or libsmbclient to download an opened file.

But opened files can be downloaded normally through CIFS. 

The preliminary test found that the file download can be completed after completing the following modifications:
    Change the initial value of the flags variable in the functions SMBC_server_internal and do_connect to CLI_FULL_CONNECTION_OPLOCKS.

What I want to ask is:
    Is there any risk to this modification.
    Is there a configuration to control oplock behavior on the client side.

Looking forward to your reply, thanks!