From: patchwork-bot+netdevbpf@kernel.org
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, andrew+netdev@lunn.ch,
dianders@chromium.org, tfiga@chromium.org,
danielgeorgem@chromium.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] net: usb: r8152: fix resume reset deadlock
Date: Sat, 31 Jan 2026 03:30:05 +0000 [thread overview]
Message-ID: <176983020561.3983574.16514295663164511885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260129031106.3805887-1-senozhatsky@chromium.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 29 Jan 2026 12:10:30 +0900 you wrote:
> rtl8152 can trigger device reset during reset which
> potentially can result in a deadlock:
>
> **** DPM device timeout after 10 seconds; 15 seconds until panic ****
> Call Trace:
> <TASK>
> schedule+0x483/0x1370
> schedule_preempt_disabled+0x15/0x30
> __mutex_lock_common+0x1fd/0x470
> __rtl8152_set_mac_address+0x80/0x1f0
> dev_set_mac_address+0x7f/0x150
> rtl8152_post_reset+0x72/0x150
> usb_reset_device+0x1d0/0x220
> rtl8152_resume+0x99/0xc0
> usb_resume_interface+0x3e/0xc0
> usb_resume_both+0x104/0x150
> usb_resume+0x22/0x110
>
> [...]
Here is the summary with links:
- [PATCHv2] net: usb: r8152: fix resume reset deadlock
https://git.kernel.org/netdev/net/c/6d06bc83a5ae
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:[~2026-01-31 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 3:10 [PATCHv2] net: usb: r8152: fix resume reset deadlock Sergey Senozhatsky
2026-01-31 3: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=176983020561.3983574.16514295663164511885.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=danielgeorgem@chromium.org \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=senozhatsky@chromium.org \
--cc=tfiga@chromium.org \
/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