From: patchwork-bot+netdevbpf@kernel.org
To: Shannon Nelson <snelson@pensando.io>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
drivers@pensando.io, jtoppins@redhat.com
Subject: Re: [PATCH net] ionic: fix double use of queue-lock
Date: Fri, 03 Sep 2021 10:50:06 +0000 [thread overview]
Message-ID: <163066620630.9656.13610846565944656838.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210902163407.60523-1-snelson@pensando.io>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 2 Sep 2021 09:34:07 -0700 you wrote:
> Deadlock seen in an instance where the hwstamp configuration
> is changed while the driver is running:
>
> [ 3988.736671] schedule_preempt_disabled+0xe/0x10
> [ 3988.736676] __mutex_lock.isra.5+0x276/0x4e0
> [ 3988.736683] __mutex_lock_slowpath+0x13/0x20
> [ 3988.736687] ? __mutex_lock_slowpath+0x13/0x20
> [ 3988.736692] mutex_lock+0x2f/0x40
> [ 3988.736711] ionic_stop_queues_reconfig+0x16/0x40 [ionic]
> [ 3988.736726] ionic_reconfigure_queues+0x43e/0xc90 [ionic]
> [ 3988.736738] ionic_lif_config_hwstamp_rxq_all+0x85/0x90 [ionic]
> [ 3988.736751] ionic_lif_hwstamp_set_ts_config+0x29c/0x360 [ionic]
> [ 3988.736763] ionic_lif_hwstamp_set+0x76/0xf0 [ionic]
> [ 3988.736776] ionic_eth_ioctl+0x33/0x40 [ionic]
> [ 3988.736781] dev_ifsioc+0x12c/0x420
> [ 3988.736785] dev_ioctl+0x316/0x720
>
> [...]
Here is the summary with links:
- [net] ionic: fix double use of queue-lock
https://git.kernel.org/netdev/net/c/79a58c06c2d1
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:[~2021-09-03 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 16:34 [PATCH net] ionic: fix double use of queue-lock Shannon Nelson
2021-09-03 10: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=163066620630.9656.13610846565944656838.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=jtoppins@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=snelson@pensando.io \
/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.