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 17:56:32 +0200
From: Florian Weimer <>
To: Mickaël Salaün <>
Cc:,  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 <>,  Mickaël Salaün
 <>,  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()

Let's assume I want to add support for this to the glibc dynamic loader,
while still being able to run on older kernels.

Is it safe to try the open call first, with O_MAYEXEC, and if that fails
with EINVAL, try again without O_MAYEXEC?

Or do I risk disabling this security feature if I do that?

Do we need a different way for recognizing kernel support.  (Note that
we cannot probe paths in /proc for various reasons.)


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.