mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jackysliu <1972843537@qq.com>
To: krzk@kernel.org
Cc: 1972843537@qq.com, andreas@gaisler.com, davem@davemloft.net,
	linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re:[PATCH] arch: fix resource leak in chmc.c
Date: Mon, 21 Jul 2025 10:04:54 +0800	[thread overview]
Message-ID: <tencent_20E2BADCCAFB7724FDBFCB3443A070A51D0A@qq.com> (raw)
In-Reply-To: <25e7455e-816c-448a-b78b-94fe9437e3c8@kernel.org>

On Fri, Jul 18 2025 15:25:47 +0200  Krzysztof Kozlowski wrote:
>Last time you were using AI, so I have doubts this is "static tools".
>Please describe it properly, so we can make informed decision whether to
>allocate time on this.

The tool determines which api is responsible for resource request 
and release, and determines if there are resource leak or double free 
issues in the code by determining the use of release specifications.
So no AI involved, don't worry.

>Nah, just free it immediately after user. Don't over complicate this.
OK, I'll resubmit a new patch later


Siyang Liu


  reply	other threads:[~2025-07-21  2:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  9:22 [PATCH] " Jacky Liu
2025-07-18 13:25 ` Krzysztof Kozlowski
2025-07-21  2:04   ` jackysliu [this message]
2025-07-18 13:43 ` Markus Elfring
2025-07-21  3:57   ` [PATCH v2] arch: fix resource leak in jbusmc_probe() jackysliu
2025-07-21  7:18     ` Markus Elfring
2025-07-21  7:55       ` [PATCH v3] sparc: " jackysliu
2025-07-21  8:17         ` Markus Elfring
2025-07-22  6:22         ` Krzysztof Kozlowski
2025-07-21  8:25     ` [PATCH v2] arch: " Krzysztof Kozlowski

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=tencent_20E2BADCCAFB7724FDBFCB3443A070A51D0A@qq.com \
    --to=1972843537@qq.com \
    --cc=andreas@gaisler.com \
    --cc=davem@davemloft.net \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.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®