public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crrodriguez at opensuse dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/16734] fopen calls mmap to allocate its buffer
Date: Thu, 19 Feb 2015 20:49:00 -0000 [thread overview]
Message-ID: <bug-16734-131-sV9k2NEitC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16734-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16734
Cristian Rodríguez <crrodriguez at opensuse dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crrodriguez at opensuse dot org
--
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-27523-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Feb 20 09:21:03 2015
Return-Path: <glibc-bugs-return-27523-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 15247 invoked by alias); 20 Feb 2015 09:21:02 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 15143 invoked by uid 48); 20 Feb 2015 09:20:58 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/17829] Incorrect handling of precision specifier in printf family
Date: Fri, 20 Feb 2015 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: stdio
X-Bugzilla-Version: 2.19
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: flagtypes.name
Message-ID: <bug-17829-131-l4o8eqWIAn@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17829-131@http.sourceware.org/bugzilla/>
References: <bug-17829-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-02/txt/msg00258.txt.bz2
Content-length: 991
https://sourceware.org/bugzilla/show_bug.cgi?id\x17829
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to nfxjfg from comment #3)
> >Certainly, this use is not recommended because printf will allocate tons of memory as part of the format processing.
>
> There's literally no reason why it'd need to allocate memory of the size of
> the maximum _possible_ length of the string. In fact, I'd argue printf
> doesn't need to do unbounded memory allocations at all.
But it's what the code does today. It could be implemented differently, sure,
but until someone writes the code, submits it, and gets it through review, it's
how things are.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-02-19 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 11:27 [Bug stdio/16734] New: " dancol at dancol dot org
2014-06-13 9:18 ` [Bug stdio/16734] " fweimer at redhat dot com
2015-02-14 22:55 ` ppluzhnikov at google dot com
2015-02-19 20:49 ` crrodriguez at opensuse dot org [this message]
2015-03-08 16:50 ` cvs-commit at gcc dot gnu.org
2015-06-06 9:43 ` neleai at seznam dot cz
2015-06-07 2:27 ` ppluzhnikov at google dot com
2015-08-13 1:57 ` cvs-commit at gcc dot gnu.org
2015-08-13 2:00 ` ppluzhnikov at google dot com
2015-10-29 16:28 ` jsm28 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-16734-131-sV9k2NEitC@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).