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 1/1 v3] skbuff: Fix a potential race while recycling page_pool
 packets
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <162646140463.32424.6557928030854719030.git-patchwork-notify@kernel.org>
Date:   Fri, 16 Jul 2021 18:50:04 +0000
References: <20210716070222.106422-1-ilias.apalodimas@linaro.org>
In-Reply-To: <20210716070222.106422-1-ilias.apalodimas@linaro.org>
To:     Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc:     netdev@vger.kernel.org, linyunsheng@huawei.com,
        alexanderduyck@fb.com, brouer@redhat.com, davem@davemloft.net,
        kuba@kernel.org, alobakin@pm.me, jonathan.lemon@gmail.com,
        willemb@google.com, linmiaohe@huawei.com, gnault@redhat.com,
        cong.wang@bytedance.com, mcroce@microsoft.com,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

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

On Fri, 16 Jul 2021 10:02:18 +0300 you wrote:
> As Alexander points out, when we are trying to recycle a cloned/expanded
> SKB we might trigger a race.  The recycling code relies on the
> pp_recycle bit to trigger,  which we carry over to cloned SKBs.
> If that cloned SKB gets expanded or if we get references to the frags,
> call skb_release_data() and overwrite skb->head, we are creating separate
> instances accessing the same page frags.  Since the skb_release_data()
> will first try to recycle the frags,  there's a potential race between
> the original and cloned SKB, since both will have the pp_recycle bit set.
> 
> [...]

Here is the summary with links:
  - [1/1,v3] skbuff: Fix a potential race while recycling page_pool packets
    https://git.kernel.org/netdev/net/c/2cc3aeb5eccc

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