From: Caleb Ristvedt <caleb.ristvedt@cune.org>
To: 41204@debbugs.gnu.org
Subject: bug#41204: port-revealed count is initially > 30000
Date: Tue, 12 May 2020 05:32:07 -0500 [thread overview]
Message-ID: <878shxqw9k.fsf@cune.org> (raw)
(port-revealed (open-input-file "/dev/null"))
=> 32539
The little investigating I've done so far suggests that this is because
scm_i_fdes_to_port calls scm_gc_malloc_pointerless and initializes only
the 'fdes' and 'options' fields, leaving 'revealed' uninitialized. The
comment above scm_gc_malloc_pointerless does a good job of explaining
why this is an issue:
/* Allocate SIZE bytes of memory whose contents should not be scanned
for pointers (useful, e.g., for strings). Note though that this
memory is *not* cleared; be sure to initialize it to prevent
information leaks. */
This issue appears to be present both in the 2.2 and 3.0 releases
packaged in guix.
- reepca
next reply other threads:[~2020-05-12 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 10:32 Caleb Ristvedt [this message]
2020-05-12 13:04 ` bug#41204: port-revealed count is initially > 30000 Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878shxqw9k.fsf@cune.org \
--to=caleb.ristvedt@cune.org \
--cc=41204@debbugs.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).