lkml.org 
[lkml]   [2022]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.10 022/158] NFSv4.1: Dont decrease the value of seq_nr_highest_sent
    Date
    From: Trond Myklebust <trond.myklebust@hammerspace.com>

    commit f07a5d2427fc113dc50c5c818eba8929bc27b8ca upstream.

    When we're trying to figure out what the server may or may not have seen
    in terms of request numbers, do not assume that requests with a larger
    number were missed, just because we saw a reply to a request with a
    smaller number.

    Fixes: 3453d5708b33 ("NFSv4.1: Avoid false retries when RPC calls are interrupted")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    ---
    fs/nfs/nfs4proc.c | 5 ++---
    1 file changed, 2 insertions(+), 3 deletions(-)

    --- a/fs/nfs/nfs4proc.c
    +++ b/fs/nfs/nfs4proc.c
    @@ -790,10 +790,9 @@ static void nfs4_slot_sequence_record_se
    if ((s32)(seqnr - slot->seq_nr_highest_sent) > 0)
    slot->seq_nr_highest_sent = seqnr;
    }
    -static void nfs4_slot_sequence_acked(struct nfs4_slot *slot,
    - u32 seqnr)
    +static void nfs4_slot_sequence_acked(struct nfs4_slot *slot, u32 seqnr)
    {
    - slot->seq_nr_highest_sent = seqnr;
    + nfs4_slot_sequence_record_sent(slot, seqnr);
    slot->seq_nr_last_acked = seqnr;
    }


    \
     
     \ /
      Last update: 2022-08-23 14:08    [W:2.354 / U:0.388 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site