From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Heyi Guo <guoheyi@linux.alibaba.com>
Cc: linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Takashi Iwai <tiwai@suse.de>
Subject: Re: Why hasn't the patch "r8152: Fix a deadlock by doubly PM resume" back ported to stable branches?
Date: Mon, 27 Oct 2025 07:45:13 +0100 [thread overview]
Message-ID: <2025102742-mumbling-starlit-c651@gregkh> (raw)
In-Reply-To: <5e065a78-b371-4ef7-8ce6-a902f80e2b02@linux.alibaba.com>
On Mon, Oct 27, 2025 at 02:04:09PM +0800, Heyi Guo wrote:
> Hi all,
>
> We found that below bug fix patch had not been back ported to stable
> branches, like linux-5.10.y. Is there any special reason?
>
> commit 776ac63a986d211286230c4fd70f85390eabedcd
> Author: Takashi Iwai <tiwai@suse.de>
> AuthorDate: Wed Jul 14 19:00:22 2021 +0200
> Commit: David S. Miller <davem@davemloft.net>
> CommitDate: Wed Jul 14 14:57:55 2021 -0700
>
> r8152: Fix a deadlock by doubly PM resume
>
> r8152 driver sets up the MAC address at reset-resume, while
> rtl8152_set_mac_address() has the temporary autopm get/put. This may
> lead to a deadlock as the PM lock has been already taken for the
> execution of the runtime PM callback.
>
> This patch adds the workaround to avoid the superfluous autpm when
> called from rtl8152_reset_resume().
>
> Link: https://bugzilla.suse.com/show_bug.cgi?id=1186194
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: David S. Miller <davem@davemloft.net>
Because it was not marked to be backported at all. If you feel it
should be, please send a tested version to stable@vger.kernel.org for
inclusion.
thanks,
greg k-h
prev parent reply other threads:[~2025-10-27 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 6:04 Why hasn't the patch "r8152: Fix a deadlock by doubly PM resume" back ported to stable branches? Heyi Guo
2025-10-27 6:45 ` Greg Kroah-Hartman [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=2025102742-mumbling-starlit-c651@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=guoheyi@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tiwai@suse.de \
/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