netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	tariqt@nvidia.com, shayd@nvidia.com, vladbu@nvidia.com,
	leonro@nvidia.com, maorg@nvidia.com, saeedm@nvidia.com
Subject: Re: [net 1/6] net/mlx5: Fix cleanup of bridge delayed work
Date: Wed, 13 Oct 2021 20:50:07 +0000	[thread overview]
Message-ID: <163415820798.8139.6832798095217662429.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211012205323.20123-2-saeed@kernel.org>

Hello:

This series was applied to netdev/net.git (master)
by Saeed Mahameed <saeedm@nvidia.com>:

On Tue, 12 Oct 2021 13:53:18 -0700 you wrote:
> From: Shay Drory <shayd@nvidia.com>
> 
> Currently, bridge cleanup is calling to cancel_delayed_work(). When this
> function is finished, there is a chance that the delayed work is still
> running. Also, the delayed work is queueing itself.
> As a result, we might execute the delayed work after the bridge cleanup
> have finished and hit a null-ptr oops[1].
> 
> [...]

Here is the summary with links:
  - [net,1/6] net/mlx5: Fix cleanup of bridge delayed work
    https://git.kernel.org/netdev/net/c/2266bb1e122a
  - [net,2/6] net/mlx5e: Allow only complete TXQs partition in MQPRIO channel mode
    https://git.kernel.org/netdev/net/c/ca20dfda05ae
  - [net,3/6] net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path
    https://git.kernel.org/netdev/net/c/94b960b9deff
  - [net,4/6] net/mlx5e: Switchdev representors are not vlan challenged
    https://git.kernel.org/netdev/net/c/b2107cdc43d8
  - [net,5/6] net/mlx5e: Mutually exclude RX-FCS and RX-port-timestamp
    https://git.kernel.org/netdev/net/c/0bc73ad46a76
  - [net,6/6] net/mlx5e: Fix division by 0 in mlx5e_select_queue for representors
    https://git.kernel.org/netdev/net/c/84c8a87402cf

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



  reply	other threads:[~2021-10-13 20:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 20:53 [pull request][net 0/6] mlx5 fixes 2021-10-12 Saeed Mahameed
2021-10-12 20:53 ` [net 1/6] net/mlx5: Fix cleanup of bridge delayed work Saeed Mahameed
2021-10-13 20:50   ` patchwork-bot+netdevbpf [this message]
2021-10-12 20:53 ` [net 2/6] net/mlx5e: Allow only complete TXQs partition in MQPRIO channel mode Saeed Mahameed
2021-10-12 20:53 ` [net 3/6] net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path Saeed Mahameed
2021-10-12 20:53 ` [net 4/6] net/mlx5e: Switchdev representors are not vlan challenged Saeed Mahameed
2021-10-12 20:53 ` [net 5/6] net/mlx5e: Mutually exclude RX-FCS and RX-port-timestamp Saeed Mahameed
2021-10-12 20:53 ` [net 6/6] net/mlx5e: Fix division by 0 in mlx5e_select_queue for representors Saeed Mahameed

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=163415820798.8139.6832798095217662429.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=maorg@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeed@kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=shayd@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=vladbu@nvidia.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).