From: patchwork-bot+netdevbpf@kernel.org
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: netdev@vger.kernel.org, siva.kallam@broadcom.com,
prashant@broadcom.com, mchan@broadcom.com,
pavan.chebbi@broadcom.com
Subject: Re: [PATCH v2] net/tg3: resolve deadlock in tg3_reset_task() during EEH
Date: Thu, 26 Jan 2023 06:50:17 +0000 [thread overview]
Message-ID: <167471581708.15959.4004093373936873252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230124185339.225806-1-drc@linux.vnet.ibm.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 24 Jan 2023 13:53:39 -0500 you wrote:
> During EEH error injection testing, a deadlock was encountered in the tg3
> driver when tg3_io_error_detected() was attempting to cancel outstanding
> reset tasks:
>
> crash> foreach UN bt
> ...
> PID: 159 TASK: c0000000067c6000 CPU: 8 COMMAND: "eehd"
> ...
> #5 [c00000000681f990] __cancel_work_timer at c00000000019fd18
> #6 [c00000000681fa30] tg3_io_error_detected at c00800000295f098 [tg3]
> #7 [c00000000681faf0] eeh_report_error at c00000000004e25c
> ...
>
> [...]
Here is the summary with links:
- [v2] net/tg3: resolve deadlock in tg3_reset_task() during EEH
https://git.kernel.org/netdev/net/c/6c4ca03bd890
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-01-26 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 0:31 [PATCH] net/tg3: resolve deadlock in tg3_reset_task() during EEH David Christensen
2023-01-24 7:25 ` Pavan Chebbi
2023-01-24 8:43 ` Michael Chan
2023-01-24 9:12 ` Pavan Chebbi
2023-01-24 18:53 ` [PATCH v2] " David Christensen
2023-01-25 8:33 ` Pavan Chebbi
2023-01-26 6: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=167471581708.15959.4004093373936873252.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=drc@linux.vnet.ibm.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pavan.chebbi@broadcom.com \
--cc=prashant@broadcom.com \
--cc=siva.kallam@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.