All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH 1/2] vfs: implement fchmodat2() syscall
@ 2017-02-28 17:03 Greg Kurz
  2017-02-28 17:03 ` [PATCH 2/2] x86: wire up " Greg Kurz
                   ` (2 more replies)
  0 siblings, 3 replies; 15+ messages in thread
From: Greg Kurz @ 2017-02-28 17:03 UTC (permalink / raw)
  To: viro; +Cc: linux-fsdevel, Eric Blake, linux-kernel

According to the POSIX.1-2008 manual page [1], the fchmodat() function has
a flag argument which may be passed the following value:

AT_SYMLINK_NOFOLLOW
    If path names a symbolic link, then the mode of the symbolic link is
    changed.

and the following error may be returned:

[EOPNOTSUPP]
    The AT_SYMLINK_NOFOLLOW bit is set in the flag argument, path names a
    symbolic link, and the system does not support changing the mode of a
    symbolic link.

The linux kernel doesn't support changing the mode of a symbolic link, but
the current implementation doesn't even have a flag argument. It is then
up to userspace to deal with that. Unfortunately, it is impossible to
implement the POSIX behavior in a race-free manner.

This patch introduces a new fchmodat2() syscall with a flag argument to
address the issue.

[1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/chmod.html

Signed-off-by: Greg Kurz <groug@kaod.org>
---
 fs/open.c                         |   23 +++++++++++++++++++----
 include/linux/syscalls.h          |    2 ++
 include/uapi/asm-generic/unistd.h |    4 +++-
 scripts/checksyscalls.sh          |    3 ++-
 4 files changed, 26 insertions(+), 6 deletions(-)

diff --git a/fs/open.c b/fs/open.c
index 9921f70bc5ca..66a8c19f72ca 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -558,24 +558,39 @@ SYSCALL_DEFINE2(fchmod, unsigned int, fd, umode_t, mode)
 	return err;
 }
 
-SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename, umode_t, mode)
+SYSCALL_DEFINE4(fchmodat2, int, dfd, const char __user *, filename, umode_t,
+		mode, int, flag)
 {
 	struct path path;
-	int error;
-	unsigned int lookup_flags = LOOKUP_FOLLOW;
+	int error = -EINVAL;
+	unsigned int lookup_flags;
+
+	if ((flag & ~AT_SYMLINK_NOFOLLOW) != 0)
+		goto out;
+
+	lookup_flags = (flag & AT_SYMLINK_NOFOLLOW) ? 0 : LOOKUP_FOLLOW;
 retry:
 	error = user_path_at(dfd, filename, lookup_flags, &path);
 	if (!error) {
-		error = chmod_common(&path, mode);
+		error = -EOPNOTSUPP;
+		if (!d_is_symlink(path.dentry))
+			error = chmod_common(&path, mode);
 		path_put(&path);
 		if (retry_estale(error, lookup_flags)) {
 			lookup_flags |= LOOKUP_REVAL;
 			goto retry;
 		}
 	}
+out:
 	return error;
 }
 
+SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename, umode_t,
+		mode)
+{
+	return sys_fchmodat2(dfd, filename, mode, 0);
+}
+
 SYSCALL_DEFINE2(chmod, const char __user *, filename, umode_t, mode)
 {
 	return sys_fchmodat(AT_FDCWD, filename, mode);
diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
index 91a740f6b884..982089d55b31 100644
--- a/include/linux/syscalls.h
+++ b/include/linux/syscalls.h
@@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char __user *filename,
 asmlinkage long sys_faccessat(int dfd, const char __user *filename, int mode);
 asmlinkage long sys_fchmodat(int dfd, const char __user * filename,
 			     umode_t mode);
+asmlinkage long sys_fchmodat2(int dfd, const char __user *filename,
+			      umode_t mode, int flag);
 asmlinkage long sys_fchownat(int dfd, const char __user *filename, uid_t user,
 			     gid_t group, int flag);
 asmlinkage long sys_openat(int dfd, const char __user *filename, int flags,
diff --git a/include/uapi/asm-generic/unistd.h b/include/uapi/asm-generic/unistd.h
index 9b1462e38b82..e8b0a00908b1 100644
--- a/include/uapi/asm-generic/unistd.h
+++ b/include/uapi/asm-generic/unistd.h
@@ -730,9 +730,11 @@ __SYSCALL(__NR_pkey_mprotect, sys_pkey_mprotect)
 __SYSCALL(__NR_pkey_alloc,    sys_pkey_alloc)
 #define __NR_pkey_free 290
 __SYSCALL(__NR_pkey_free,     sys_pkey_free)
+#define __NR_fchmodat2 291
+__SYSCALL(__NR_fchmodat2,     sys_fchmodat2)
 
 #undef __NR_syscalls
-#define __NR_syscalls 291
+#define __NR_syscalls 292
 
 /*
  * All syscalls below here should go away really,
diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh
index 2c9082ba6137..2e7471a1d308 100755
--- a/scripts/checksyscalls.sh
+++ b/scripts/checksyscalls.sh
@@ -19,7 +19,7 @@ cat << EOF
 #define __IGNORE_link		/* linkat */
 #define __IGNORE_unlink		/* unlinkat */
 #define __IGNORE_mknod		/* mknodat */
-#define __IGNORE_chmod		/* fchmodat */
+#define __IGNORE_chmod		/* fchmodat2 */
 #define __IGNORE_chown		/* fchownat */
 #define __IGNORE_mkdir		/* mkdirat */
 #define __IGNORE_rmdir		/* unlinkat */
@@ -39,6 +39,7 @@ cat << EOF
 
 /* Missing flags argument */
 #define __IGNORE_renameat	/* renameat2 */
+#define __IGNORE_fchmodat	/* fchmodat2 */
 
 /* CLOEXEC flag */
 #define __IGNORE_pipe		/* pipe2 */

^ permalink raw reply related	[flat|nested] 15+ messages in thread

* [PATCH 2/2] x86: wire up fchmodat2() syscall
  2017-02-28 17:03 [PATCH 1/2] vfs: implement fchmodat2() syscall Greg Kurz
@ 2017-02-28 17:03 ` Greg Kurz
  2017-03-01  9:00   ` kbuild test robot
  2017-02-28 18:23 ` [PATCH 1/2] vfs: implement " Eric Blake
  2017-03-01  9:01 ` Michael Kerrisk
  2 siblings, 1 reply; 15+ messages in thread
From: Greg Kurz @ 2017-02-28 17:03 UTC (permalink / raw)
  To: viro; +Cc: linux-fsdevel, Eric Blake, linux-kernel

Signed-off-by: Greg Kurz <groug@kaod.org>
---
 arch/x86/entry/syscalls/syscall_32.tbl |    1 +
 arch/x86/entry/syscalls/syscall_64.tbl |    1 +
 2 files changed, 2 insertions(+)

diff --git a/arch/x86/entry/syscalls/syscall_32.tbl b/arch/x86/entry/syscalls/syscall_32.tbl
index 2b3618542544..413529600b8a 100644
--- a/arch/x86/entry/syscalls/syscall_32.tbl
+++ b/arch/x86/entry/syscalls/syscall_32.tbl
@@ -389,3 +389,4 @@
 380	i386	pkey_mprotect		sys_pkey_mprotect
 381	i386	pkey_alloc		sys_pkey_alloc
 382	i386	pkey_free		sys_pkey_free
+383	i386	fchmodat2		sys_fchmodat2
diff --git a/arch/x86/entry/syscalls/syscall_64.tbl b/arch/x86/entry/syscalls/syscall_64.tbl
index e93ef0b38db8..23a7e5d02ae4 100644
--- a/arch/x86/entry/syscalls/syscall_64.tbl
+++ b/arch/x86/entry/syscalls/syscall_64.tbl
@@ -338,6 +338,7 @@
 329	common	pkey_mprotect		sys_pkey_mprotect
 330	common	pkey_alloc		sys_pkey_alloc
 331	common	pkey_free		sys_pkey_free
+332	common	fchmodat2		sys_fchmodat2
 
 #
 # x32-specific system call numbers start at 512 to avoid cache impact

^ permalink raw reply related	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-02-28 17:03 [PATCH 1/2] vfs: implement fchmodat2() syscall Greg Kurz
  2017-02-28 17:03 ` [PATCH 2/2] x86: wire up " Greg Kurz
@ 2017-02-28 18:23 ` Eric Blake
  2017-02-28 18:41   ` Greg Kurz
  2017-04-11 17:52   ` Colin Walters
  2017-03-01  9:01 ` Michael Kerrisk
  2 siblings, 2 replies; 15+ messages in thread
From: Eric Blake @ 2017-02-28 18:23 UTC (permalink / raw)
  To: Greg Kurz, viro; +Cc: linux-fsdevel, linux-kernel


[-- Attachment #1.1: Type: text/plain, Size: 1979 bytes --]

On 02/28/2017 11:03 AM, Greg Kurz wrote:
> According to the POSIX.1-2008 manual page [1], the fchmodat() function has
> a flag argument which may be passed the following value:
> 
> AT_SYMLINK_NOFOLLOW
>     If path names a symbolic link, then the mode of the symbolic link is
>     changed.
> 
> and the following error may be returned:
> 
> [EOPNOTSUPP]
>     The AT_SYMLINK_NOFOLLOW bit is set in the flag argument, path names a
>     symbolic link, and the system does not support changing the mode of a
>     symbolic link.
> 
> The linux kernel doesn't support changing the mode of a symbolic link, but
> the current implementation doesn't even have a flag argument. It is then
> up to userspace to deal with that. Unfortunately, it is impossible to
> implement the POSIX behavior in a race-free manner.
> 
> This patch introduces a new fchmodat2() syscall with a flag argument to
> address the issue.
> 
> [1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/chmod.html
> 
> Signed-off-by: Greg Kurz <groug@kaod.org>
> ---

Might also be worth mentioning that this patch is required in order to
solve CVE-2016-9602, per discussion at
https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg06089.html

> +++ b/include/linux/syscalls.h
> @@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char __user *filename,
>  asmlinkage long sys_faccessat(int dfd, const char __user *filename, int mode);
>  asmlinkage long sys_fchmodat(int dfd, const char __user * filename,
>  			     umode_t mode);
> +asmlinkage long sys_fchmodat2(int dfd, const char __user *filename,
> +			      umode_t mode, int flag);
>  asmlinkage long sys_fchownat(int dfd, const char __user *filename, uid_t user,
>  			     gid_t group, int flag);

Is the indentation off here?

Reviewed-by: Eric Blake <eblake@redhat.com>


-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-02-28 18:23 ` [PATCH 1/2] vfs: implement " Eric Blake
@ 2017-02-28 18:41   ` Greg Kurz
  2017-02-28 18:59     ` Eric Blake
  2017-04-11 17:52   ` Colin Walters
  1 sibling, 1 reply; 15+ messages in thread
From: Greg Kurz @ 2017-02-28 18:41 UTC (permalink / raw)
  To: Eric Blake; +Cc: viro, linux-fsdevel, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 2260 bytes --]

On Tue, 28 Feb 2017 12:23:01 -0600
Eric Blake <eblake@redhat.com> wrote:

> On 02/28/2017 11:03 AM, Greg Kurz wrote:
> > According to the POSIX.1-2008 manual page [1], the fchmodat() function has
> > a flag argument which may be passed the following value:
> > 
> > AT_SYMLINK_NOFOLLOW
> >     If path names a symbolic link, then the mode of the symbolic link is
> >     changed.
> > 
> > and the following error may be returned:
> > 
> > [EOPNOTSUPP]
> >     The AT_SYMLINK_NOFOLLOW bit is set in the flag argument, path names a
> >     symbolic link, and the system does not support changing the mode of a
> >     symbolic link.
> > 
> > The linux kernel doesn't support changing the mode of a symbolic link, but
> > the current implementation doesn't even have a flag argument. It is then
> > up to userspace to deal with that. Unfortunately, it is impossible to
> > implement the POSIX behavior in a race-free manner.
> > 
> > This patch introduces a new fchmodat2() syscall with a flag argument to
> > address the issue.
> > 
> > [1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/chmod.html
> > 
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---  
> 
> Might also be worth mentioning that this patch is required in order to
> solve CVE-2016-9602, per discussion at
> https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg06089.html
> 

True. I'll add a reference to it if I have to send a v2.

> > +++ b/include/linux/syscalls.h
> > @@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char __user *filename,
> >  asmlinkage long sys_faccessat(int dfd, const char __user *filename, int mode);
> >  asmlinkage long sys_fchmodat(int dfd, const char __user * filename,
> >  			     umode_t mode);
> > +asmlinkage long sys_fchmodat2(int dfd, const char __user *filename,
> > +			      umode_t mode, int flag);
> >  asmlinkage long sys_fchownat(int dfd, const char __user *filename, uid_t user,
> >  			     gid_t group, int flag);  
> 
> Is the indentation off here?
> 

This is linux style indent with tabs+spaces. FWIW it is displayed correctly
in vi and emacs (I've simply copied the sys_fchmodat() declaration).

> Reviewed-by: Eric Blake <eblake@redhat.com>
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-02-28 18:41   ` Greg Kurz
@ 2017-02-28 18:59     ` Eric Blake
  0 siblings, 0 replies; 15+ messages in thread
From: Eric Blake @ 2017-02-28 18:59 UTC (permalink / raw)
  To: Greg Kurz; +Cc: viro, linux-fsdevel, linux-kernel


[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]

On 02/28/2017 12:41 PM, Greg Kurz wrote:

>>> +++ b/include/linux/syscalls.h
>>> @@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char __user *filename,
>>>  asmlinkage long sys_faccessat(int dfd, const char __user *filename, int mode);
>>>  asmlinkage long sys_fchmodat(int dfd, const char __user * filename,
>>>  			     umode_t mode);
>>> +asmlinkage long sys_fchmodat2(int dfd, const char __user *filename,
>>> +			      umode_t mode, int flag);
>>>  asmlinkage long sys_fchownat(int dfd, const char __user *filename, uid_t user,
>>>  			     gid_t group, int flag);  
>>
>> Is the indentation off here?
>>
> 
> This is linux style indent with tabs+spaces. FWIW it is displayed correctly
> in vi and emacs (I've simply copied the sys_fchmodat() declaration).

Sorry for the noise; I see that it is correct now, since fchmodat2 is
one bye longer than fchmodat or fchownat.  Sometimes, I wish I could
convince my mailer to display leading tabs as exactly 8 spaces rather
than to the next 8-space tab stop, so that prefixed characters that
aren't tab-stop aligned don't mess with the actual visual output.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 2/2] x86: wire up fchmodat2() syscall
  2017-02-28 17:03 ` [PATCH 2/2] x86: wire up " Greg Kurz
@ 2017-03-01  9:00   ` kbuild test robot
  0 siblings, 0 replies; 15+ messages in thread
From: kbuild test robot @ 2017-03-01  9:00 UTC (permalink / raw)
  To: Greg Kurz; +Cc: kbuild-all, viro, linux-fsdevel, Eric Blake, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

Hi Greg,

[auto build test WARNING on linus/master]
[also build test WARNING on v4.10]
[cannot apply to next-20170228]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Greg-Kurz/vfs-implement-fchmodat2-syscall/20170301-150213
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All warnings (new ones prefixed by >>):

>> <stdin>:1326:2: warning: #warning syscall fchmodat2 not implemented [-Wcpp]

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 49190 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-02-28 17:03 [PATCH 1/2] vfs: implement fchmodat2() syscall Greg Kurz
  2017-02-28 17:03 ` [PATCH 2/2] x86: wire up " Greg Kurz
  2017-02-28 18:23 ` [PATCH 1/2] vfs: implement " Eric Blake
@ 2017-03-01  9:01 ` Michael Kerrisk
  2017-04-11 11:39   ` Greg Kurz
  2 siblings, 1 reply; 15+ messages in thread
From: Michael Kerrisk @ 2017-03-01  9:01 UTC (permalink / raw)
  To: Greg Kurz; +Cc: Al Viro, Linux-Fsdevel, Eric Blake, Linux Kernel, Linux API

[CC += linux-api@vger.kernel.org]

Hello Greg,

Since this is a kernel-user-space API change, please CC linux-api@.
The kernel source file Documentation/SubmitChecklist notes that all
Linux kernel patches that change userspace interfaces should be CCed
to linux-api@vger.kernel.org, so that the various parties who are
interested in API changes are informed. For further information, see
https://www.kernel.org/doc/man-pages/linux-api-ml.html

Thanks,

Michael


On Tue, Feb 28, 2017 at 6:03 PM, Greg Kurz <groug@kaod.org> wrote:
> According to the POSIX.1-2008 manual page [1], the fchmodat() function has
> a flag argument which may be passed the following value:
>
> AT_SYMLINK_NOFOLLOW
>     If path names a symbolic link, then the mode of the symbolic link is
>     changed.
>
> and the following error may be returned:
>
> [EOPNOTSUPP]
>     The AT_SYMLINK_NOFOLLOW bit is set in the flag argument, path names a
>     symbolic link, and the system does not support changing the mode of a
>     symbolic link.
>
> The linux kernel doesn't support changing the mode of a symbolic link, but
> the current implementation doesn't even have a flag argument. It is then
> up to userspace to deal with that. Unfortunately, it is impossible to
> implement the POSIX behavior in a race-free manner.
>
> This patch introduces a new fchmodat2() syscall with a flag argument to
> address the issue.
>
> [1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/chmod.html
>
> Signed-off-by: Greg Kurz <groug@kaod.org>
> ---
>  fs/open.c                         |   23 +++++++++++++++++++----
>  include/linux/syscalls.h          |    2 ++
>  include/uapi/asm-generic/unistd.h |    4 +++-
>  scripts/checksyscalls.sh          |    3 ++-
>  4 files changed, 26 insertions(+), 6 deletions(-)
>
> diff --git a/fs/open.c b/fs/open.c
> index 9921f70bc5ca..66a8c19f72ca 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -558,24 +558,39 @@ SYSCALL_DEFINE2(fchmod, unsigned int, fd, umode_t, mode)
>         return err;
>  }
>
> -SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename, umode_t, mode)
> +SYSCALL_DEFINE4(fchmodat2, int, dfd, const char __user *, filename, umode_t,
> +               mode, int, flag)
>  {
>         struct path path;
> -       int error;
> -       unsigned int lookup_flags = LOOKUP_FOLLOW;
> +       int error = -EINVAL;
> +       unsigned int lookup_flags;
> +
> +       if ((flag & ~AT_SYMLINK_NOFOLLOW) != 0)
> +               goto out;
> +
> +       lookup_flags = (flag & AT_SYMLINK_NOFOLLOW) ? 0 : LOOKUP_FOLLOW;
>  retry:
>         error = user_path_at(dfd, filename, lookup_flags, &path);
>         if (!error) {
> -               error = chmod_common(&path, mode);
> +               error = -EOPNOTSUPP;
> +               if (!d_is_symlink(path.dentry))
> +                       error = chmod_common(&path, mode);
>                 path_put(&path);
>                 if (retry_estale(error, lookup_flags)) {
>                         lookup_flags |= LOOKUP_REVAL;
>                         goto retry;
>                 }
>         }
> +out:
>         return error;
>  }
>
> +SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename, umode_t,
> +               mode)
> +{
> +       return sys_fchmodat2(dfd, filename, mode, 0);
> +}
> +
>  SYSCALL_DEFINE2(chmod, const char __user *, filename, umode_t, mode)
>  {
>         return sys_fchmodat(AT_FDCWD, filename, mode);
> diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
> index 91a740f6b884..982089d55b31 100644
> --- a/include/linux/syscalls.h
> +++ b/include/linux/syscalls.h
> @@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char __user *filename,
>  asmlinkage long sys_faccessat(int dfd, const char __user *filename, int mode);
>  asmlinkage long sys_fchmodat(int dfd, const char __user * filename,
>                              umode_t mode);
> +asmlinkage long sys_fchmodat2(int dfd, const char __user *filename,
> +                             umode_t mode, int flag);
>  asmlinkage long sys_fchownat(int dfd, const char __user *filename, uid_t user,
>                              gid_t group, int flag);
>  asmlinkage long sys_openat(int dfd, const char __user *filename, int flags,
> diff --git a/include/uapi/asm-generic/unistd.h b/include/uapi/asm-generic/unistd.h
> index 9b1462e38b82..e8b0a00908b1 100644
> --- a/include/uapi/asm-generic/unistd.h
> +++ b/include/uapi/asm-generic/unistd.h
> @@ -730,9 +730,11 @@ __SYSCALL(__NR_pkey_mprotect, sys_pkey_mprotect)
>  __SYSCALL(__NR_pkey_alloc,    sys_pkey_alloc)
>  #define __NR_pkey_free 290
>  __SYSCALL(__NR_pkey_free,     sys_pkey_free)
> +#define __NR_fchmodat2 291
> +__SYSCALL(__NR_fchmodat2,     sys_fchmodat2)
>
>  #undef __NR_syscalls
> -#define __NR_syscalls 291
> +#define __NR_syscalls 292
>
>  /*
>   * All syscalls below here should go away really,
> diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh
> index 2c9082ba6137..2e7471a1d308 100755
> --- a/scripts/checksyscalls.sh
> +++ b/scripts/checksyscalls.sh
> @@ -19,7 +19,7 @@ cat << EOF
>  #define __IGNORE_link          /* linkat */
>  #define __IGNORE_unlink                /* unlinkat */
>  #define __IGNORE_mknod         /* mknodat */
> -#define __IGNORE_chmod         /* fchmodat */
> +#define __IGNORE_chmod         /* fchmodat2 */
>  #define __IGNORE_chown         /* fchownat */
>  #define __IGNORE_mkdir         /* mkdirat */
>  #define __IGNORE_rmdir         /* unlinkat */
> @@ -39,6 +39,7 @@ cat << EOF
>
>  /* Missing flags argument */
>  #define __IGNORE_renameat      /* renameat2 */
> +#define __IGNORE_fchmodat      /* fchmodat2 */
>
>  /* CLOEXEC flag */
>  #define __IGNORE_pipe          /* pipe2 */
>



-- 
Michael Kerrisk Linux man-pages maintainer;
http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface", http://blog.man7.org/

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-03-01  9:01 ` Michael Kerrisk
@ 2017-04-11 11:39   ` Greg Kurz
  2017-04-11 12:04     ` Greg Kurz
  0 siblings, 1 reply; 15+ messages in thread
From: Greg Kurz @ 2017-04-11 11:39 UTC (permalink / raw)
  To: Michael Kerrisk
  Cc: Al Viro, Linux-Fsdevel, Eric Blake, Linux Kernel, Linux API

[-- Attachment #1: Type: text/plain, Size: 6411 bytes --]

On Wed, 1 Mar 2017 10:01:53 +0100
Michael Kerrisk <mtk.manpages@gmail.com> wrote:

> [CC += linux-api@vger.kernel.org]
> 
> Hello Greg,
> 
> Since this is a kernel-user-space API change, please CC linux-api@.
> The kernel source file Documentation/SubmitChecklist notes that all
> Linux kernel patches that change userspace interfaces should be CCed
> to linux-api@vger.kernel.org, so that the various parties who are
> interested in API changes are informed. For further information, see
> https://www.kernel.org/doc/man-pages/linux-api-ml.html
> 
> Thanks,
> 
> Michael
> 

My bad :-\ 

Anyway, since I had no feedback so far, I'll send a v2 and this time I'll
rembember to Cc linux-api@vger.kernel.org.

Thanks,

--
Greg

> 
> On Tue, Feb 28, 2017 at 6:03 PM, Greg Kurz <groug@kaod.org> wrote:
> > According to the POSIX.1-2008 manual page [1], the fchmodat() function has
> > a flag argument which may be passed the following value:
> >
> > AT_SYMLINK_NOFOLLOW
> >     If path names a symbolic link, then the mode of the symbolic link is
> >     changed.
> >
> > and the following error may be returned:
> >
> > [EOPNOTSUPP]
> >     The AT_SYMLINK_NOFOLLOW bit is set in the flag argument, path names a
> >     symbolic link, and the system does not support changing the mode of a
> >     symbolic link.
> >
> > The linux kernel doesn't support changing the mode of a symbolic link, but
> > the current implementation doesn't even have a flag argument. It is then
> > up to userspace to deal with that. Unfortunately, it is impossible to
> > implement the POSIX behavior in a race-free manner.
> >
> > This patch introduces a new fchmodat2() syscall with a flag argument to
> > address the issue.
> >
> > [1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/chmod.html
> >
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> >  fs/open.c                         |   23 +++++++++++++++++++----
> >  include/linux/syscalls.h          |    2 ++
> >  include/uapi/asm-generic/unistd.h |    4 +++-
> >  scripts/checksyscalls.sh          |    3 ++-
> >  4 files changed, 26 insertions(+), 6 deletions(-)
> >
> > diff --git a/fs/open.c b/fs/open.c
> > index 9921f70bc5ca..66a8c19f72ca 100644
> > --- a/fs/open.c
> > +++ b/fs/open.c
> > @@ -558,24 +558,39 @@ SYSCALL_DEFINE2(fchmod, unsigned int, fd, umode_t, mode)
> >         return err;
> >  }
> >
> > -SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename, umode_t, mode)
> > +SYSCALL_DEFINE4(fchmodat2, int, dfd, const char __user *, filename, umode_t,
> > +               mode, int, flag)
> >  {
> >         struct path path;
> > -       int error;
> > -       unsigned int lookup_flags = LOOKUP_FOLLOW;
> > +       int error = -EINVAL;
> > +       unsigned int lookup_flags;
> > +
> > +       if ((flag & ~AT_SYMLINK_NOFOLLOW) != 0)
> > +               goto out;
> > +
> > +       lookup_flags = (flag & AT_SYMLINK_NOFOLLOW) ? 0 : LOOKUP_FOLLOW;
> >  retry:
> >         error = user_path_at(dfd, filename, lookup_flags, &path);
> >         if (!error) {
> > -               error = chmod_common(&path, mode);
> > +               error = -EOPNOTSUPP;
> > +               if (!d_is_symlink(path.dentry))
> > +                       error = chmod_common(&path, mode);
> >                 path_put(&path);
> >                 if (retry_estale(error, lookup_flags)) {
> >                         lookup_flags |= LOOKUP_REVAL;
> >                         goto retry;
> >                 }
> >         }
> > +out:
> >         return error;
> >  }
> >
> > +SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename, umode_t,
> > +               mode)
> > +{
> > +       return sys_fchmodat2(dfd, filename, mode, 0);
> > +}
> > +
> >  SYSCALL_DEFINE2(chmod, const char __user *, filename, umode_t, mode)
> >  {
> >         return sys_fchmodat(AT_FDCWD, filename, mode);
> > diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
> > index 91a740f6b884..982089d55b31 100644
> > --- a/include/linux/syscalls.h
> > +++ b/include/linux/syscalls.h
> > @@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char __user *filename,
> >  asmlinkage long sys_faccessat(int dfd, const char __user *filename, int mode);
> >  asmlinkage long sys_fchmodat(int dfd, const char __user * filename,
> >                              umode_t mode);
> > +asmlinkage long sys_fchmodat2(int dfd, const char __user *filename,
> > +                             umode_t mode, int flag);
> >  asmlinkage long sys_fchownat(int dfd, const char __user *filename, uid_t user,
> >                              gid_t group, int flag);
> >  asmlinkage long sys_openat(int dfd, const char __user *filename, int flags,
> > diff --git a/include/uapi/asm-generic/unistd.h b/include/uapi/asm-generic/unistd.h
> > index 9b1462e38b82..e8b0a00908b1 100644
> > --- a/include/uapi/asm-generic/unistd.h
> > +++ b/include/uapi/asm-generic/unistd.h
> > @@ -730,9 +730,11 @@ __SYSCALL(__NR_pkey_mprotect, sys_pkey_mprotect)
> >  __SYSCALL(__NR_pkey_alloc,    sys_pkey_alloc)
> >  #define __NR_pkey_free 290
> >  __SYSCALL(__NR_pkey_free,     sys_pkey_free)
> > +#define __NR_fchmodat2 291
> > +__SYSCALL(__NR_fchmodat2,     sys_fchmodat2)
> >
> >  #undef __NR_syscalls
> > -#define __NR_syscalls 291
> > +#define __NR_syscalls 292
> >
> >  /*
> >   * All syscalls below here should go away really,
> > diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh
> > index 2c9082ba6137..2e7471a1d308 100755
> > --- a/scripts/checksyscalls.sh
> > +++ b/scripts/checksyscalls.sh
> > @@ -19,7 +19,7 @@ cat << EOF
> >  #define __IGNORE_link          /* linkat */
> >  #define __IGNORE_unlink                /* unlinkat */
> >  #define __IGNORE_mknod         /* mknodat */
> > -#define __IGNORE_chmod         /* fchmodat */
> > +#define __IGNORE_chmod         /* fchmodat2 */
> >  #define __IGNORE_chown         /* fchownat */
> >  #define __IGNORE_mkdir         /* mkdirat */
> >  #define __IGNORE_rmdir         /* unlinkat */
> > @@ -39,6 +39,7 @@ cat << EOF
> >
> >  /* Missing flags argument */
> >  #define __IGNORE_renameat      /* renameat2 */
> > +#define __IGNORE_fchmodat      /* fchmodat2 */
> >
> >  /* CLOEXEC flag */
> >  #define __IGNORE_pipe          /* pipe2 */
> >  
> 
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-04-11 11:39   ` Greg Kurz
@ 2017-04-11 12:04     ` Greg Kurz
  0 siblings, 0 replies; 15+ messages in thread
From: Greg Kurz @ 2017-04-11 12:04 UTC (permalink / raw)
  To: Michael Kerrisk
  Cc: Al Viro, Linux-Fsdevel, Eric Blake, Linux Kernel, Linux API

[-- Attachment #1: Type: text/plain, Size: 7082 bytes --]

On Tue, 11 Apr 2017 13:39:37 +0200
Greg Kurz <groug@kaod.org> wrote:

> On Wed, 1 Mar 2017 10:01:53 +0100
> Michael Kerrisk <mtk.manpages@gmail.com> wrote:
> 
> > [CC += linux-api@vger.kernel.org]
> > 
> > Hello Greg,
> > 
> > Since this is a kernel-user-space API change, please CC linux-api@.
> > The kernel source file Documentation/SubmitChecklist notes that all
> > Linux kernel patches that change userspace interfaces should be CCed
> > to linux-api@vger.kernel.org, so that the various parties who are
> > interested in API changes are informed. For further information, see
> > https://www.kernel.org/doc/man-pages/linux-api-ml.html
> > 
> > Thanks,
> > 
> > Michael
> >   
> 
> My bad :-\ 
> 
> Anyway, since I had no feedback so far, I'll send a v2 and this time I'll
> rembember to Cc linux-api@vger.kernel.org.
> 
> Thanks,
> 

BTW, commit "186128f75392 docs-rst: add documents to development-process" moved
Documentation/SubmitChecklist to Documentation/process/submit-checklist.rst, but
the www.kernel.org page hasn't been updated to reflect that...

Cheers.

--
Greg

> --
> Greg
> 
> > 
> > On Tue, Feb 28, 2017 at 6:03 PM, Greg Kurz <groug@kaod.org> wrote:  
> > > According to the POSIX.1-2008 manual page [1], the fchmodat() function has
> > > a flag argument which may be passed the following value:
> > >
> > > AT_SYMLINK_NOFOLLOW
> > >     If path names a symbolic link, then the mode of the symbolic link is
> > >     changed.
> > >
> > > and the following error may be returned:
> > >
> > > [EOPNOTSUPP]
> > >     The AT_SYMLINK_NOFOLLOW bit is set in the flag argument, path names a
> > >     symbolic link, and the system does not support changing the mode of a
> > >     symbolic link.
> > >
> > > The linux kernel doesn't support changing the mode of a symbolic link, but
> > > the current implementation doesn't even have a flag argument. It is then
> > > up to userspace to deal with that. Unfortunately, it is impossible to
> > > implement the POSIX behavior in a race-free manner.
> > >
> > > This patch introduces a new fchmodat2() syscall with a flag argument to
> > > address the issue.
> > >
> > > [1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/chmod.html
> > >
> > > Signed-off-by: Greg Kurz <groug@kaod.org>
> > > ---
> > >  fs/open.c                         |   23 +++++++++++++++++++----
> > >  include/linux/syscalls.h          |    2 ++
> > >  include/uapi/asm-generic/unistd.h |    4 +++-
> > >  scripts/checksyscalls.sh          |    3 ++-
> > >  4 files changed, 26 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/fs/open.c b/fs/open.c
> > > index 9921f70bc5ca..66a8c19f72ca 100644
> > > --- a/fs/open.c
> > > +++ b/fs/open.c
> > > @@ -558,24 +558,39 @@ SYSCALL_DEFINE2(fchmod, unsigned int, fd, umode_t, mode)
> > >         return err;
> > >  }
> > >
> > > -SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename, umode_t, mode)
> > > +SYSCALL_DEFINE4(fchmodat2, int, dfd, const char __user *, filename, umode_t,
> > > +               mode, int, flag)
> > >  {
> > >         struct path path;
> > > -       int error;
> > > -       unsigned int lookup_flags = LOOKUP_FOLLOW;
> > > +       int error = -EINVAL;
> > > +       unsigned int lookup_flags;
> > > +
> > > +       if ((flag & ~AT_SYMLINK_NOFOLLOW) != 0)
> > > +               goto out;
> > > +
> > > +       lookup_flags = (flag & AT_SYMLINK_NOFOLLOW) ? 0 : LOOKUP_FOLLOW;
> > >  retry:
> > >         error = user_path_at(dfd, filename, lookup_flags, &path);
> > >         if (!error) {
> > > -               error = chmod_common(&path, mode);
> > > +               error = -EOPNOTSUPP;
> > > +               if (!d_is_symlink(path.dentry))
> > > +                       error = chmod_common(&path, mode);
> > >                 path_put(&path);
> > >                 if (retry_estale(error, lookup_flags)) {
> > >                         lookup_flags |= LOOKUP_REVAL;
> > >                         goto retry;
> > >                 }
> > >         }
> > > +out:
> > >         return error;
> > >  }
> > >
> > > +SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename, umode_t,
> > > +               mode)
> > > +{
> > > +       return sys_fchmodat2(dfd, filename, mode, 0);
> > > +}
> > > +
> > >  SYSCALL_DEFINE2(chmod, const char __user *, filename, umode_t, mode)
> > >  {
> > >         return sys_fchmodat(AT_FDCWD, filename, mode);
> > > diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
> > > index 91a740f6b884..982089d55b31 100644
> > > --- a/include/linux/syscalls.h
> > > +++ b/include/linux/syscalls.h
> > > @@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char __user *filename,
> > >  asmlinkage long sys_faccessat(int dfd, const char __user *filename, int mode);
> > >  asmlinkage long sys_fchmodat(int dfd, const char __user * filename,
> > >                              umode_t mode);
> > > +asmlinkage long sys_fchmodat2(int dfd, const char __user *filename,
> > > +                             umode_t mode, int flag);
> > >  asmlinkage long sys_fchownat(int dfd, const char __user *filename, uid_t user,
> > >                              gid_t group, int flag);
> > >  asmlinkage long sys_openat(int dfd, const char __user *filename, int flags,
> > > diff --git a/include/uapi/asm-generic/unistd.h b/include/uapi/asm-generic/unistd.h
> > > index 9b1462e38b82..e8b0a00908b1 100644
> > > --- a/include/uapi/asm-generic/unistd.h
> > > +++ b/include/uapi/asm-generic/unistd.h
> > > @@ -730,9 +730,11 @@ __SYSCALL(__NR_pkey_mprotect, sys_pkey_mprotect)
> > >  __SYSCALL(__NR_pkey_alloc,    sys_pkey_alloc)
> > >  #define __NR_pkey_free 290
> > >  __SYSCALL(__NR_pkey_free,     sys_pkey_free)
> > > +#define __NR_fchmodat2 291
> > > +__SYSCALL(__NR_fchmodat2,     sys_fchmodat2)
> > >
> > >  #undef __NR_syscalls
> > > -#define __NR_syscalls 291
> > > +#define __NR_syscalls 292
> > >
> > >  /*
> > >   * All syscalls below here should go away really,
> > > diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh
> > > index 2c9082ba6137..2e7471a1d308 100755
> > > --- a/scripts/checksyscalls.sh
> > > +++ b/scripts/checksyscalls.sh
> > > @@ -19,7 +19,7 @@ cat << EOF
> > >  #define __IGNORE_link          /* linkat */
> > >  #define __IGNORE_unlink                /* unlinkat */
> > >  #define __IGNORE_mknod         /* mknodat */
> > > -#define __IGNORE_chmod         /* fchmodat */
> > > +#define __IGNORE_chmod         /* fchmodat2 */
> > >  #define __IGNORE_chown         /* fchownat */
> > >  #define __IGNORE_mkdir         /* mkdirat */
> > >  #define __IGNORE_rmdir         /* unlinkat */
> > > @@ -39,6 +39,7 @@ cat << EOF
> > >
> > >  /* Missing flags argument */
> > >  #define __IGNORE_renameat      /* renameat2 */
> > > +#define __IGNORE_fchmodat      /* fchmodat2 */
> > >
> > >  /* CLOEXEC flag */
> > >  #define __IGNORE_pipe          /* pipe2 */
> > >    
> > 
> > 
> >   
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-02-28 18:23 ` [PATCH 1/2] vfs: implement " Eric Blake
  2017-02-28 18:41   ` Greg Kurz
@ 2017-04-11 17:52   ` Colin Walters
  2017-04-11 17:55     ` Eric Blake
  1 sibling, 1 reply; 15+ messages in thread
From: Colin Walters @ 2017-04-11 17:52 UTC (permalink / raw)
  To: Eric Blake, Greg Kurz, viro; +Cc: linux-fsdevel, linux-kernel



On Tue, Feb 28, 2017, at 02:23 PM, Eric Blake wrote:

> Might also be worth mentioning that this patch is required in order to
> solve CVE-2016-9602, per discussion at
> https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg06089.html

I only briefly looked at this, but can't `open(..., O_PATH)` be used to solve
this today?

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-04-11 17:52   ` Colin Walters
@ 2017-04-11 17:55     ` Eric Blake
  2017-04-11 18:07       ` Eric Blake
  0 siblings, 1 reply; 15+ messages in thread
From: Eric Blake @ 2017-04-11 17:55 UTC (permalink / raw)
  To: Colin Walters, Greg Kurz, viro; +Cc: linux-fsdevel, linux-kernel


[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]

On 04/11/2017 12:52 PM, Colin Walters wrote:
> 
> 
> On Tue, Feb 28, 2017, at 02:23 PM, Eric Blake wrote:
> 
>> Might also be worth mentioning that this patch is required in order to
>> solve CVE-2016-9602, per discussion at
>> https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg06089.html
> 
> I only briefly looked at this, but can't `open(..., O_PATH)` be used to solve
> this today?

O_PATH was the fallback that qemu used - but that's non-POSIX, which
means we have to have a different solution for POSIX systems than for
Linux systems, while waiting for Linux to catch up to POSIX.


-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-04-11 17:55     ` Eric Blake
@ 2017-04-11 18:07       ` Eric Blake
  2017-04-11 18:08         ` Eric Blake
  2017-04-11 19:09         ` Colin Walters
  0 siblings, 2 replies; 15+ messages in thread
From: Eric Blake @ 2017-04-11 18:07 UTC (permalink / raw)
  To: Colin Walters, Greg Kurz, viro; +Cc: linux-fsdevel, linux-kernel


[-- Attachment #1.1: Type: text/plain, Size: 1746 bytes --]

On 04/11/2017 12:55 PM, Eric Blake wrote:
> On 04/11/2017 12:52 PM, Colin Walters wrote:
>>
>>
>> On Tue, Feb 28, 2017, at 02:23 PM, Eric Blake wrote:
>>
>>> Might also be worth mentioning that this patch is required in order to
>>> solve CVE-2016-9602, per discussion at
>>> https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg06089.html
>>
>> I only briefly looked at this, but can't `open(..., O_PATH)` be used to solve
>> this today?
> 
> O_PATH was the fallback that qemu used

Hmm - actually, qemu used O_PATH for the directory portion of *at
traversals:
git.qemu-project.org/?p=qemu.git;a=commitdiff;h=918112c

but did not use O_PATH for its chmod() fallback:
git.qemu-project.org/?p=qemu.git;a=commitdiff;h=e3187a4

A good idea on the surface. But reading the man page of openat(), the
section on O_PATH says:
   The  file
              itself  is not opened, and other file operations (e.g.,
read(2),
              write(2), fchmod(2), fchown(2), fgetxattr(2), mmap(2))
fail with
              the error EBADF.

> - but that's non-POSIX, which
> means we have to have a different solution for POSIX systems than for
> Linux systems, while waiting for Linux to catch up to POSIX.

But even if using open(O_PATH)/fchmod() works, it is not immediately
obvious whether it can catch all the same cases that chmodat(O_NOFOLLOW)
would cover, as there are cases where you have permissions to change
mode bits but not open() the file for reading or writing.  And even if
it gets rid of a TOCTTOU race, it still is a 2-syscall hit rather than
an atomic single syscall.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-04-11 18:07       ` Eric Blake
@ 2017-04-11 18:08         ` Eric Blake
  2017-04-11 19:09         ` Colin Walters
  1 sibling, 0 replies; 15+ messages in thread
From: Eric Blake @ 2017-04-11 18:08 UTC (permalink / raw)
  To: Colin Walters, Greg Kurz, viro; +Cc: linux-fsdevel, linux-kernel


[-- Attachment #1.1: Type: text/plain, Size: 641 bytes --]

On 04/11/2017 01:07 PM, Eric Blake wrote:

> 
> But even if using open(O_PATH)/fchmod() works, it is not immediately
> obvious whether it can catch all the same cases that chmodat(O_NOFOLLOW)

Typo; I obviously meant fchmodat(AT_SYMLINK_NOFOLLOW)

> would cover, as there are cases where you have permissions to change
> mode bits but not open() the file for reading or writing.  And even if
> it gets rid of a TOCTTOU race, it still is a 2-syscall hit rather than
> an atomic single syscall.
> 

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-04-11 18:07       ` Eric Blake
  2017-04-11 18:08         ` Eric Blake
@ 2017-04-11 19:09         ` Colin Walters
  2017-04-19 12:45           ` Greg Kurz
  1 sibling, 1 reply; 15+ messages in thread
From: Colin Walters @ 2017-04-11 19:09 UTC (permalink / raw)
  To: Eric Blake, Greg Kurz, viro; +Cc: linux-fsdevel, linux-kernel

On Tue, Apr 11, 2017, at 02:07 PM, Eric Blake wrote:
> 
> A good idea on the surface. But reading the man page of openat(), the
> section on O_PATH says:
>    The  file
>               itself  is not opened, and other file operations (e.g.,
> read(2),
>               write(2), fchmod(2), fchown(2), fgetxattr(2), mmap(2))
> fail with
>               the error EBADF.

Right, though more topically I'd have expected
fchmodat() (not fchmod()) to take AT_EMPTY_PATH,
just like fstatat() does.

But it doesn't appear to be supported...oh, even at
the syscall level, interesting.   Ah, I see, glibc does:

int
fchmodat (int fd, const char *file, mode_t mode, int flag)
{
  if (flag & ~AT_SYMLINK_NOFOLLOW)
    return INLINE_SYSCALL_ERROR_RETURN_VALUE (EINVAL);
...
}

And indeed the syscall doesn't have flags, bringing us back
to the start here.   Sorry, that seems obvious in retrospect,
but I was "working forwards" from the O_PATH userspace API
mindset.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 1/2] vfs: implement fchmodat2() syscall
  2017-04-11 19:09         ` Colin Walters
@ 2017-04-19 12:45           ` Greg Kurz
  0 siblings, 0 replies; 15+ messages in thread
From: Greg Kurz @ 2017-04-19 12:45 UTC (permalink / raw)
  To: Colin Walters; +Cc: Eric Blake, viro, linux-fsdevel, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]

On Tue, 11 Apr 2017 15:09:40 -0400
Colin Walters <walters@verbum.org> wrote:

> On Tue, Apr 11, 2017, at 02:07 PM, Eric Blake wrote:
> > 
> > A good idea on the surface. But reading the man page of openat(), the
> > section on O_PATH says:
> >    The  file
> >               itself  is not opened, and other file operations (e.g.,
> > read(2),
> >               write(2), fchmod(2), fchown(2), fgetxattr(2), mmap(2))
> > fail with
> >               the error EBADF.  
> 
> Right, though more topically I'd have expected
> fchmodat() (not fchmod()) to take AT_EMPTY_PATH,
> just like fstatat() does.
> 

Like Eric said in another mail, this would still require to open() the file
first... ie, we cannot change mode if initial bits are 0000, whereas it
succeeds with chmod().

> But it doesn't appear to be supported...oh, even at
> the syscall level, interesting.   Ah, I see, glibc does:
> 
> int
> fchmodat (int fd, const char *file, mode_t mode, int flag)
> {
>   if (flag & ~AT_SYMLINK_NOFOLLOW)
>     return INLINE_SYSCALL_ERROR_RETURN_VALUE (EINVAL);
> ...
> }
> 
> And indeed the syscall doesn't have flags, bringing us back
> to the start here.   Sorry, that seems obvious in retrospect,
> but I was "working forwards" from the O_PATH userspace API
> mindset.
> 
> 

The use case is to fix CVE-2016-9602 in QEMU. We need to be able to change
the mode bits of a file that resides under a specific directory, which is
shared between the host and the guest.

Since untrusted code in a guest can create symlinks, we need to be sure
that the file isn't a symlink, otherwise the mode bit change could affect
an arbitrary file not residing under the shared directory.

This could be handled with chroot() or unshare()+chdir() but this isn't an
option because we want this to work even if QEMU is unprivileged.

According to POSIX, this is exactly how fchmodat(AT_SYMLINK_NOFOLLOW) should
behave on Linux:

[EOPNOTSUPP]
    The AT_SYMLINK_NOFOLLOW bit is set in the flag argument, path names a
    symbolic link, and the system does not support changing the mode of a
    symbolic link.

I hope this is clear enough.

--
Greg

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2017-04-19 14:03 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-28 17:03 [PATCH 1/2] vfs: implement fchmodat2() syscall Greg Kurz
2017-02-28 17:03 ` [PATCH 2/2] x86: wire up " Greg Kurz
2017-03-01  9:00   ` kbuild test robot
2017-02-28 18:23 ` [PATCH 1/2] vfs: implement " Eric Blake
2017-02-28 18:41   ` Greg Kurz
2017-02-28 18:59     ` Eric Blake
2017-04-11 17:52   ` Colin Walters
2017-04-11 17:55     ` Eric Blake
2017-04-11 18:07       ` Eric Blake
2017-04-11 18:08         ` Eric Blake
2017-04-11 19:09         ` Colin Walters
2017-04-19 12:45           ` Greg Kurz
2017-03-01  9:01 ` Michael Kerrisk
2017-04-11 11:39   ` Greg Kurz
2017-04-11 12:04     ` Greg Kurz

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.