[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <167179d0-e1ea-39a8-4143-949ad57294c2@linux.alibaba.com>
Date:   Sun, 19 Mar 2023 21:36:20 +0800
From:   Cheng Xu <chengyou@...ux.alibaba.com>
To:     Markus Elfring <Markus.Elfring@....de>,
        kernel-janitors@...r.kernel.org, linux-rdma@...r.kernel.org,
        Jason Gunthorpe <jgg@...pe.ca>,
        Kai Shen <kaishen@...ux.alibaba.com>,
        Leon Romanovsky <leon@...nel.org>,
        Yang Li <yang.lee@...ux.alibaba.com>
Cc:     cocci@...ia.fr, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] RDMA/erdma: Fix exception handling in
 erdma_accept_newconn()
On 3/19/23 4:15 AM, Markus Elfring wrote:
> Date: Sat, 18 Mar 2023 21:08:58 +0100
> 
<...>
> +disassoc_socket:
> +    erdma_socket_disassoc(new_s);
> +    sock_release(new_s);
> +    new_cep->state = ERDMA_EPSTATE_CLOSED;
> +    erdma_cancel_mpatimer(new_cep);
> +put_cep:
> +    erdma_cep_put(new_cep);> +    new_cep->sock = NULL;
Thanks, but this causes an use-after-free issue because new_cep will be
released after last erdma_cep_put being called.
Cheng Xu
>  }
>  
>  static int erdma_newconn_connected(struct erdma_cep *cep)
Powered by blists - more mailing lists