public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/98129] Failure on reading big chunk of /dev/urandom
Date: Fri, 04 Dec 2020 22:28:17 +0000 [thread overview]
Message-ID: <bug-98129-4-Vx1tK3apCo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98129-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98129
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to anlauf from comment #9)
> The patch seems to regtest ok, but certainly needs some wider testing.
Actually, I think the bug is in io/unix.c:raw_read. That should take
care of repeating the reads as needed.
Seems like that, if nbyte <= MAX_CHUNK, we do not take account of the
possibility of a short read.
next prev parent reply other threads:[~2020-12-04 22:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 20:01 [Bug libfortran/98129] New: " tkoenig at gcc dot gnu.org
2020-12-04 10:41 ` [Bug libfortran/98129] " dominiq at lps dot ens.fr
2020-12-04 12:40 ` tkoenig at gcc dot gnu.org
2020-12-04 12:50 ` tkoenig at gcc dot gnu.org
2020-12-04 15:27 ` kargl at gcc dot gnu.org
2020-12-04 16:17 ` tkoenig at gcc dot gnu.org
2020-12-04 18:16 ` kargl at gcc dot gnu.org
2020-12-04 18:37 ` anlauf at gcc dot gnu.org
2020-12-04 21:32 ` anlauf at gcc dot gnu.org
2020-12-04 22:09 ` anlauf at gcc dot gnu.org
2020-12-04 22:28 ` tkoenig at gcc dot gnu.org [this message]
2020-12-04 22:38 ` anlauf at gcc dot gnu.org
2021-01-21 21:58 ` anlauf at gcc dot gnu.org
2021-01-22 12:12 ` anlauf at gcc dot gnu.org
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=bug-98129-4-Vx1tK3apCo@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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).