lkml.org 
[lkml]   [2017]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRFC: reject unknown open flags
    Date
    Linux has traditionally accepted random garbage in the flags argument to
    the open syscall (including the later added openat). This really harms
    when adding new flags, because applications can't just probe for the
    flag to actually work. While rejecting unknown flags is an ABI change
    strictly speaking I can't see what would actually get broken by it
    in practice, so by the Linux rules it might not be an issue.

    Below is the trivial series to reject unknown flags. If this is not
    acceptable there migh be some other ways, although they seem ugly:

    (a) add a new openat2 system call that enforces this behavior, and
    hope all majors libcs switch to using that by default to implement
    open(3).
    (b) add a new personality flag to enforce this behavior (or maybe
    opt in by default and allow admins to opt out of it)

    \
     
     \ /
      Last update: 2017-03-30 18:34    [W:3.036 / U:0.048 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site