The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] scripts/sorttable: Fix resource leak on file pointer fp
Date: Thu, 27 Feb 2025 09:58:58 +0000	[thread overview]
Message-ID: <ce34b982-490e-44dc-8071-c04d4fbcb0f1@gmail.com> (raw)
In-Reply-To: <a7857c72-89ec-406b-8d66-d9e95657a6e0@stanley.mountain>


[-- Attachment #1.1.1: Type: text/plain, Size: 649 bytes --]

On 27/02/2025 09:57, Dan Carpenter wrote:
> On Wed, Feb 26, 2025 at 10:49:34PM +0000, Colin Ian King wrote:
>> There is a resource leak on fp on an error return path in function
>> parse_symbols that causes a resource leak. Fix this by adding in
>> the missing fclose.
>>
>> Fixes: ef378c3b8233 ("scripts/sorttable: Zero out weak functions in mcount_loc table")
>> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> 
> This is in scripts/ so it doesn't really matter.  We're going to exit
> and release everything immediately either way.

Ack. Won't fix these issues in scripts in future.

> 
> regards,
> dan carpenter
> 


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 4901 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      reply	other threads:[~2025-02-27  9:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 22:49 [PATCH][next] scripts/sorttable: Fix resource leak on file pointer fp Colin Ian King
2025-02-26 23:20 ` Steven Rostedt
2025-02-27  9:57 ` Dan Carpenter
2025-02-27  9:58   ` Colin King (gmail) [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=ce34b982-490e-44dc-8071-c04d4fbcb0f1@gmail.com \
    --to=colin.i.king@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=dan.carpenter@linaro.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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