]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
nfs: fix memory leak in error path of nfs4_do_reclaim
authorLi Lingfeng <lilingfeng3@huawei.com>
Wed, 4 Sep 2024 12:34:57 +0000 (20:34 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 17 Oct 2024 13:08:03 +0000 (15:08 +0200)
commit 8f6a7c9467eaf39da4c14e5474e46190ab3fb529 upstream.

Commit c77e22834ae9 ("NFSv4: Fix a potential sleep while atomic in
nfs4_do_reclaim()") separate out the freeing of the state owners from
nfs4_purge_state_owners() and finish it outside the rcu lock.
However, the error path is omitted. As a result, the state owners in
"freeme" will not be released.
Fix it by adding freeing in the error path.

Fixes: c77e22834ae9 ("NFSv4: Fix a potential sleep while atomic in nfs4_do_reclaim()")
Signed-off-by: Li Lingfeng <lilingfeng3@huawei.com>
Cc: stable@vger.kernel.org # v5.3+
Signed-off-by: Anna Schumaker <anna.schumaker@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfs/nfs4state.c

index d8fc5d72a161c95d1c96835e01bde62e6ad352d9..e5cdb700bbe724da4980b97c68ba4419422d94ca 100644 (file)
@@ -1948,6 +1948,7 @@ restart:
                                set_bit(ops->owner_flag_bit, &sp->so_flags);
                                nfs4_put_state_owner(sp);
                                status = nfs4_recovery_handle_error(clp, status);
+                               nfs4_free_state_owners(&freeme);
                                return (status != 0) ? status : -EAGAIN;
                        }