netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Shailend Chand <shailend@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net-next 0/6] gve: Alloc before freeing when changing config
Date: Wed, 24 Jan 2024 01:50:26 +0000	[thread overview]
Message-ID: <170606102606.25797.6019199168197277313.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240122182632.1102721-1-shailend@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 22 Jan 2024 18:26:26 +0000 you wrote:
> Functions allocating resources did so directly into priv thus far. The
> assumption doing that was that priv was not already holding references
> to live resources.
> 
> When ring configuration is changed in any way from userspace, thus far
> we relied on calling the ndo_stop and ndo_open callbacks in succession.
> This meant that we teardown existing resources and rob the OS of
> networking before we have successfully allocated resources for the new
> config.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] gve: Define config structs for queue allocation
    https://git.kernel.org/netdev/net-next/c/7cea48b9a4b2
  - [net-next,2/6] gve: Refactor napi add and remove functions
    https://git.kernel.org/netdev/net-next/c/1dfc2e46117e
  - [net-next,3/6] gve: Switch to config-aware queue allocation
    https://git.kernel.org/netdev/net-next/c/f13697cc7a19
  - [net-next,4/6] gve: Refactor gve_open and gve_close
    https://git.kernel.org/netdev/net-next/c/92a6d7a4010c
  - [net-next,5/6] gve: Alloc before freeing when adjusting queues
    https://git.kernel.org/netdev/net-next/c/5f08cd3d6423
  - [net-next,6/6] gve: Alloc before freeing when changing features
    https://git.kernel.org/netdev/net-next/c/f3753771e7cc

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



      parent reply	other threads:[~2024-01-24  1:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 18:26 [PATCH net-next 0/6] gve: Alloc before freeing when changing config Shailend Chand
2024-01-22 18:26 ` [PATCH net-next 1/6] gve: Define config structs for queue allocation Shailend Chand
2024-01-23 16:26   ` Simon Horman
2024-01-22 18:26 ` [PATCH net-next 2/6] gve: Refactor napi add and remove functions Shailend Chand
2024-01-23 16:26   ` Simon Horman
2024-01-22 18:26 ` [PATCH net-next 3/6] gve: Switch to config-aware queue allocation Shailend Chand
2024-01-23 16:27   ` Simon Horman
2024-01-22 18:26 ` [PATCH net-next 4/6] gve: Refactor gve_open and gve_close Shailend Chand
2024-01-22 18:26 ` [PATCH net-next 5/6] gve: Alloc before freeing when adjusting queues Shailend Chand
2024-01-22 18:26 ` [PATCH net-next 6/6] gve: Alloc before freeing when changing features Shailend Chand
2024-01-24  1:50 ` 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=170606102606.25797.6019199168197277313.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shailend@google.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).