From: Dinh Nguyen <dinguyen@kernel.org>
To: Rounak Das <rounakdas2025@gmail.com>
Cc: bp@alien8.de, tony.luck@intel.com,
niravkumar.l.rabara@altera.com, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 3/4] EDAC/altera: Fix code leak on dci allocation failure
Date: Fri, 14 Aug 2026 08:21:55 -0500 [thread overview]
Message-ID: <ea68e8dc-3b5e-45eb-8822-d72b1c358c51@kernel.org> (raw)
In-Reply-To: <CAPYTKoPpccGRmu60qhzxUy7MAoH40z3B=ioUN4qCSFFmPakWmQ@mail.gmail.com>
Hi Rounak
On 8/6/26 13:16, Rounak Das wrote:
> Hi Dinh,
>
>> - if (!devres_open_group(device->edac->dev, altr_portb_setup, GFP_KERNEL))
>> + if (!devres_open_group(device->edac->dev, altr_portb_setup, GFP_KERNEL)) {
>> + edac_device_free_ctl_info(dci);
>> return -ENOMEM;
>> + }
>
> This overlaps with my of_node_put fix that was acked on 2026-07-20
> (20260717131720.19038-1-rounakdas2025@gmail.com), which was held
> until the sashiko issues were addressed.
>
> Patches 3/4 and 4/4 touch the same two hunks in altr_portb_setup(): the
> devres_open_group() failure path and the err_release_group_1 label. Both
> changes are needed in the first one, i.e.
>
> if (!devres_open_group(...)) {
> edac_device_free_ctl_info(dci);
> of_node_put(np);
> return -ENOMEM;
> }
>
> so whichever goes in second will need a rebase. Happy to resend mine on
> top of this series if that ordering is easier.
>
Can I ask you to rebase and resend it once this series lands?
Thanks,
Dinh
next prev parent reply other threads:[~2026-08-14 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 15:54 [PATCHv2 0/4] EDAC/altera: Address sashiko reviews part 1(v2) Dinh Nguyen
2026-08-06 15:54 ` [PATCHv2 1/4] EDAC/altera: Add suppress_bind_attrs so driver cannot get unbound Dinh Nguyen
2026-08-14 3:56 ` Borislav Petkov
2026-08-06 15:54 ` [PATCHv2 2/4] EDAC/altera: Drop __init from ECC setup paths for re-probe safety Dinh Nguyen
2026-08-06 15:54 ` [PATCHv2 3/4] EDAC/altera: Fix code leak on dci allocation failure Dinh Nguyen
2026-08-06 18:16 ` Rounak Das
2026-08-14 13:21 ` Dinh Nguyen [this message]
2026-08-06 15:54 ` [PATCHv2 4/4] EDAC/altera: Fix use-after-free in error paths Dinh Nguyen
2026-08-14 2:15 ` [PATCHv2 0/4] EDAC/altera: Address sashiko reviews part 1(v2) Borislav Petkov
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=ea68e8dc-3b5e-45eb-8822-d72b1c358c51@kernel.org \
--to=dinguyen@kernel.org \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niravkumar.l.rabara@altera.com \
--cc=rounakdas2025@gmail.com \
--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