From: Prasanna Kumar T S M <ptsm@linux.microsoft.com>
To: Borislav Petkov <bp@alien8.de>
Cc: shubhrajyoti.datta@amd.com, tony.luck@intel.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 4/5] EDAC/versalnet: Fix device_register() error handling in init_one_mc()
Date: Mon, 23 Mar 2026 12:38:57 +0530 [thread overview]
Message-ID: <84ae7198-b755-4dde-b97c-978958d27b4b@linux.microsoft.com> (raw)
In-Reply-To: <20260322161052.GAacAUjFGWFwPle6c9@fat_crate.local>
On 22-03-2026 21:40, Borislav Petkov wrote:
> On Sun, Mar 22, 2026 at 06:11:45AM -0700, Prasanna Kumar T S M wrote:
>> When device_register() fails, it must be followed by put_device()
>> rather than kfree(), because device_register() calls
>> device_initialize() which sets up the device refcount. The matching
>> release function versal_edac_release() handles the actual kfree().
>>
>> Also reorder the dev allocation to after edac_mc_alloc() so the error
>> path no longer needs a separate err_dev_free label.
>
> Nope.
>
> edac_mc_alloc() is a lot more heavy-weight than a simple k*alloc(). Pls keep
> the ordering as it is.
Re-ordering this simplifies the error handling path. See below for details.
>
>> Fixes: d5fe2fec6c40d ("EDAC: Add a driver for the AMD Versal NET DDR controller")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Prasanna Kumar T S M <ptsm@linux.microsoft.com>
>> ---
>> drivers/edac/versalnet_edac.c | 16 ++++++++--------
>> 1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/edac/versalnet_edac.c b/drivers/edac/versalnet_edac.c
>> index acd51b492772..6463e88ed3d3 100644
>> --- a/drivers/edac/versalnet_edac.c
>> +++ b/drivers/edac/versalnet_edac.c
>> @@ -817,24 +817,26 @@ static int init_one_mc(struct mc_priv *priv, struct platform_device *pdev, int i
>> if (!name)
>> return rc;
>>
>> - dev = kzalloc(sizeof(*dev), GFP_KERNEL);
>> - if (!dev)
>> - goto err_name_free;
>> -
>> mci = edac_mc_alloc(i, ARRAY_SIZE(layers), layers, sizeof(struct mc_priv));
>> if (!mci) {
>> edac_printk(KERN_ERR, EDAC_MC, "Failed memory allocation for MC%d\n", i);
>> - goto err_dev_free;
>> + goto err_name_free;
>> }
>>
>> + dev = kzalloc(sizeof(*dev), GFP_KERNEL);
>> + if (!dev)
>> + goto err_mc_free;
>> +
>> sprintf(name, "versal-net-ddrmc5-edac-%d", i);
>>
>> dev->init_name = name;
>> dev->release = versal_edac_release;
>>
>> rc = device_register(dev);
>> - if (rc)
>> + if (rc) {
>> + put_device(dev);
>
> Why here and not at the error label below?
After calling device_register(), put_device() has to be used
irrespective of the return value. In this case, kfree(dev) will happen
as a part of put_device().
If device_register() was not called, kfree(dev) has to be called to free
the memory.
If kzalloc(dev) is done after edac_mc_alloc(), there is no need to
decide between kfree(dev) or put_device(dev). This simplifies the error
handling path. This is the reason behind re-ordering and keeping
put_device(dev) under 'if (rc) { ... }'.
>
>> goto err_mc_free;
>> + }
>>
>> mci->pdev = dev;
>> mc_init(mci, dev);
>> @@ -856,8 +858,6 @@ static int init_one_mc(struct mc_priv *priv, struct platform_device *pdev, int i
>> device_unregister(mci->pdev);
>> err_mc_free:
>> edac_mc_free(mci);
>> -err_dev_free:
>> - kfree(dev);
>> err_name_free:
>> kfree(name);
>>
>> --
>> 2.49.0
>>
>
Do you think it is best to do edac_mc_alloc() before kzalloc(dev)?
Thanks,
Prasanna Kumar
next prev parent reply other threads:[~2026-03-23 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 13:11 [PATCH 1/5] EDAC/versalnet: Fix teardown ordering in mc_remove() Prasanna Kumar T S M
2026-03-22 13:11 ` [PATCH 2/5] EDAC/versalnet: Release reference to remoteproc device in remove Prasanna Kumar T S M
2026-03-22 15:59 ` Borislav Petkov
2026-03-23 7:25 ` Prasanna Kumar T S M
2026-03-22 13:11 ` [PATCH 3/5] EDAC/versalnet: Fix memory leak in remove and probe error paths Prasanna Kumar T S M
2026-03-22 19:15 ` Borislav Petkov
2026-03-22 13:11 ` [PATCH 4/5] EDAC/versalnet: Fix device_register() error handling in init_one_mc() Prasanna Kumar T S M
2026-03-22 16:10 ` Borislav Petkov
2026-03-23 7:08 ` Prasanna Kumar T S M [this message]
2026-03-24 11:23 ` Borislav Petkov
2026-03-24 12:16 ` Borislav Petkov
2026-03-22 13:11 ` [PATCH 5/5] EDAC/versalnet: Fix device name memory leak Prasanna Kumar T S M
2026-03-22 16:15 ` Borislav Petkov
2026-03-23 6:59 ` Prasanna Kumar T S M
2026-03-26 17:23 ` kernel test robot
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=84ae7198-b755-4dde-b97c-978958d27b4b@linux.microsoft.com \
--to=ptsm@linux.microsoft.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shubhrajyoti.datta@amd.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