bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: daniel@iogearbox.net, ast@kernel.org, bpf@vger.kernel.org,
	netdev@vger.kernel.org, hawk@kernel.org, davem@davemloft.net,
	john.fastabend@gmail.com, lorenzo@kernel.org, bsd@fb.com,
	alexanderduyck@fb.com
Subject: Re: [PATCH bpf-next] xdp: move the rxq_info.mem clearing to unreg_mem_model()
Date: Mon, 28 Jun 2021 21:20:54 +0000	[thread overview]
Message-ID: <162491525444.9606.11980237651538254312.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210625221612.2637086-1-kuba@kernel.org>

Hello:

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

On Fri, 25 Jun 2021 15:16:12 -0700 you wrote:
> xdp_rxq_info_unreg() implicitly calls xdp_rxq_info_unreg_mem_model().
> This may well be confusing to the driver authors, and lead to double
> free if they call xdp_rxq_info_unreg_mem_model() before
> xdp_rxq_info_unreg() (when mem model type == MEM_TYPE_PAGE_POOL).
> 
> In fact error path of mvpp2_rxq_init() seems to currently do
> exactly that.
> 
> [...]

Here is the summary with links:
  - [bpf-next] xdp: move the rxq_info.mem clearing to unreg_mem_model()
    https://git.kernel.org/bpf/bpf-next/c/a78cae247681

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



      reply	other threads:[~2021-06-28 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 22:16 [PATCH bpf-next] xdp: move the rxq_info.mem clearing to unreg_mem_model() Jakub Kicinski
2021-06-28 21:20 ` 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=162491525444.9606.11980237651538254312.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexanderduyck@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=bsd@fb.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).