From: Borislav Petkov <bp@alien8.de>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: Rounak Das <rounakdas2025@gmail.com>,
tony.luck@intel.com, stable@vger.kernel.org,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] EDAC/altera: Fix device node reference leaks in the SDMMC ECC setup
Date: Mon, 20 Jul 2026 09:13:03 -0700 [thread overview]
Message-ID: <20260720161303.GAal5JD89lrQVa44ZV@fat_crate.local> (raw)
In-Reply-To: <e1ef6af9-3040-44ae-ad00-5e9011c8edda@kernel.org>
On Mon, Jul 20, 2026 at 09:13:25AM -0500, Dinh Nguyen wrote:
> > Under altr_portb_setup() and socfpga_init_sdmmc_ecc(),
> > of_find_compatible_node() was being used to look up the sdmmc-ecc
> > node. This node wasn't being dropped using of_node_put().
> >
> > altr_portb_setup() did not drop its reference under its success path
> > or on any error path.
> >
> > socfpga_init_sdmmc_ecc() did an early return thereby skipping the
> > common exit label and thus leaking the reference.
> >
> > Add the missing of_node_put() calls in altr_portb_setup(), and route
> > socfpga_init_sdmmc_ecc()'s success path through the common exit label.
> >
> > Fixes: 911049845d70 ("EDAC, altera: Add Arria10 SD-MMC EDAC support")
> > Fixes: 788586efd116 ("EDAC/altera: Initialize peripheral FIFOs in probe()")
> > Cc: stable@vger.kernel.org
> > Closes: https://sashiko.dev/#/patchset/20260708091135.94114-1-rounakdas2025%40gmail.com
> > Signed-off-by: Rounak Das <rounakdas2025@gmail.com>
> > ---
>
> Acked-by: Dinh Nguyen <dinguyen@kernel.org>
I'll hold off on that until the Sashiko preexisting issues have been
addressed:
https://sashiko.dev/#/patchset/20260717102549.13309-1-rounakdas2025%40gmail.com
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2026-07-20 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 10:25 [PATCH] EDAC/altera: Fix device node reference leaks in the SDMMC ECC setup Rounak Das
2026-07-17 11:48 ` Dinh Nguyen
2026-07-17 13:17 ` [PATCH v2] " Rounak Das
2026-07-20 14:13 ` Dinh Nguyen
2026-07-20 16:13 ` Borislav Petkov [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=20260720161303.GAal5JD89lrQVa44ZV@fat_crate.local \
--to=bp@alien8.de \
--cc=dinguyen@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rounakdas2025@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.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