Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] net:nfc:digital: Fix a double free in digital_tg_recv_dep_req
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <161956321049.28898.4886085211372158981.git-patchwork-notify@kernel.org>
Date:   Tue, 27 Apr 2021 22:40:10 +0000
References: <20210427162258.7238-1-lyl2019@mail.ustc.edu.cn>
In-Reply-To: <20210427162258.7238-1-lyl2019@mail.ustc.edu.cn>
To:     Lv Yunlong <lyl2019@mail.ustc.edu.cn>
Cc:     davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Tue, 27 Apr 2021 09:22:58 -0700 you wrote:
> In digital_tg_recv_dep_req, it calls nfc_tm_data_received(..,resp).
> If nfc_tm_data_received() failed, the callee will free the resp via
> kfree_skb() and return error. But in the exit branch, the resp
> will be freed again.
> 
> My patch sets resp to NULL if nfc_tm_data_received() failed, to
> avoid the double free.
> 
> [...]

Here is the summary with links:
  - net:nfc:digital: Fix a double free in digital_tg_recv_dep_req
    https://git.kernel.org/netdev/net-next/c/75258586793e

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html