[LTP] utimensat EACCES vs. EPERM in 4.8+

Jan Stancek jstancek@redhat.com
Mon Jan 16 16:46:45 CET 2017


we seem to have a conflict between kernel and man pages.
>From utimensat man page:

EACCES times is NULL, or both tv_nsec values are UTIME_NOW, and either:
       *  the effective user ID of the caller does not match the owner of the
          file, the caller does not  have  write  access  to  the file, and the
          caller is not privileged (Linux: does not have either the CAP_FOWNER
          or the CAP_DAC_OVERRIDE capability); or,
       *  the file is marked immutable (see chattr(1)).

But following 2 commits gradually replaced EACCES with EPERM.

commit 337684a1746f93ae107e05d90977b070bb7e39d8
Author: Eryu Guan <guaneryu@gmail.com>
Date:   Tue Aug 2 19:58:28 2016 +0800
    fs: return EPERM on immutable inode

commit f2b20f6ee842313a0d681dbbf7f87b70291a6a3b
Author: Miklos Szeredi <mszeredi@redhat.com>
Date:   Fri Sep 16 12:44:20 2016 +0200
    vfs: move permission checking into notify_change() for utimes(NULL)

4.9 kernel and simple touch on immutable file gives me:
utimensat(AT_FDCWD, "afile", NULL, 0)   = -1 EPERM (Operation not permitted)

while an older kernel it gives me:
utimensat(AT_FDCWD, "afile", NULL, 0)   = -1 EACCES (Permission denied)

Do we need to update man page or fix kernel back to return EACCES?


More information about the ltp mailing list