Malahal has uploaded this change for review.
Update dupreq after svc_sendreply failure
If svc_sendreply() fails, we don't update the dupreq. The dupreq state
will be forever in DUPREQ_START! Here after, all retries will be dropped
as the dupreq is found in a processing state leading to endless retries.
svc_sendreply() can fail in UDP transports. TCP transports don't fail
unless there is some kind of RPC encoding failure.
Change-Id: Ib2b0bdd689d57c141448ccfb7c0789f3dfd6fa9c
Signed-off-by: Malahal Naineni <malahal@us.ibm.com>
---
M src/MainNFSD/nfs_worker_thread.c
1 file changed, 0 insertions(+), 1 deletion(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/88/488188/1
To view, visit change 488188. To unsubscribe, or for help writing mail filters, visit settings.