public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12685] fopen doesn't honor last byte of valid modes
Date: Sun, 22 Apr 2012 01:59:00 -0000	[thread overview]
Message-ID: <bug-12685-131-zEinqcuvFZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12685-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12685

Michael Kerrisk <mtk.manpages at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |mtk.manpages at gmail dot
                   |                            |com
         Resolution|FIXED                       |

--- Comment #2 from Michael Kerrisk <mtk.manpages at gmail dot com> 2012-04-22 01:58:14 UTC ---
Actually, is there any reason at all to limit the length of the string? Whay
not parse until NUL? Given that "mode" may be a constructed string, or that
other flags may be added in the future, it seems that arbitrarily limiting the
length of the string to some number of bytes is just setting up both glibc and
userspace bugs for the future.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-04-22  1:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  0:46 [Bug libc/12685] New: fopen doesn't " eblake at redhat dot com
2011-04-20  0:47 ` [Bug libc/12685] fopen doesn't honor " eblake at redhat dot com
2011-04-20  0:52 ` ppluzhnikov at google dot com
2011-04-23  3:42 ` drepper.fsp at gmail dot com
2012-04-22  1:59 ` mtk.manpages at gmail dot com [this message]
2012-04-22  2:02 ` mtk.manpages at gmail dot com
2012-04-22  2:12 ` mtk.manpages at gmail dot com
2012-04-22 10:40 ` [Bug stdio/12685] " jsm28 at gcc dot gnu.org
2013-05-09 15:14 ` ondra at iuuk dot mff.cuni.cz
2013-05-09 16:08 ` bugdal at aerifal dot cx
2014-06-27 13:30 ` fweimer at redhat dot com

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-12685-131-zEinqcuvFZ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).