All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Saravana Kannan" <saravanak@google.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Hervé Codina" <herve.codina@bootlin.com>,
	linux-kernel@vger.kernel.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH RESEND v2] drivers: core: fix device leak in __fw_devlink_relax_cycles()
Date: Wed, 5 Mar 2025 09:07:05 +0100	[thread overview]
Message-ID: <20250305090705.4b2eb1e9@booty> (raw)
In-Reply-To: <2025030332-tumble-seduce-7650@gregkh>

Hello Greg,

On Mon, 3 Mar 2025 15:07:53 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:

> On Mon, Mar 03, 2025 at 10:30:51AM +0100, Luca Ceresoli wrote:
> > Commit bac3b10b78e5 ("driver core: fw_devlink: Stop trying to optimize
> > cycle detection logic") introduced a new struct device *con_dev and a
> > get_dev_from_fwnode() call to get it, but without adding a corresponding
> > put_device().
> > 
> > Closes: https://lore.kernel.org/all/20241204124826.2e055091@booty/
> > Fixes: bac3b10b78e5 ("driver core: fw_devlink: Stop trying to optimize cycle detection logic")
> > Cc: stable@vger.kernel.org
> > Reviewed-by: Saravana Kannan <saravanak@google.com>
> > Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> > ---
> > Changes in v2:
> > - add 'Cc: stable@vger.kernel.org'
> > - use Closes: tag, not Link:
> > - Link to v1: https://lore.kernel.org/r/20250212-fix__fw_devlink_relax_cycles_missing_device_put-v1-1-41818c7d7722@bootlin.com
> > ---
> >  drivers/base/core.c | 1 +
> >  1 file changed, 1 insertion(+)  
> 
> This was applied to my tree on Feb 20, right?  Or is this a new version?
> Why was it resent?

I just didn't know it got applied, sorry for the noise. Being a fix, I
was expecting to see it in current master where but it isn't there yet.
Assuming it will be soon, you can ignore it.

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2025-03-05  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03  9:30 [PATCH RESEND v2] drivers: core: fix device leak in __fw_devlink_relax_cycles() Luca Ceresoli
2025-03-03 14:07 ` Greg Kroah-Hartman
2025-03-05  8:07   ` Luca Ceresoli [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=20250305090705.4b2eb1e9@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=akpm@linux-foundation.org \
    --cc=dakr@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=herve.codina@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=saravanak@google.com \
    --cc=stable@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.