#include #include #include "debug.h" #include "debug-internal.h" static int __base_pr(const char *format, ...) { va_list args; int err; va_start(args, format); err = vfprintf(stderr, format, args); va_end(args); return err; } libapi_print_fn_t __pr_warning = __base_pr; libapi_print_fn_t __pr_info = __base_pr; libapi_print_fn_t __pr_debug; void libapi_set_print(libapi_print_fn_t warn, libapi_print_fn_t info, libapi_print_fn_t debug) { __pr_warning = warn; __pr_info = info; __pr_debug = debug; } z.ch/cgit.cgi/linux/net-next.git' title='net-next.git Git repository'/>
summaryrefslogtreecommitdiff
path: root/tools/lib/symbol
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2017-01-22 14:04:29 -0500
committerTrond Myklebust <trond.myklebust@primarydata.com>2017-01-24 12:50:47 -0500
commit059aa734824165507c65fd30a55ff000afd14983 (patch)
tree63defb4adb0656c4af72a05081b181b163f94b3e /tools/lib/symbol
parent8ac092519ad91931c96d306c4bfae2c6587c325f (diff)
nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
Xuan Qi reports that the Linux NFSv4 client failed to lock a file that was migrated. The steps he observed on the wire: 1. The client sent a LOCK request to the source server 2. The source server replied NFS4ERR_MOVED 3. The client switched to the destination server 4. The client sent the same LOCK request to the destination server with a bumped lock sequence ID 5. The destination server rejected the LOCK request with NFS4ERR_BAD_SEQID RFC 3530 section 8.1.5 provides a list of NFS errors which do not bump a lock sequence ID. However, RFC 3530 is now obsoleted by RFC 7530. In RFC 7530 section 9.1.7, this list has been updated by the addition of NFS4ERR_MOVED. Reported-by: Xuan Qi <xuan.qi@oracle.com> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Cc: stable@vger.kernel.org # v3.7+ Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'tools/lib/symbol')