License cleanup: add SPDX GPL-2.0 license identifier to files with no license
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 <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 22:07:57 +08:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
|
* Request reply cache. This was heavily inspired by the
|
|
|
|
|
* implementation in 4.3BSD/4.4BSD.
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 1995, 1996 Olaf Kirch <okir@monad.swb.de>
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef NFSCACHE_H
|
|
|
|
|
#define NFSCACHE_H
|
|
|
|
|
|
2009-12-04 02:28:59 +08:00
|
|
|
#include <linux/sunrpc/svc.h>
|
2019-05-17 21:03:38 +08:00
|
|
|
#include "netns.h"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
/*
|
2009-04-01 04:28:13 +08:00
|
|
|
* Representation of a reply cache entry.
|
2013-01-29 03:41:07 +08:00
|
|
|
*
|
|
|
|
|
* Note that we use a sockaddr_in6 to hold the address instead of the more
|
|
|
|
|
* typical sockaddr_storage. This is for space reasons, since sockaddr_storage
|
|
|
|
|
* is much larger than a sockaddr_in6.
|
2005-04-17 06:20:36 +08:00
|
|
|
*/
|
2023-07-09 23:45:48 +08:00
|
|
|
struct nfsd_cacherep {
|
2018-10-04 01:11:51 +08:00
|
|
|
struct {
|
|
|
|
|
/* Keep often-read xid, csum in the same cache line: */
|
|
|
|
|
__be32 k_xid;
|
|
|
|
|
__wsum k_csum;
|
|
|
|
|
u32 k_proc;
|
|
|
|
|
u32 k_prot;
|
|
|
|
|
u32 k_vers;
|
|
|
|
|
unsigned int k_len;
|
|
|
|
|
struct sockaddr_in6 k_addr;
|
|
|
|
|
} c_key;
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2018-10-01 22:41:57 +08:00
|
|
|
struct rb_node c_node;
|
2018-10-04 01:11:51 +08:00
|
|
|
struct list_head c_lru;
|
2005-04-17 06:20:36 +08:00
|
|
|
unsigned char c_state, /* unused, inprog, done */
|
|
|
|
|
c_type, /* status, buffer */
|
|
|
|
|
c_secure : 1; /* req came from port < 1024 */
|
|
|
|
|
unsigned long c_timestamp;
|
|
|
|
|
union {
|
|
|
|
|
struct kvec u_vec;
|
2006-10-20 14:29:02 +08:00
|
|
|
__be32 u_status;
|
2005-04-17 06:20:36 +08:00
|
|
|
} c_u;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#define c_replvec c_u.u_vec
|
|
|
|
|
#define c_replstat c_u.u_status
|
|
|
|
|
|
|
|
|
|
/* cache entry states */
|
|
|
|
|
enum {
|
|
|
|
|
RC_UNUSED,
|
|
|
|
|
RC_INPROG,
|
|
|
|
|
RC_DONE
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/* return values */
|
|
|
|
|
enum {
|
|
|
|
|
RC_DROPIT,
|
|
|
|
|
RC_REPLY,
|
2013-01-29 03:41:09 +08:00
|
|
|
RC_DOIT
|
2005-04-17 06:20:36 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Cache types.
|
|
|
|
|
* We may want to add more types one day, e.g. for diropres and
|
|
|
|
|
* attrstat replies. Using cache entries with fixed length instead
|
|
|
|
|
* of buffer pointers may be more efficient.
|
|
|
|
|
*/
|
|
|
|
|
enum {
|
|
|
|
|
RC_NOCACHE,
|
|
|
|
|
RC_REPLSTAT,
|
|
|
|
|
RC_REPLBUFF,
|
|
|
|
|
};
|
|
|
|
|
|
2013-01-29 03:41:13 +08:00
|
|
|
/* Cache entries expire after this time period */
|
|
|
|
|
#define RC_EXPIRE (120 * HZ)
|
|
|
|
|
|
2013-02-05 00:57:27 +08:00
|
|
|
/* Checksum this amount of the request */
|
|
|
|
|
#define RC_CSUMLEN (256U)
|
|
|
|
|
|
2020-06-02 05:44:45 +08:00
|
|
|
int nfsd_drc_slab_create(void);
|
|
|
|
|
void nfsd_drc_slab_free(void);
|
2019-05-17 21:03:38 +08:00
|
|
|
int nfsd_reply_cache_init(struct nfsd_net *);
|
|
|
|
|
void nfsd_reply_cache_shutdown(struct nfsd_net *);
|
NFSD: Fix checksum mismatches in the duplicate reply cache
nfsd_cache_csum() currently assumes that the server's RPC layer has
been advancing rq_arg.head[0].iov_base as it decodes an incoming
request, because that's the way it used to work. On entry, it
expects that buf->head[0].iov_base points to the start of the NFS
header, and excludes the already-decoded RPC header.
These days however, head[0].iov_base now points to the start of the
RPC header during all processing. It no longer points at the NFS
Call header when execution arrives at nfsd_cache_csum().
In a retransmitted RPC the XID and the NFS header are supposed to
be the same as the original message, but the contents of the
retransmitted RPC header can be different. For example, for krb5,
the GSS sequence number will be different between the two. Thus if
the RPC header is always included in the DRC checksum computation,
the checksum of the retransmitted message might not match the
checksum of the original message, even though the NFS part of these
messages is identical.
The result is that, even if a matching XID is found in the DRC,
the checksum mismatch causes the server to execute the
retransmitted RPC transaction again.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Tested-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
2023-11-11 00:28:45 +08:00
|
|
|
int nfsd_cache_lookup(struct svc_rqst *rqstp, unsigned int start,
|
|
|
|
|
unsigned int len, struct nfsd_cacherep **cacherep);
|
2023-07-09 23:45:48 +08:00
|
|
|
void nfsd_cache_update(struct svc_rqst *rqstp, struct nfsd_cacherep *rp,
|
2023-07-09 23:45:41 +08:00
|
|
|
int cachetype, __be32 *statp);
|
2022-09-23 00:31:55 +08:00
|
|
|
int nfsd_reply_cache_stats_show(struct seq_file *m, void *v);
|
2009-04-06 17:00:49 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
#endif /* NFSCACHE_H */
|
