mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: LuMingYin <lumingyindetect@126.com>
Cc: LuMingYin <lumingyindetect@163.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] tools: Fix a memory leak in disas_funcs()
Date: Sun, 28 Apr 2024 10:52:52 +0200	[thread overview]
Message-ID: <ca80e477-0008-468d-8e33-cbf1d61f223d@web.de> (raw)
In-Reply-To: <20240323065550.603005-1-lumingyindetect@163.com>

…
> However, after using the memory area pointed to by 'cmd' (line 4619), it is not deallocated, resulting in a memory leak bug. This commit fixes the bug.

Please take advices from known information sources better into account.

* https://kernelnewbies.org/FirstKernelPatch

* https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc5#n3


I got the impression that Josh Poimboeuf answered your development concern already.
https://lore.kernel.org/lkml/20240323182209.xqzb6rsswvfbg74n@treble/
https://lkml.org/lkml/2024/3/23/285


Would you like to support faster execution of the mentioned program
so that manual memory releases can be omitted so far?


Did your email address change in the meantime?

Regards,
Markus

      parent reply	other threads:[~2024-04-28  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23  6:55 [PATCH] tools:Fix a memory leak bug related to the cmd LuMingYin
2024-03-24  5:56 ` lumingyindetect
2024-04-28  8:52 ` Markus Elfring [this message]

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=ca80e477-0008-468d-8e33-cbf1d61f223d@web.de \
    --to=markus.elfring@web.de \
    --cc=jpoimboe@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumingyindetect@126.com \
    --cc=lumingyindetect@163.com \
    --cc=peterz@infradead.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®