mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akhilesh Patil <akhilesh@ee.iitb.ac.in>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: akhileshpatilvnit@gmail.com, LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Dave Jiang <dave.jiang@intel.com>,
	Itay Avraham <itayavr@nvidia.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] fwctl: mlx5: fix memory alloc/free in mlx5ctl_fw_rpc()
Date: Sat, 16 Aug 2025 10:13:17 +0530	[thread overview]
Message-ID: <aKAMZenB2iqSSfd3@bhairav-test.ee.iitb.ac.in> (raw)
In-Reply-To: <35e23690-a907-4606-a484-e3e342a14e7c@web.de>

On Fri, Aug 15, 2025 at 04:40:10PM +0200, Markus Elfring wrote:
> > Use kvfree() to free memory allocated by kvzalloc() instead of kfree().
> > Avoid potential memory management issue by matching alloc/free routines.
> 
> Will another bit of background information become helpful
> for an improved change description?
> 
> Test command example:
> Markus_Elfring@Sonne:…/Projekte/Linux/next-analyses> /usr/bin/spatch -D report scripts/coccinelle/api/kfree_mismatch.cocci drivers/fwctl/mlx5/main.c

Sure, I will update the commit message to add this and push v2.
Thanks Markus for the suggestion. 

Regards,
Akhilesh

> …
> 
> Regards,
> Markus

  reply	other threads:[~2025-08-16  4:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10 18:17 Akhilesh Patil
2025-08-11 15:28 ` Dave Jiang
2025-08-15 14:40 ` Markus Elfring
2025-08-16  4:43   ` Akhilesh Patil [this message]
2025-08-15 18:59 ` Alison Schofield
2025-08-16  4:47   ` Akhilesh Patil
2025-08-16  6:19 ` [PATCH v2] " Akhilesh Patil
2025-08-18 18:33   ` Alison Schofield
2025-08-18 23:53   ` Jason Gunthorpe
2025-08-18 23:55   ` Jason Gunthorpe

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=aKAMZenB2iqSSfd3@bhairav-test.ee.iitb.ac.in \
    --to=akhilesh@ee.iitb.ac.in \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Markus.Elfring@web.de \
    --cc=akhileshpatilvnit@gmail.com \
    --cc=dave.jiang@intel.com \
    --cc=itayavr@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=skhan@linuxfoundation.org \
    /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®