linux-toradex.git/fs/freevxfs, branch v5.1-rc4

freevxfs_lookup(): use d_splice_alias()

2018-05-22T18:27:51+00:00

code is simpler that way
Cc: Christoph Hellwig 
Signed-off-by: Al Viro

vxfs: Define usercopy region in vxfs_inode slab cache

2018-01-15T20:07:57+00:00

vxfs symlink pathnames, stored in struct vxfs_inode_info field
vii_immed.vi_immed and therefore contained in the vxfs_inode slab cache,
need to be copied to/from userspace.

cache object allocation:
    fs/freevxfs/vxfs_super.c:
        vxfs_alloc_inode(...):
            ...
            vi = kmem_cache_alloc(vxfs_inode_cachep, GFP_KERNEL);
            ...
            return &vi->vfs_inode;

    fs/freevxfs/vxfs_inode.c:
        cxfs_iget(...):
            ...
            inode->i_link = vip->vii_immed.vi_immed;

example usage trace:
    readlink_copy+0x43/0x70
    vfs_readlink+0x62/0x110
    SyS_readlinkat+0x100/0x130

    fs/namei.c:
        readlink_copy(..., link):
            ...
            copy_to_user(..., link, len);

        (inlined in vfs_readlink)
        generic_readlink(dentry, ...):
            struct inode *inode = d_inode(dentry);
            const char *link = inode->i_link;
            ...
            readlink_copy(..., link);

In support of usercopy hardening, this patch defines a region in the
vxfs_inode slab cache in which userspace copy operations are allowed.

This region is known as the slab cache's usercopy region. Slab caches
can now check that each dynamically sized copy operation involving
cache-managed memory falls entirely within the slab's usercopy region.

This patch is modified from Brad Spengler/PaX Team's PAX_USERCOPY
whitelisting code in the last public patch of grsecurity/PaX based on my
understanding of the code. Changes or omissions from the original code are
mine and don't reflect the original grsecurity/PaX code.

Signed-off-by: David Windsor 
[kees: adjust commit log, provide usage trace]
Cc: Christoph Hellwig 
Signed-off-by: Kees Cook

Rename superblock flags (MS_xyz -> SB_xyz)

2017-11-27T21:05:09+00:00

This is a pure automated search-and-replace of the internal kernel
superblock flags.

The s_flags are now called SB_*, with the names and the values for the
moment mirroring the MS_* flags that they're equivalent to.

Note how the MS_xyz flags are the ones passed to the mount system call,
while the SB_xyz flags are what we then use in sb->s_flags.

The script to do this was:

    # places to look in; re security/*: it generally should *not* be
    # touched (that stuff parses mount(2) arguments directly), but
    # there are two places where we really deal with superblock flags.
    FILES="drivers/mtd drivers/staging/lustre fs ipc mm \
            include/linux/fs.h include/uapi/linux/bfs_fs.h \
            security/apparmor/apparmorfs.c security/apparmor/include/lib.h"
    # the list of MS_... constants
    SYMS="RDONLY NOSUID NODEV NOEXEC SYNCHRONOUS REMOUNT MANDLOCK \
          DIRSYNC NOATIME NODIRATIME BIND MOVE REC VERBOSE SILENT \
          POSIXACL UNBINDABLE PRIVATE SLAVE SHARED RELATIME KERNMOUNT \
          I_VERSION STRICTATIME LAZYTIME SUBMOUNT NOREMOTELOCK NOSEC BORN \
          ACTIVE NOUSER"

    SED_PROG=
    for i in $SYMS; do SED_PROG="$SED_PROG -e s/MS_$i/SB_$i/g"; done

    # we want files that contain at least one of MS_...,
    # with fs/namespace.c and fs/pnode.c excluded.
    L=$(for i in $SYMS; do git grep -w -l MS_$i $FILES; done| sort|uniq|grep -v '^fs/namespace.c'|grep -v '^fs/pnode.c')

    for f in $L; do sed -i $f $SED_PROG; done

Requested-by: Al Viro 
Signed-off-by: Linus Torvalds

freevxfs: update Kconfig information

2016-06-13T08:20:39+00:00

Signed-off-by: Krzysztof Błaszkowski 
Signed-off-by: Christoph Hellwig

freevxfs: refactor readdir and lookup code

2016-06-12T17:35:17+00:00

This change fixes also a buffer overflow which was caused by
accessing address space beyond mapped page

Signed-off-by: Krzysztof Błaszkowski 
Signed-off-by: Christoph Hellwig

freevxfs: fix lack of inode initialization

2016-06-12T17:35:13+00:00

There is nothing worse than just allocated inode without being
initialized _once().

Signed-off-by: Krzysztof Błaszkowski 
Signed-off-by: Christoph Hellwig

freevxfs: fix memory leak in vxfs_read_fshead()

2016-06-12T17:27:31+00:00

Every successful mount two structs vxfs_fsh were not released.

Signed-off-by: Krzysztof Błaszkowski 
Signed-off-by: Christoph Hellwig

freevxfs: update documentation and cresdits for HP-UX support

2016-06-01T07:27:33+00:00

Signed-off-by: Krzysztof Błaszkowski 
[hch: cosmetic updates]
Signed-off-by: Christoph Hellwig

freevxfs: implement ->alloc_inode and ->destroy_inode

2016-06-01T07:23:24+00:00

This driver predates those methods and was trying to be clever allocating
it's own private data.  Switch to the generic scheme used by other file
systems.

Based on an earlier patch from Krzysztof Błaszkowski .

Signed-off-by: Christoph Hellwig

freevxfs: avoid the need for forward declaring the super operations

2016-06-01T07:21:26+00:00

Signed-off-by: Christoph Hellwig