From: Greg KH <gregkh@linuxfoundation.org>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, jani.nikula@intel.com,
Imre Deak <imre.deak@intel.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
"Rafael J . Wysocki" <rafael@kernel.org>,
intel-gfx@lists.freedesktop.org,
Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [Intel-gfx] [PATCH v2] component: do not leave master devres group open after bind
Date: Wed, 13 Oct 2021 15:09:50 +0200 [thread overview]
Message-ID: <YWbangk7KAxZFoq3@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110061613520.3554566@eliteleevi.tm.intel.com>
On Wed, Oct 06, 2021 at 04:47:57PM +0300, Kai Vehmanen wrote:
> Hi,
>
> On Tue, 5 Oct 2021, Greg KH wrote:
>
> > On Wed, Sep 22, 2021 at 11:54:32AM +0300, Kai Vehmanen wrote:
> > > In current code, the devres group for aggregate master is left open
> > > after call to component_master_add_*(). This leads to problems when the
> > > master does further managed allocations on its own. When any
> > > participating driver calls component_del(), this leads to immediate
> > > release of resources.
> [...]
> > > the devres group, and by closing the devres group after
> > > the master->ops->bind() call is done. This allows devres allocations
> > > done by the driver acting as master to be isolated from the binding state
> > > of the aggregate driver. This modifies the logic originally introduced in
> > > commit 9e1ccb4a7700 ("drivers/base: fix devres handling for master device")
> > >
> > > BugLink: https://gitlab.freedesktop.org/drm/intel/-/issues/4136
> > > Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> > > Acked-by: Imre Deak <imre.deak@intel.com>
> > > Acked-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> >
> > What commit does this "fix:"? And does it need to go to stable
> > kernel(s)?
>
> I didn't put a "Fixes" on the original commit 9e1ccb4a7700
> ("drivers/base: fix devres handling for master device") as it alone
> didn't cause problems. It did open the door for possible devres issues
> for anybody calling component_master_add_().
>
> On audio side, this surfaced with the more recent commit 3fcaf24e5dce
> ("ALSA: hda: Allocate resources with device-managed APIs"). In theory one
> could have hit issues already before, but this made it very easy to hit
> on actual systems.
>
> If I'd have to pick one, it would be 9e1ccb4a7700 ("drivers/base: fix
> devres handling for master device"). And yes, given comments on this
> thread, I'd say this needs to go to stable kernels.
Then please add a fixes: line and a cc: stable line and resend.
thanks,
greg k-h
prev parent reply other threads:[~2021-10-13 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 8:54 [Intel-gfx] [PATCH v2] component: do not leave master devres group open after bind Kai Vehmanen
2021-09-22 10:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success for component: do not leave master devres group open after bind (rev2) Patchwork
2021-09-22 12:52 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-09-28 10:22 ` [Intel-gfx] [PATCH v2] component: do not leave master devres group open after bind Takashi Iwai
2021-09-28 10:45 ` Kai Vehmanen
2021-10-05 14:35 ` Greg KH
2021-10-06 13:47 ` Kai Vehmanen
2021-10-13 13:09 ` Greg KH [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=YWbangk7KAxZFoq3@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=rafael@kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rmk+kernel@armlinux.org.uk \
--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