diff options
author | Trond Myklebust <[email protected]> | 2012-08-08 16:03:13 -0400 |
---|---|---|
committer | Trond Myklebust <[email protected]> | 2012-08-08 16:03:13 -0400 |
commit | 47fbf7976e0b7d9dcdd799e2a1baba19064d9631 (patch) | |
tree | 1d2a0b4d69f331f5f0d82f15be9a1f06b3d80aa1 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 7de6e28417c65919cf2c1621841a650c4a3afbbd (diff) |
NFSv4.1: Remove a bogus BUG_ON() in nfs4_layoutreturn_done
Ever since commit 0a57cdac3f (NFSv4.1 send layoutreturn to fence
disconnected data server) we've been sending layoutreturn calls
while there is potentially still outstanding I/O to the data
servers. The reason we do this is to avoid races between replayed
writes to the MDS and the original writes to the DS.
When this happens, the BUG_ON() in nfs4_layoutreturn_done can
be triggered because it assumes that we would never call
layoutreturn without knowing that all I/O to the DS is
finished. The fix is to remove the BUG_ON() now that the
assumptions behind the test are obsolete.
Reported-by: Boaz Harrosh <[email protected]>
Reported-by: Tigran Mkrtchyan <[email protected]>
Signed-off-by: Trond Myklebust <[email protected]>
Cc: [email protected] [>=3.5]
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions