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
     

12 Apr, 2015

1 commit

16 Oct, 2014

1 commit

17 Mar, 2011

1 commit

13 Jan, 2011

1 commit

13 Oct, 2007

1 commit

  • bfab36e81   NTFS: Fix a mount time deadlock. ... Browse Code »

    Big thanks go to Mathias Kolehmainen for reporting the bug, providing
    debug output and testing the patches I sent him to get it working.

    The fix was to stop calling ntfs_attr_set() at mount time as that causes
    balance_dirty_pages_ratelimited() to be called which on systems with
    little memory actually tries to go and balance the dirty pages which tries
    to take the s_umount semaphore but because we are still in fill_super()
    across which the VFS holds s_umount for writing this results in a
    deadlock.

    We now do the dirty work by hand by submitting individual buffers. This
    has the annoying "feature" that mounting can take a few seconds if the
    journal is large as we have clear it all. One day someone should improve
    on this by deferring the journal clearing to a helper kernel thread so it
    can be done in the background but I don't have time for this at the moment
    and the current solution works fine so I am leaving it like this for now.

    Signed-off-by: Anton Altaparmakov
    Signed-off-by: Linus Torvalds

    Anton Altaparmakov
     

18 Jan, 2007

1 commit

23 Mar, 2006

1 commit

24 Feb, 2006

1 commit

11 Oct, 2005

1 commit

  • 98b270362   NTFS: The big ntfs write(2) rewrite has arrived. We now implement our own ... Browse Code »

    file operations ->write(), ->aio_write(), and ->writev() for regular
    files. This replaces the old use of generic_file_write(), et al and
    the address space operations ->prepare_write and ->commit_write.
    This means that both sparse and non-sparse (unencrypted and
    uncompressed) files can now be extended using the normal write(2)
    code path. There are two limitations at present and these are that
    we never create sparse files and that we only have limited support
    for highly fragmented files, i.e. ones whose data attribute is split
    across multiple extents. When such a case is encountered,
    EOPNOTSUPP is returned.

    Signed-off-by: Anton Altaparmakov

    Anton Altaparmakov
     

04 Oct, 2005

1 commit

26 Sep, 2005

1 commit

23 Sep, 2005

1 commit

09 Sep, 2005

1 commit

08 Sep, 2005

1 commit

  • e7a1033b9   NTFS: Support more clean journal ($LogFile) states. ... Browse Code »

    - Support journals ($LogFile) which have been modified by chkdsk. This
    means users can boot into Windows after we marked the volume dirty.
    The Windows boot will run chkdsk and then reboot. The user can then
    immediately boot into Linux rather than having to do a full Windows
    boot first before rebooting into Linux and we will recognize such a
    journal and empty it as it is clean by definition.
    - Support journals ($LogFile) with only one restart page as well as
    journals with two different restart pages. We sanity check both and
    either use the only sane one or the more recent one of the two in the
    case that both are valid.

    Signed-off-by: Anton Altaparmakov

    Anton Altaparmakov
     

26 Jun, 2005

1 commit

25 Jun, 2005

1 commit

04 May, 2005

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds