Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 06 Sep 2019 20:44:03 +0200
From: Florian Weimer <>
To: Jeff Layton <>
Cc: Mickaël Salaün <>,
  Mickaël Salaün
 <>,,  Aleksa Sarai
 <>,  Alexei Starovoitov <>,  Al Viro
 <>,  Andy Lutomirski <>,  Christian
 Heimes <>,  Daniel Borkmann <>,
  Eric Chiang <>,  James Morris <>,
  Jan Kara <>,  Jann Horn <>,  Jonathan Corbet
 <>,  Kees Cook <>,  Matthew Garrett
 <>,  Matthew Wilcox <>,  Michael
 Kerrisk <>,  Mimi Zohar <>,
  Philippe Trébuchet <>,
  Scott Shell
 <>,  Sean Christopherson
 <>,  Shuah Khan <>,  Song
 Liu <>,  Steve Dower <>,  Steve
 Grubb <>,  Thibaut Sautereau
 <>,  Vincent Strubel
 <>,  Yves-Alexis Perez
Subject: Re: [PATCH v2 1/5] fs: Add support for an O_MAYEXEC flag on sys_open()

* Jeff Layton:

> Even better would be to declare the new flag in some openat2-only flag
> space, so there's no confusion about it being supported by legacy open
> calls.

Isn't that desirable anyway because otherwise fcntl with F_GETFL will
give really confusing results?

> If glibc wants to implement an open -> openat2 wrapper in userland
> later, it can set that flag in the wrapper implicitly to emulate the old
> behavior.

I see us rather doing the opposite, i.e. implement openat2 with
non-exotic flags using openat.  But we've bitten by this in the past, so
maybe that's not such a great idea.  It's tempting to make the same
mistake again for every new system call.


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.