Eric Lee / smarc-fsl-linux-kernel

02 Nov, 2017

1 commit

  • b24413180   License cleanup: add SPDX GPL-2.0 license identifier to files with no license ... Browse Code »

    Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

09 Jul, 2017

1 commit

  • b8d4c1f9f   Merge branch 'work.misc' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs ... Browse Code »

    Pull misc filesystem updates from Al Viro:
    "Assorted normal VFS / filesystems stuff..."

    * 'work.misc' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
    dentry name snapshots
    Make statfs properly return read-only state after emergency remount
    fs/dcache: init in_lookup_hashtable
    minix: Deinline get_block, save 2691 bytes
    fs: Reorder inode_owner_or_capable() to avoid needless
    fs: warn in case userspace lied about modprobe return

    Linus Torvalds
     

30 Jun, 2017

1 commit

  • a8e2b6367   Make statfs properly return read-only state after emergency remount ... Browse Code »

    Emergency remount (sysrq-u) sets MS_RDONLY to the superblock but doesn't set
    MNT_READONLY to the mount point.

    Once calculate_f_flags() only check for the mount point read only state,
    when setting kstatfs flags, after an emergency remount, statfs does not
    report the filesystem as read-only, even though it is.

    Enable flags_by_sb() to also check for superblock read only state, so the
    kstatfs and consequently statfs can properly show the read-only state of
    the filesystem.

    Signed-off-by: Carlos Maiolino
    Signed-off-by: Al Viro

    Carlos Maiolino
     

05 Jun, 2017

1 commit

18 Apr, 2017

1 commit

06 Dec, 2016

1 commit

13 Oct, 2013

1 commit

  • 9d05746e7   vfs: allow O_PATH file descriptors for fstatfs() ... Browse Code »

    Olga reported that file descriptors opened with O_PATH do not work with
    fstatfs(), found during further development of ksh93's thread support.

    There is no reason to not allow O_PATH file descriptors here (fstatfs is
    very much a path operation), so use "fdget_raw()". See commit
    55815f70147d ("vfs: make O_PATH file descriptors usable for 'fstat()'")
    for a very similar issue reported for fstat() by the same team.

    Reported-and-tested-by: ольга крыжановская
    Acked-by: Al Viro
    Cc: stable@kernel.org # O_PATH introduced in 3.0+
    Signed-off-by: Linus Torvalds

    Linus Torvalds
     

21 Dec, 2012

1 commit

27 Sep, 2012

1 commit

30 May, 2012

1 commit

29 Feb, 2012

1 commit

04 Jan, 2012

1 commit

05 Nov, 2011

1 commit

  • 5c8a0fbba   VFS: fix statfs() automounter semantics regression ... Browse Code »
    1

    No one in their right mind would expect statfs() to not work on a
    automounter managed mount point. Fix it.

    [ I'm not sure about the "no one in their right mind" part. It's not
    mounted, and you didn't ask for it to be mounted. But nobody will
    really care, and this probably makes it match previous semantics, so..
    - Linus ]

    This mirrors the fix made to the quota code in 815d405ceff0d69646.

    Signed-off-by: Dan McGee
    Cc: Trond Myklebust
    Cc: Alexander Viro
    Cc: stable@kernel.org
    Signed-off-by: Linus Torvalds

    Dan McGee
     

14 Mar, 2011

1 commit

  • c8b91accf   clean statfs-like syscalls up ... Browse Code »

    New helpers: user_statfs() and fd_statfs(), taking userland pathname and
    descriptor resp. and filling struct kstatfs. Syscalls of statfs family
    (native, compat and foreign - osf and hpux on alpha and parisc resp.)
    switched to those. Removes some boilerplate code, simplifies cleanup
    on errors...

    Signed-off-by: Al Viro

    Al Viro
     

10 Aug, 2010

2 commits

  • 365b18189   add f_flags to struct statfs(64) ... Browse Code »

    Add a flags field to help glibc implementing statvfs(3) efficiently.

    We copy the flag values from glibc, and add a new ST_VALID flag to
    denote that f_flags is implemented.

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Al Viro

    Christoph Hellwig
     
  • ebabe9a90   pass a struct path to vfs_statfs ... Browse Code »

    We'll need the path to implement the flags field for statvfs support.
    We do have it available in all callers except:

    - ecryptfs_statfs. This one doesn't actually need vfs_statfs but just
    needs to do a caller to the lower filesystem statfs method.
    - sys_ustat. Add a non-exported statfs_by_dentry helper for it which
    doesn't won't be able to fill out the flags field later on.

    In addition rename the helpers for statfs vs fstatfs to do_*statfs instead
    of the misleading vfs prefix.

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Al Viro

    Christoph Hellwig
     

22 May, 2010

1 commit