From: Macpaul Lin <macpaul.lin@mediatek.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-stable <stable@vger.kernel.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Ainge Hsu <ainge.hsu@mediatek.com>,
Eddie Hung <eddie.hung@mediatek.com>,
Miles Chen <miles.chen@mediatek.com>,
Kuohong Wang <kuohong.wang@mediatek.com>,
linux-mediatek <linux-mediatek@lists.infradead.org>,
Macpaul Lin <macpaul.lin@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-usb <linux-usb@vger.kernel.org>,
AceLan Kao <acelan.kao@canonical.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Jens Axboe <axboe@kernel.dk>,
Mediatek WSD Upstream <wsd_upstream@mediatek.com>
Subject: Fix: Please help to cherry-pick patch "bdi: Do not use freezable workqueue" to stable tree
Date: Thu, 15 Jul 2021 12:28:39 +0800 [thread overview]
Message-ID: <1626323319.18118.17.camel@mtkswgap22> (raw)
Dear Greg,
Our customers have feedback some similar issues as below link on Android
kernel-4.14 and kernel-4.19.
Link: https://marc.info/?l=linux-kernel&m=138695698516487
They've reported system become abnormal when OTG U-disk has been plugged
out after the system has been suspended.
After debugging, we've found the root cause is the same of the issue
(link) has been reported. We've also tested the patch "bdi: Do not use
freezable workqueue" is worked.
Link: https://lkml.org/lkml/2019/10/4/176
commit id in Linus tree: a2b90f11217790ec0964ba9c93a4abb369758c26
However, we've checked that patch seems hasn't been applied to stable
tree (We've checked 4.14 and 4.19). Would you please help to cherry-pick
this patch to stable trees (and to Android trees)?
Thanks!
Macpaul Lin
next reply other threads:[~2021-07-15 4:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 4:28 Macpaul Lin [this message]
2021-07-15 11:03 ` Fix: Please help to cherry-pick patch "bdi: Do not use freezable workqueue" to stable tree Greg Kroah-Hartman
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=1626323319.18118.17.camel@mtkswgap22 \
--to=macpaul.lin@mediatek.com \
--cc=acelan.kao@canonical.com \
--cc=ainge.hsu@mediatek.com \
--cc=axboe@kernel.dk \
--cc=eddie.hung@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=macpaul.lin@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=miles.chen@mediatek.com \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--cc=wsd_upstream@mediatek.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 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).