From: Robert Richter <rrichter@amd.com>
To: Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: dave@stgolabs.net, jonathan.cameron@huawei.com,
dave.jiang@intel.com, alison.schofield@intel.com,
vishal.l.verma@intel.com, ira.weiny@intel.com,
dan.j.williams@intel.com, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.li@zohomail.com,
peterz@infradead.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v2] cxl/memdev: automate cleanup with __free()
Date: Tue, 24 Jun 2025 17:17:12 +0200 [thread overview]
Message-ID: <aFrBeCn-j_AB1yzv@rric.localdomain> (raw)
In-Reply-To: <20250623083841.364002-1-pranav.tyagi03@gmail.com>
On 23.06.25 14:08:41, Pranav Tyagi wrote:
> Use the scope based resource management (defined in linux/cleanup.h) to
> automate the lifetime control of struct cxl_mbox_transfer_fw. This
> eliminates explicit kfree() calls and makes the code more robust and
> maintainable in presence of early returns.
>
> Signed-off-by: Pranav Tyagi <pranav.tyagi03@gmail.com>
> ---
> drivers/cxl/core/memdev.c | 21 ++++++++-------------
> 1 file changed, 8 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
> index f88a13adf7fa..38f4449f9740 100644
> --- a/drivers/cxl/core/memdev.c
> +++ b/drivers/cxl/core/memdev.c
> @@ -7,6 +7,7 @@
> #include <linux/slab.h>
> #include <linux/idr.h>
> #include <linux/pci.h>
> +#include <linux/cleanup.h>
> #include <cxlmem.h>
> #include "trace.h"
> #include "core.h"
> @@ -802,11 +803,10 @@ static int cxl_mem_activate_fw(struct cxl_memdev_state *mds, int slot)
> static int cxl_mem_abort_fw_xfer(struct cxl_memdev_state *mds)
> {
> struct cxl_mailbox *cxl_mbox = &mds->cxlds.cxl_mbox;
> - struct cxl_mbox_transfer_fw *transfer;
> struct cxl_mbox_cmd mbox_cmd;
> - int rc;
> -
> - transfer = kzalloc(struct_size(transfer, data, 0), GFP_KERNEL);
> +
> + struct cxl_mbox_transfer_fw *transfer __free(kfree) =
> + kzalloc(struct_size(transfer, data, 0), GFP_KERNEL);
I don't see a reason for __free() here as there are no early exits.
> if (!transfer)
> return -ENOMEM;
>
> @@ -821,9 +821,7 @@ static int cxl_mem_abort_fw_xfer(struct cxl_memdev_state *mds)
>
> transfer->action = CXL_FW_TRANSFER_ACTION_ABORT;
>
> - rc = cxl_internal_send_cmd(cxl_mbox, &mbox_cmd);
> - kfree(transfer);
> - return rc;
> + return cxl_internal_send_cmd(cxl_mbox, &mbox_cmd);
> }
>
> static void cxl_fw_cleanup(struct fw_upload *fwl)
> @@ -880,7 +878,7 @@ static enum fw_upload_err cxl_fw_write(struct fw_upload *fwl, const u8 *data,
> struct cxl_dev_state *cxlds = &mds->cxlds;
> struct cxl_mailbox *cxl_mbox = &cxlds->cxl_mbox;
> struct cxl_memdev *cxlmd = cxlds->cxlmd;
> - struct cxl_mbox_transfer_fw *transfer;
> + struct cxl_mbox_transfer_fw *transfer __free(kfree);
Jonathan already catched this.
> struct cxl_mbox_cmd mbox_cmd;
> u32 cur_size, remaining;
> size_t size_in;
> @@ -949,7 +947,7 @@ static enum fw_upload_err cxl_fw_write(struct fw_upload *fwl, const u8 *data,
> rc = cxl_internal_send_cmd(cxl_mbox, &mbox_cmd);
> if (rc < 0) {
> rc = FW_UPLOAD_ERR_RW_ERROR;
> - goto out_free;
> + return rc;
If you want to remove the goto here, just free transfer right after
calling cxl_internal_send_cmd(). It is no longer used then.
I only want those cleanup helpers where they are actually useful and
do not just add complexity.
Thanks,
-Robert
> }
>
> *written = cur_size;
> @@ -963,14 +961,11 @@ static enum fw_upload_err cxl_fw_write(struct fw_upload *fwl, const u8 *data,
> dev_err(&cxlmd->dev, "Error activating firmware: %d\n",
> rc);
> rc = FW_UPLOAD_ERR_HW_ERROR;
> - goto out_free;
> + return rc;
> }
> }
>
> rc = FW_UPLOAD_ERR_NONE;
> -
> -out_free:
> - kfree(transfer);
> return rc;
> }
>
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-06-24 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 8:38 [PATCH v2] cxl/memdev: automate cleanup with __free() Pranav Tyagi
2025-06-24 14:43 ` Jonathan Cameron
2025-06-24 15:17 ` Robert Richter [this message]
2025-06-26 14:32 ` Pranav Tyagi
2025-06-26 14:55 ` Greg KH
2025-06-26 15:12 ` Pranav Tyagi
2025-06-28 3:04 ` Dan Carpenter
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=aFrBeCn-j_AB1yzv@rric.localdomain \
--to=rrichter@amd.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=peterz@infradead.org \
--cc=pranav.tyagi03@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=vishal.l.verma@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