netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Chenguang Zhao <zhaochenguang@kylinos.cn>
Cc: saeedm@nvidia.com, leon@kernel.org, tariqt@nvidia.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, moshe@nvidia.com,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2] net/mlx5: Fix variable not being completed when function returns
Date: Thu, 09 Jan 2025 16:30:33 +0000	[thread overview]
Message-ID: <173644023374.1439025.12349410132405031646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250108030009.68520-1-zhaochenguang@kylinos.cn>

Hello:

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

On Wed,  8 Jan 2025 11:00:09 +0800 you wrote:
> The cmd_work_handler function returns from the child function
>     cmd_alloc_index because the allocate command entry fails,
>     Before returning, there is no complete ent->slotted.
> 
>     The patch fixes it.
> 
>      mlx5_core 0000:01:00.0: cmd_work_handler:877:(pid 3880418): failed to allocate command entry
>      INFO: task kworker/13:2:4055883 blocked for more than 120 seconds.
>            Not tainted 4.19.90-25.44.v2101.ky10.aarch64 #1
>      "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>      kworker/13:2    D    0 4055883      2 0x00000228
>      Workqueue: events mlx5e_tx_dim_work [mlx5_core]
>      Call trace:
>       __switch_to+0xe8/0x150
>       __schedule+0x2a8/0x9b8
>       schedule+0x2c/0x88
>       schedule_timeout+0x204/0x478
>       wait_for_common+0x154/0x250
>       wait_for_completion+0x28/0x38
>       cmd_exec+0x7a0/0xa00 [mlx5_core]
>       mlx5_cmd_exec+0x54/0x80 [mlx5_core]
>       mlx5_core_modify_cq+0x6c/0x80 [mlx5_core]
>       mlx5_core_modify_cq_moderation+0xa0/0xb8 [mlx5_core]
>       mlx5e_tx_dim_work+0x54/0x68 [mlx5_core]
>       process_one_work+0x1b0/0x448
>       worker_thread+0x54/0x468
>       kthread+0x134/0x138
>       ret_from_fork+0x10/0x18
> 
> [...]

Here is the summary with links:
  - [v2] net/mlx5: Fix variable not being completed when function returns
    https://git.kernel.org/netdev/net/c/0e2909c6bec9

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



      parent reply	other threads:[~2025-01-09 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08  3:00 [PATCH v2] net/mlx5: Fix variable not being completed when function returns Chenguang Zhao
2025-01-09 13:25 ` Tariq Toukan
2025-01-09 16:29   ` Jakub Kicinski
2025-01-09 16:30 ` 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=173644023374.1439025.12349410132405031646.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=moshe@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=zhaochenguang@kylinos.cn \
    /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).