From: Rob Herring <robh@kernel.org>
To: Zijun Hu <zijun_hu@icloud.com>
Cc: Saravana Kannan <saravanak@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Marc Zyngier <maz@kernel.org>,
Stefan Wiehler <stefan.wiehler@nokia.com>,
Tony Lindgren <tony@atomide.com>,
Thierry Reding <thierry.reding@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Julia Lawall <Julia.Lawall@lip6.fr>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Zijun Hu <quic_zijuhu@quicinc.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 0/9] of: fix bugs about refcount
Date: Mon, 24 Feb 2025 17:26:45 -0600 [thread overview]
Message-ID: <20250224232645.GA117818-robh@kernel.org> (raw)
In-Reply-To: <20250209-of_irq_fix-v2-0-93e3a2659aa7@quicinc.com>
On Sun, Feb 09, 2025 at 08:58:53PM +0800, Zijun Hu wrote:
> This patch series is to fix of bugs about refcount.
>
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
> ---
> Changes in v2:
> - Add 2 unittest patches + 1 refcount bug fix + 1 refcount comments patch
> - Correct titles and commit messages
> - Link to v1: https://lore.kernel.org/r/20241209-of_irq_fix-v1-0-782f1419c8a1@quicinc.com
>
> ---
> Zijun Hu (9):
> of: unittest: Add a case to test if API of_irq_parse_one() leaks refcount
> of/irq: Fix device node refcount leakage in API of_irq_parse_one()
> of: unittest: Add a case to test if API of_irq_parse_raw() leaks refcount
> of/irq: Fix device node refcount leakage in API of_irq_parse_raw()
> of/irq: Fix device node refcount leakages in of_irq_count()
> of/irq: Fix device node refcount leakage in API irq_of_parse_and_map()
> of/irq: Fix device node refcount leakages in of_irq_init()
> of/irq: Add comments about refcount for API of_irq_find_parent()
> of: resolver: Fix device node refcount leakage in of_resolve_phandles()
>
> drivers/of/irq.c | 34 ++++++++++---
> drivers/of/resolver.c | 2 +
> drivers/of/unittest-data/tests-interrupts.dtsi | 13 +++++
> drivers/of/unittest.c | 67 ++++++++++++++++++++++++++
> 4 files changed, 110 insertions(+), 6 deletions(-)
I've applied the series. I made a few adjustments to use __free()
cleanup and simplify things.
Rob
next prev parent reply other threads:[~2025-02-24 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 12:58 [PATCH v2 0/9] of: fix bugs about refcount Zijun Hu
2025-02-09 12:58 ` [PATCH v2 2/9] of/irq: Fix device node refcount leakage in API of_irq_parse_one() Zijun Hu
2025-02-09 12:58 ` [PATCH v2 4/9] of/irq: Fix device node refcount leakage in API of_irq_parse_raw() Zijun Hu
2025-02-09 12:58 ` [PATCH v2 5/9] of/irq: Fix device node refcount leakages in of_irq_count() Zijun Hu
2025-02-09 12:58 ` [PATCH v2 6/9] of/irq: Fix device node refcount leakage in API irq_of_parse_and_map() Zijun Hu
2025-02-09 12:59 ` [PATCH v2 7/9] of/irq: Fix device node refcount leakages in of_irq_init() Zijun Hu
2025-02-09 12:59 ` [PATCH v2 9/9] of: resolver: Fix device node refcount leakage in of_resolve_phandles() Zijun Hu
2025-02-24 23:26 ` Rob Herring [this message]
2025-02-25 12:17 ` [PATCH v2 0/9] of: fix bugs about refcount Zijun Hu
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=20250224232645.GA117818-robh@kernel.org \
--to=robh@kernel.org \
--cc=Julia.Lawall@lip6.fr \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=quic_zijuhu@quicinc.com \
--cc=saravanak@google.com \
--cc=stable@vger.kernel.org \
--cc=stefan.wiehler@nokia.com \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=zijun_hu@icloud.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