02 Nov, 2017

1 commit

  • 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
     

27 Apr, 2017

1 commit

  • In the past, readdir assumed that the user buffer will be large enough
    that all entries from the server will fit. If this was not true,
    entries would be skipped.

    Since it works now, request 512 entries rather than 96 per server
    operation.

    Signed-off-by: Martin Brandenburg
    Signed-off-by: Mike Marshall

    Martin Brandenburg
     

10 Feb, 2017

1 commit

  • The deamon through which the kernel module communicates with the userspace
    part of Orangefs, the "client-core", sends initialization data to the
    kernel module with ioctl. The initialization data was built by the
    client-core in a 2k buffer and copy_from_user'd into a 1k buffer
    in the kernel module. When more than 1k of initialization data needed
    to be sent, some was lost, reducing the usability of the control by which
    debug levels are set. This patch sets the kernel side buffer to 2K to
    match the userspace side...

    Signed-off-by: Mike Marshall

    Mike Marshall
     

13 Aug, 2016

1 commit

  • This is a new userspace operation, which will be done if the client-core
    version is greater than or equal to 2.9.6. This will provide a way to
    implement optional features and to determine which features are
    supported by the client-core. If the client-core version is older than
    2.9.6, no optional features are supported and the op will not be done.

    The intent is to allow protocol extensions without relying on the
    client-core's current behavior of ignoring what it doesn't understand.

    Signed-off-by: Martin Brandenburg

    Martin Brandenburg
     

09 Aug, 2016

1 commit

  • This has been dormant code for many years. Parts of it were removed from
    the OrangeFS kernel code when it went into mainline. These bits were missed.
    Now the readahead cache has been resurrected in the OrangeFS userspace
    portions. It was renamed there, since it doesn't really have anything to do
    with mmap specifically, so it will be renamed here.

    Signed-off-by: Martin Brandenburg

    Martin Brandenburg
     

25 Feb, 2016

1 commit


05 Jan, 2016

1 commit


05 Dec, 2015

1 commit