From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Johan Hovold <johan@kernel.org>,
stable-commits@vger.kernel.org, johan+linaro@kernel.org,
Felipe Balbi <balbi@kernel.org>
Subject: Re: Patch "usb: dwc3: qcom: fix peripheral and OTG suspend" has been added to the 5.19-stable tree
Date: Mon, 5 Sep 2022 19:57:25 +0200 [thread overview]
Message-ID: <YxY4hbjs0Y0877Ns@kroah.com> (raw)
In-Reply-To: <YxYrS3z/nYFYzoTh@sashalap>
On Mon, Sep 05, 2022 at 01:00:59PM -0400, Sasha Levin wrote:
> On Mon, Sep 05, 2022 at 05:00:10PM +0200, Johan Hovold wrote:
> > On Mon, Sep 05, 2022 at 09:36:07AM -0400, Sasha Levin wrote:
> > > On Mon, Sep 05, 2022 at 03:23:13PM +0200, Johan Hovold wrote:
> > > >On Mon, Sep 05, 2022 at 09:17:41AM -0400, Sasha Levin wrote:
> > > >> On Mon, Sep 05, 2022 at 03:13:09PM +0200, Johan Hovold wrote:
> > > >> >On Mon, Sep 05, 2022 at 09:04:44AM -0400, Sasha Levin wrote:
> > > >> >> On Mon, Sep 05, 2022 at 02:58:31PM +0200, Johan Hovold wrote:
> > > >> >> >On Mon, Sep 05, 2022 at 08:53:09AM -0400, Sasha Levin wrote:
> > > >> >> >> Fixes: 6895ea55c385 ("usb: dwc3: qcom: Configure wakeup interrupts during suspend")
> > > >> >> >
> > > >> >> >This commit doesn't exist in 5.19 (and earlier trees), shouldn't your
> > > >> >> >scripts check for that?
> > > >> >>
> > > >> >> They do - it was backported to 5.19.
> > > >> >
> > > >> >What?! Why on earth would 6895ea55c385 ("usb: dwc3: qcom: Configure
> > > >> >wakeup interrupts during suspend") be backported to stable?
> > > >> >
> > > >> >Please drop that patch instead. It's essentially a new feature and is in
> > > >> >any case in no way stable material.
> > > >>
> > > >> Right, it was picked up as a dependency of a872ab303d5d ("usb: dwc3: qcom: fix use-after-free on runtime-PM wakeup")
> > > >
> > > >That's wrong too, it's not a dependency for that fix.
> > >
> > > Right, it may not strictly be one, but we're trying to bring in
> > > dependencies as is without modifying the patch is it's far less error
> > > prone, and keeps future backports easy, as long as backporting those
> > > isn't riskier.
> >
> > It should only be some context that have changed. Backporting a known
> > broken and non-trivial feature patch for that can't be right. It is
> > certainly riskier.
> >
> > > In this case, if I were to drop a872ab303d5d I'd also need to drop:
> > >
> > > a872ab303d5d ("usb: dwc3: qcom: fix use-after-free on runtime-PM wakeup")
> > > 6498a96c8c9c ("usb: dwc3: qcom: fix runtime PM wakeup")
> > >
> > > >So does this mean you're dropping the patches that should not be
> > > >backported?
> > >
> > > Having said the above, at the end it's your patches and your call, let
> > > me know if you're okay with dropping a872ab303d5d, a872ab303d5d, and
> >
> > You mentioned a872ab303d5d twice here.
> >
> > > 6498a96c8c9c from all trees and I'll do that.
> >
> > This one didn't have a CC stable tag so not sure why you're backporting
> > that one either.
> >
> > Just pick
> >
> > a872ab303d5d ("usb: dwc3: qcom: fix use-after-free on runtime-PM wakeup")
> >
> > which was the only patch I had marked for stable and fix up the trivial
> > context change (an unrelated function has been added after the new
> > helper in mainline).
>
> Okay, this should be done. Please take a look at the queue to confirm.
At a quick glance, looks good to me. I'll go through the other USB cc:
stable patches tomorrow and make sure.
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-05 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220905125309.1037700-1-sashal@kernel.org>
[not found] ` <YxXyd5H9TLWKUbWy@hovoldconsulting.com>
[not found] ` <YxXz7LBh5Y4DSd4W@sashalap>
[not found] ` <YxX15QkMDV+0amk8@hovoldconsulting.com>
[not found] ` <YxX29eiH0qyyRk9x@sashalap>
[not found] ` <YxX4QT6eeRiatmX+@hovoldconsulting.com>
[not found] ` <YxX7R/EAynZC/iGr@sashalap>
2022-09-05 15:07 ` Patch "usb: dwc3: qcom: fix peripheral and OTG suspend" has been added to the 5.19-stable tree Greg Kroah-Hartman
[not found] ` <YxYO+u0rAg029yNl@hovoldconsulting.com>
[not found] ` <YxYrS3z/nYFYzoTh@sashalap>
2022-09-05 17:57 ` Greg Kroah-Hartman [this message]
2022-09-06 5:48 ` Johan Hovold
2022-09-06 6:46 ` Greg Kroah-Hartman
2022-09-06 7:01 ` Johan Hovold
2022-09-06 11:22 ` Greg Kroah-Hartman
2022-09-06 12:09 ` Johan Hovold
[not found] <20220923165534.652593-1-sashal@kernel.org>
2022-09-24 8:56 ` Johan Hovold
2022-09-24 9:14 ` Greg Kroah-Hartman
2022-09-24 9:22 ` Johan Hovold
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=YxY4hbjs0Y0877Ns@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-commits@vger.kernel.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