From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Kaige Li <likaige@loongson.cn>
Cc: linux-mips@vger.kernel.org, Tiezhu Yang <yangtiezhu@loongson.cn>,
Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [PATCH] MIPS: tools: Fix resource leak in elf-entry.c
Date: Sun, 24 May 2020 09:41:25 +0200 [thread overview]
Message-ID: <20200524074125.GE4161@alpha.franken.de> (raw)
In-Reply-To: <1589461181-29695-1-git-send-email-likaige@loongson.cn>
On Thu, May 14, 2020 at 08:59:41PM +0800, Kaige Li wrote:
> There is a file descriptor resource leak in elf-entry.c, fix this
> by adding fclose() before return and die.
>
> Signed-off-by: Kaige Li <likaige@loongson.cn>
> ---
> arch/mips/tools/elf-entry.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-05-24 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:59 [PATCH] MIPS: tools: Fix resource leak in elf-entry.c Kaige Li
2020-05-24 7:41 ` Thomas Bogendoerfer [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=20200524074125.GE4161@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=likaige@loongson.cn \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=yangtiezhu@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).