All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org, Conor Dooley <conor@kernel.org>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Joshua Yeong <joshua.yeong@starfivetech.com>,
	Felix Gu <ustc.gu@gmail.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	Daire McNamara <daire.mcnamara@microchip.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cache: starfive: fix device node leak in starlink_cache_init()
Date: Fri,  6 Feb 2026 20:28:46 +0000	[thread overview]
Message-ID: <20260206-front-jackpot-6d679f8f5232@spud> (raw)
In-Reply-To: <20260131-starlink-v1-1-30985722d51f@gmail.com>

From: Conor Dooley <conor.dooley@microchip.com>

On Sat, 31 Jan 2026 01:13:45 +0800, Felix Gu wrote:
> of_find_matching_node() returns a device_node with refcount incremented.
> 
> Use __free(device_node) attribute to automatically call of_node_put()
> when the variable goes out of scope, preventing the refcount leak.
> 
> 

Applied to riscv-soc-fixes, thanks!

[1/1] cache: starfive: fix device node leak in starlink_cache_init()
      https://git.kernel.org/conor/c/3c85234b979a

Thanks,
Conor.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org, Conor Dooley <conor@kernel.org>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Joshua Yeong <joshua.yeong@starfivetech.com>,
	Felix Gu <ustc.gu@gmail.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	Daire McNamara <daire.mcnamara@microchip.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cache: starfive: fix device node leak in starlink_cache_init()
Date: Fri,  6 Feb 2026 20:28:46 +0000	[thread overview]
Message-ID: <20260206-front-jackpot-6d679f8f5232@spud> (raw)
In-Reply-To: <20260131-starlink-v1-1-30985722d51f@gmail.com>

From: Conor Dooley <conor.dooley@microchip.com>

On Sat, 31 Jan 2026 01:13:45 +0800, Felix Gu wrote:
> of_find_matching_node() returns a device_node with refcount incremented.
> 
> Use __free(device_node) attribute to automatically call of_node_put()
> when the variable goes out of scope, preventing the refcount leak.
> 
> 

Applied to riscv-soc-fixes, thanks!

[1/1] cache: starfive: fix device node leak in starlink_cache_init()
      https://git.kernel.org/conor/c/3c85234b979a

Thanks,
Conor.

  parent reply	other threads:[~2026-02-06 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 17:13 [PATCH] cache: starfive: fix device node leak in starlink_cache_init() Felix Gu
2026-01-30 17:28 ` Jonathan Cameron
2026-02-06 20:28 ` Conor Dooley [this message]
2026-02-06 20:28   ` Conor Dooley

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=20260206-front-jackpot-6d679f8f5232@spud \
    --to=conor@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathan.cameron@huawei.com \
    --cc=joshua.yeong@starfivetech.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=ustc.gu@gmail.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.