This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/12685] fopen doesn't honor last byte of valid modes


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]