netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Larysa Zaremba <larysa.zaremba@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
	pabeni@redhat.com, intel-wired-lan@osuosl.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	alexandr.lobakin@intel.com, anthony.l.nguyen@intel.com,
	maciej.fijalkowski@intel.com
Subject: Re: [PATCH net] ice: xsk: Fix cleaning of XDP_TX frames
Date: Sat, 11 Feb 2023 04:00:19 +0000	[thread overview]
Message-ID: <167608801979.32607.6812685908820179983.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230209160130.1779890-1-larysa.zaremba@intel.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  9 Feb 2023 17:01:30 +0100 you wrote:
> Incrementation of xsk_frames inside the for-loop produces
> infinite loop, if we have both normal AF_XDP-TX and XDP_TXed
> buffers to complete.
> 
> Split xsk_frames into 2 variables (xsk_frames and completed_frames)
> to eliminate this bug.
> 
> [...]

Here is the summary with links:
  - [net] ice: xsk: Fix cleaning of XDP_TX frames
    https://git.kernel.org/netdev/net/c/1f090494170e

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



      parent reply	other threads:[~2023-02-11  4:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 16:01 [PATCH net] ice: xsk: Fix cleaning of XDP_TX frames Larysa Zaremba
2023-02-09 17:07 ` Alexander H Duyck
2023-02-09 17:20 ` Tony Nguyen
2023-02-09 18:00   ` Jakub Kicinski
2023-02-11  4:00 ` 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=167608801979.32607.6812685908820179983.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandr.lobakin@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@osuosl.org \
    --cc=kuba@kernel.org \
    --cc=larysa.zaremba@intel.com \
    --cc=maciej.fijalkowski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).