Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 26 Sep 2014 09:23:43 +0200
Subject: Re: fdopen/fflush problem

On Fri, Sep 26, 2014 at 03:05:48AM -0400, Rich Felker wrote:
>     unspecified if the flag argument contains more than the following
>     flags:"
> The list that follows includes just O_APPEND, O_CLOEXEC, and O_*SYNC,
> so including O_WRONLY has unspecified behavior. However, since this is
> just unspecified, not undefined, it seems bad for something "horribly
> wrong" to happen, like a file with no access like we're getting now.
> Indeed, POSIX will define an optional error:
>     "The mkostemp( ) function may fail if:
>     [EINVAL] The value of the flag argument is invalid."
> So I think we should either make this error be detected, or silently
> mask off the bad access mode. My leaning would be towards reporting it
> as an error. Opinions?

+1 (reporting an error)


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.