Bug 12503 - fmemopen disobeys POSIX regarding 'b' flag
Summary: fmemopen disobeys POSIX regarding 'b' flag
Status: RESOLVED WONTFIX
Alias: None
Product: glibc
Classification: Unclassified
Component: libc (show other bugs)
Version: 2.12
: P2 normal
Target Milestone: ---
Assignee: Ulrich Drepper
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-22 15:51 UTC by Eric Blake
Modified: 2014-06-27 13:50 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Blake 2011-02-22 15:51:55 UTC 
POSIX requires that the 'b' flag of fmemopen have no effect.  But the resolution to bug 6544 commandeered the 'b' flag to make fmemopen disobey POSIX.  Please use a different flag than 'b', or get POSIX changed to leave the behavior of fmemopen and 'b' unspecified.
Comment 1 Ulrich Drepper 2011-03-05 09:33:11 UTC 
No, this is existing practice on which the standard was based.
Comment 2 Eric Blake 2011-03-17 18:13:30 UTC 
(In reply to comment #1)
> No, this is existing practice on which the standard was based.

Actually, the standard was based on the fmemopen() behavior that existed in 2006, when glibc ignored 'b'.  However, I've opened an Austin Group bug to see who needs to change (glibc, POSIX, or both).
http://austingroupbugs.net/view.php?id=396

Based on the outcome of that POSIX bug, glibc may yet need to change its implementation to comply, so I'm reopening this glibc bug.
Comment 3 Ulrich Drepper 2011-03-18 10:08:22 UTC 
Stop reopening the bug.  There will be no change.  The existing behavior is common practice and the functionality is needed.