public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Lv Yunlong <lyl2019@mail.ustc.edu.cn>
Cc: jmaloy@redhat.com, ying.xue@windriver.com, davem@davemloft.net,
	kuba@kernel.org, netdev@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net:tipc: Fix a double free in tipc_sk_mcast_rcv
Date: Mon, 29 Mar 2021 23:30:08 +0000	[thread overview]
Message-ID: <161706060899.18537.8994477724999069966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210328073029.4325-1-lyl2019@mail.ustc.edu.cn>

Hello:

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

On Sun, 28 Mar 2021 00:30:29 -0700 you wrote:
> In the if(skb_peek(arrvq) == skb) branch, it calls __skb_dequeue(arrvq) to get
> the skb by skb = skb_peek(arrvq). Then __skb_dequeue() unlinks the skb from arrvq
> and returns the skb which equals to skb_peek(arrvq). After __skb_dequeue(arrvq)
> finished, the skb is freed by kfree_skb(__skb_dequeue(arrvq)) in the first time.
> 
> Unfortunately, the same skb is freed in the second time by kfree_skb(skb) after
> the branch completed.
> 
> [...]

Here is the summary with links:
  - net:tipc: Fix a double free in tipc_sk_mcast_rcv
    https://git.kernel.org/netdev/net/c/6bf24dc0cc0c

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



      reply	other threads:[~2021-03-29 23:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28  7:30 [PATCH] net:tipc: Fix a double free in tipc_sk_mcast_rcv Lv Yunlong
2021-03-29 23:30 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=161706060899.18537.8994477724999069966.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyl2019@mail.ustc.edu.cn \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=ying.xue@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox