From: keith.busch@intel.com (Keith Busch)
Subject: parse_and_open without closing the fd
Date: Mon, 20 Nov 2017 13:21:28 -0700 [thread overview]
Message-ID: <20171120202128.GC12587@localhost.localdomain> (raw)
In-Reply-To: <13087d0e-c7e7-521b-e029-6f6a71e153ba@oracle.com>
On Mon, Nov 20, 2017@03:11:28PM -0500, Thomas Tai wrote:
> > It's implicitly closed on exit. This is a short-lived one-shot program,
> > so there is some laziness with accounting for all resources that are
> > automatically reclaimed. That said, it's still nice to clean this up as
> > we find such examples.
> >
>
> I see. Thanks Keith for your quick response.
Fixed now. :)
prev parent reply other threads:[~2017-11-20 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 20:04 parse_and_open without closing the fd Thomas Tai
2017-11-20 20:13 ` Keith Busch
2017-11-20 20:11 ` Thomas Tai
2017-11-20 20:21 ` Keith Busch [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=20171120202128.GC12587@localhost.localdomain \
--to=keith.busch@intel.com \
/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