linux.git/drivers/staging/gs_fpgaboot, branch v5.8

staging: remove redundant 'default n' from Kconfig

2019-04-16T11:39:01+00:00

'default n' is the default value for any bool or tristate Kconfig
setting so there is no need to write it explicitly.

Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
is not set' for visible symbols") the Kconfig behavior is the same
regardless of 'default n' being present or not:

    ...
    One side effect of (and the main motivation for) this change is making
    the following two definitions behave exactly the same:

        config FOO
                bool

        config FOO
                bool
                default n

    With this change, neither of these will generate a
    '# CONFIG_FOO is not set' line (assuming FOO isn't selected/implied).
    That might make it clearer to people that a bare 'default n' is
    redundant.
    ...

Signed-off-by: Bartlomiej Zolnierkiewicz 
Signed-off-by: Greg Kroah-Hartman

staging: add missing SPDX lines to Makefile files

2019-04-03T09:10:15+00:00

There are a few remaining drivers/staging/*/Makefile files that do not
have SPDX identifiers in them.  Add the correct GPL-2.0 identifier to
them to make scanning tools happy.

Reviewed-by: Mukesh Ojha 
Signed-off-by: Greg Kroah-Hartman

staging: add missing SPDX lines to Kconfig files

2019-04-03T09:10:15+00:00

There are a few remaining drivers/staging/*/Kconfig files that do not
have SPDX identifiers in them.  Add the correct GPL-2.0 identifier to
them to make scanning tools happy.

Signed-off-by: Greg Kroah-Hartman

staging: gs_fpgaboot: cleanup alignment issue - style

2019-01-15T15:08:05+00:00

Cleanup alignment issue reported by checkpatch.
CHECK: Alignment should match open parenthesis

Signed-off-by: Michael Straube 
Signed-off-by: Greg Kroah-Hartman

staging: gs_fpgaboot: add SPDX identifiers

2019-01-15T15:08:05+00:00

This satisfies a checkpatch warning and is the preferred
method for notating the license.

The SPDX identifier is a legally binding shorthand, which
can be used instead of the full boiler plate text.

Signed-off-by: Michael Straube 
Signed-off-by: Greg Kroah-Hartman

Staging: gs_fpgaboot: remove FSF's mailing address from io.h

2018-01-08T15:47:23+00:00

This patch removes FSF's mailing address issue from io.h found by
checkpatch.pl tool.

Signed-off-by: Shubham Kumaram 
Signed-off-by: Greg Kroah-Hartman

staging: gs_fpgaboot: pr_err() strings should end with newlines

2017-10-03T16:36:25+00:00

pr_err() messages should end with a new-line to avoid other messages
being concatenated.

Signed-off-by: Arvind Yadav 
Signed-off-by: Greg Kroah-Hartman

staging: gs_fpgaboot: return valid error codes

2017-07-29T00:07:37+00:00

The return values on error are modified to be valid error codes. Theses
error codes are propagated back to the init function's return.

Signed-off-by: Jacob von Chorus 
Signed-off-by: Greg Kroah-Hartman

staging: gs_fpgaboot: change char to u8

2017-07-29T00:07:37+00:00

The bitstream storage variables were changed from char to u8 arrays to
prevent issues such as negative lengths. This change makes the code
compatible with the "data" field in "struct firmware" which is of type
u8.

Signed-off-by: Jacob von Chorus 
Signed-off-by: Greg Kroah-Hartman

staging: gs_fpgaboot: add buffer overflow checks

2017-07-29T00:07:37+00:00

Four fields in struct fpgaimage are char arrays of length MAX_STR (256).
The amount of data read into these buffers is controlled by a length
field in the bitstream file read from userspace. If a corrupt or
malicious firmware file was supplied, kernel data beyond these buffers
can be overwritten arbitrarily.

This patch adds a check of the bitstream's length value to ensure it
fits within the bounds of the allocated buffers. An error condition is
returned from gs_read_bitstream if any of the reads fail.

Signed-off-by: Jacob von Chorus 
Signed-off-by: Greg Kroah-Hartman