From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Peng Fan <fanpeng@loongson.cn>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mips/vdso: Fix resource leaks in genvdso.c
Date: Thu, 16 Jul 2020 11:55:58 +0200 [thread overview]
Message-ID: <20200716095558.GF8455@alpha.franken.de> (raw)
In-Reply-To: <1594729818-7859-1-git-send-email-fanpeng@loongson.cn>
On Tue, Jul 14, 2020 at 08:30:18PM +0800, Peng Fan wrote:
> Close "fd" before the return of map_vdso() and close "out_file"
> in main().
>
> Signed-off-by: Peng Fan <fanpeng@loongson.cn>
> ---
>
> v2:
> - add one missing fclose()
>
> ---
> arch/mips/vdso/genvdso.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
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-07-16 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 12:30 [PATCH v2] mips/vdso: Fix resource leaks in genvdso.c Peng Fan
2020-07-16 9:55 ` 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=20200716095558.GF8455@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=fanpeng@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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;
as well as URLs for NNTP newsgroup(s).