linux-toradex.git/fs/devpts, branch v4.9-rc3

Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs

2016-10-11T03:16:43+00:00

Pull more vfs updates from Al Viro:
 ">rename2() work from Miklos + current_time() from Deepa"

* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
  fs: Replace current_fs_time() with current_time()
  fs: Replace CURRENT_TIME_SEC with current_time() for inode timestamps
  fs: Replace CURRENT_TIME with current_time() for inode timestamps
  fs: proc: Delete inode time initializations in proc_alloc_inode()
  vfs: Add current_time() api
  vfs: add note about i_op->rename changes to porting
  fs: rename "rename2" i_op to "rename"
  vfs: remove unused i_op->rename
  fs: make remaining filesystems use .rename2
  libfs: support RENAME_NOREPLACE in simple_rename()
  fs: support RENAME_NOREPLACE for local filesystems
  ncpfs: fix unused variable warning

fs: Replace CURRENT_TIME with current_time() for inode timestamps

2016-09-28T01:06:21+00:00

CURRENT_TIME macro is not appropriate for filesystems as it
doesn't use the right granularity for filesystem timestamps.
Use current_time() instead.

CURRENT_TIME is also not y2038 safe.

This is also in preparation for the patch that transitions
vfs timestamps to use 64 bit time and hence make them
y2038 safe. As part of the effort current_time() will be
extended to do range checks. Hence, it is necessary for all
file system timestamps to use current_time(). Also,
current_time() will be transitioned along with vfs to be
y2038 safe.

Note that whenever a single call to current_time() is used
to change timestamps in different inodes, it is because they
share the same time granularity.

Signed-off-by: Deepa Dinamani 
Reviewed-by: Arnd Bergmann 
Acked-by: Felipe Balbi 
Acked-by: Steven Whitehouse 
Acked-by: Ryusuke Konishi 
Acked-by: David Sterba 
Signed-off-by: Al Viro

devpts: Change the owner of /dev/pts/ptmx to the mounter of /dev/pts

2016-09-23T09:31:31+00:00

In 99.99% of the cases only root in a user namespace can mount /dev/pts
and in those cases the owner of /dev/pts/ptmx will remain root.root

In the oddball case where someone else has CAP_SYS_ADMIN this code
modifies the /dev/pts mount code to use current_fsuid and current_fsgid
as the values to use when creating the /dev/ptmx inode.  As is done
when any other file is created.

This is a code simplification, and it allows running without a root
user entirely.

Signed-off-by: "Eric W. Biederman" 
Signed-off-by: Greg Kroah-Hartman

devpts: Remove sync_filesystems

2016-09-23T09:31:31+00:00

devpts does not and never will have anything to sync
so don't bother calling sync_filesystems on remount.

Signed-off-by: "Eric W. Biederman" 
Signed-off-by: Greg Kroah-Hartman

devpts: Make devpts_kill_sb safe if fsi is NULL

2016-09-23T09:31:31+00:00

Signed-off-by: "Eric W. Biederman" 
Signed-off-by: Greg Kroah-Hartman

devpts: Simplify devpts_mount by using mount_nodev

2016-09-23T09:31:31+00:00

Now that all of the work of setting up a superblock has been moved to
devpts_fill_super simplify devpts_mount by calling mount_nodev instead
of rolling mount_nodev by hand.

Signed-off-by: "Eric W. Biederman" 
Signed-off-by: Greg Kroah-Hartman

devpts: Move the creation of /dev/pts/ptmx into fill_super

2016-09-23T09:31:31+00:00

The code makes more sense here and things are just clearer.

Signed-off-by: "Eric W. Biederman" 
Signed-off-by: Greg Kroah-Hartman

devpts: Move parse_mount_options into fill_super

2016-09-23T09:31:31+00:00

Signed-off-by: "Eric W. Biederman" 
Signed-off-by: Greg Kroah-Hartman

devpts: return NULL pts 'priv' entry for non-devpts nodes

2016-09-03T18:02:50+00:00

In commit 8ead9dd54716 ("devpts: more pty driver interface cleanups") I
made devpts_get_priv() just return the dentry->fs_data directly.  And
because I thought it wouldn't happen, I added a warning if you ever saw
a pts node that wasn't on devpts.

And no, that warning never triggered under any actual real use, but you
can trigger it by creating nonsensical pts nodes by hand.

So just revert the warning, and make devpts_get_priv() return NULL for
that case like it used to.

Reported-by: Dmitry Vyukov 
Cc: stable@vger.kernel.org # 4.6+
Cc: Eric W Biederman" 
Signed-off-by: Linus Torvalds

userns: Remove the now unnecessary FS_USERNS_DEV_MOUNT flag

2016-06-23T20:47:31+00:00

Now that SB_I_NODEV controls the nodev behavior devpts can just clear
this flag during mount.  Simplifying the code and making it easier
to audit how the code works.  While still preserving the invariant
that s_iflags is only modified during mount.

Acked-by: Seth Forshee 
Signed-off-by: "Eric W. Biederman"