From: Li Ming <ming.li@zohomail.com>
To: Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: rrichter@amd.com, peterz@infradead.org,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
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
Subject: Re: [PATCH] cxl/memdev: automate cleanup with __free()
Date: Sun, 22 Jun 2025 20:22:45 +0800 [thread overview]
Message-ID: <50a01a17-4afc-415d-b5c8-9a84e3bdf191@zohomail.com> (raw)
In-Reply-To: <20250622120958.475765-1-pranav.tyagi03@gmail.com>
On 6/22/2025 8:09 PM, 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 | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
> index f88a13adf7fa..be73a6099cb6 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,11 @@ 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);
> if (!transfer)
> return -ENOMEM;
>
> @@ -822,7 +823,6 @@ 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;
the rc can be removed with your change, can be "return cxl_internal_send_cmd(cxl_mbox, &mbox_cmd)".
> }
>
> @@ -880,7 +880,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);
> struct cxl_mbox_cmd mbox_cmd;
> u32 cur_size, remaining;
> size_t size_in;
> @@ -970,7 +970,6 @@ static enum fw_upload_err cxl_fw_write(struct fw_upload *fwl, const u8 *data,
> rc = FW_UPLOAD_ERR_NONE;
>
> out_free:
> - kfree(transfer);
> return rc;
> }
>
I believe all "goto out_free" in the function are not needed with your change.
Ming
next prev parent reply other threads:[~2025-06-22 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 12:09 Pranav Tyagi
2025-06-22 12:22 ` Li Ming [this message]
2025-06-22 12:50 ` Pranav Tyagi
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=50a01a17-4afc-415d-b5c8-9a84e3bdf191@zohomail.com \
--to=ming.li@zohomail.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=peterz@infradead.org \
--cc=pranav.tyagi03@gmail.com \
--cc=rrichter@amd.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
all inboxes | Powered by JetHome®