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 14:07:57 +00:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
2008-01-10 10:49:06 +00:00
|
|
|
/*
|
|
|
|
|
* ipv6 in net namespaces
|
|
|
|
|
*/
|
|
|
|
|
|
2008-01-10 10:56:03 +00:00
|
|
|
#include <net/inet_frag.h>
|
|
|
|
|
|
2008-01-10 10:49:06 +00:00
|
|
|
#ifndef __NETNS_IPV6_H__
|
|
|
|
|
#define __NETNS_IPV6_H__
|
2009-08-29 01:34:49 +00:00
|
|
|
#include <net/dst_ops.h>
|
2019-04-17 20:35:49 +00:00
|
|
|
#include <uapi/linux/icmpv6.h>
|
2008-01-10 10:49:06 +00:00
|
|
|
|
2008-01-10 10:53:43 +00:00
|
|
|
struct ctl_table_header;
|
|
|
|
|
|
|
|
|
|
struct netns_sysctl_ipv6 {
|
|
|
|
|
#ifdef CONFIG_SYSCTL
|
2012-04-19 13:37:09 +00:00
|
|
|
struct ctl_table_header *hdr;
|
|
|
|
|
struct ctl_table_header *route_hdr;
|
|
|
|
|
struct ctl_table_header *icmp_hdr;
|
2008-01-22 14:08:36 +00:00
|
|
|
struct ctl_table_header *frags_hdr;
|
2013-02-06 09:46:33 +00:00
|
|
|
struct ctl_table_header *xfrm6_hdr;
|
2008-01-10 10:53:43 +00:00
|
|
|
#endif
|
2008-01-10 11:01:01 +00:00
|
|
|
int flush_delay;
|
|
|
|
|
int ip6_rt_max_size;
|
|
|
|
|
int ip6_rt_gc_min_interval;
|
|
|
|
|
int ip6_rt_gc_timeout;
|
|
|
|
|
int ip6_rt_gc_interval;
|
|
|
|
|
int ip6_rt_gc_elasticity;
|
|
|
|
|
int ip6_rt_mtu_expires;
|
|
|
|
|
int ip6_rt_min_advmss;
|
2021-05-17 18:15:22 +00:00
|
|
|
u32 multipath_hash_fields;
|
2021-03-31 17:52:12 +00:00
|
|
|
u8 multipath_hash_policy;
|
2021-05-17 18:15:22 +00:00
|
|
|
u8 bindv6only;
|
2021-03-31 17:52:12 +00:00
|
|
|
u8 flowlabel_consistency;
|
|
|
|
|
u8 auto_flowlabels;
|
2008-01-10 11:02:40 +00:00
|
|
|
int icmpv6_time;
|
2021-03-31 17:52:12 +00:00
|
|
|
u8 icmpv6_echo_ignore_all;
|
|
|
|
|
u8 icmpv6_echo_ignore_multicast;
|
|
|
|
|
u8 icmpv6_echo_ignore_anycast;
|
2019-04-17 20:35:49 +00:00
|
|
|
DECLARE_BITMAP(icmpv6_ratemask, ICMPV6_MSG_MAX + 1);
|
|
|
|
|
unsigned long *icmpv6_ratemask_ptr;
|
2021-03-31 17:52:12 +00:00
|
|
|
u8 anycast_src_echo_reply;
|
|
|
|
|
u8 ip_nonlocal_bind;
|
|
|
|
|
u8 fwmark_reflect;
|
|
|
|
|
u8 flowlabel_state_ranges;
|
2015-03-23 22:36:05 +00:00
|
|
|
int idgen_retries;
|
|
|
|
|
int idgen_delay;
|
2017-08-23 07:55:41 +00:00
|
|
|
int flowlabel_reflect;
|
2017-10-30 21:16:00 +00:00
|
|
|
int max_dst_opts_cnt;
|
|
|
|
|
int max_hbh_opts_cnt;
|
|
|
|
|
int max_dst_opts_len;
|
|
|
|
|
int max_hbh_opts_len;
|
ipv6: sr: Compute flowlabel for outer IPv6 header of seg6 encap mode
ECMP (equal-cost multipath) hashes are typically computed on the packets'
5-tuple(src IP, dst IP, src port, dst port, L4 proto).
For encapsulated packets, the L4 data is not readily available and ECMP
hashing will often revert to (src IP, dst IP). This will lead to traffic
polarization on a single ECMP path, causing congestion and waste of network
capacity.
In IPv6, the 20-bit flow label field is also used as part of the ECMP hash.
In the lack of L4 data, the hashing will be on (src IP, dst IP, flow
label). Having a non-zero flow label is thus important for proper traffic
load balancing when L4 data is unavailable (i.e., when packets are
encapsulated).
Currently, the seg6_do_srh_encap() function extracts the original packet's
flow label and set it as the outer IPv6 flow label. There are two issues
with this behaviour:
a) There is no guarantee that the inner flow label is set by the source.
b) If the original packet is not IPv6, the flow label will be set to
zero (e.g., IPv4 or L2 encap).
This patch adds a function, named seg6_make_flowlabel(), that computes a
flow label from a given skb. It supports IPv6, IPv4 and L2 payloads, and
leverages the per namespace 'seg6_flowlabel" sysctl value.
The currently support behaviours are as follows:
-1 set flowlabel to zero.
0 copy flowlabel from Inner paceket in case of Inner IPv6
(Set flowlabel to 0 in case IPv4/L2)
1 Compute the flowlabel using seg6_make_flowlabel()
This patch has been tested for IPv6, IPv4, and L2 traffic.
Signed-off-by: Ahmed Abdelsalam <amsalam20@gmail.com>
Acked-by: David Lebrun <dlebrun@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2018-04-24 18:23:16 +00:00
|
|
|
int seg6_flowlabel;
|
ipv6: ioam: Data plane support for Pre-allocated Trace
Implement support for processing the IOAM Pre-allocated Trace with IPv6,
see [1] and [2]. Introduce a new IPv6 Hop-by-Hop TLV option, see IANA [3].
A new per-interface sysctl is introduced. The value is a boolean to accept (=1)
or ignore (=0, by default) IPv6 IOAM options on ingress for an interface:
- net.ipv6.conf.XXX.ioam6_enabled
Two other sysctls are introduced to define IOAM IDs, represented by an integer.
They are respectively per-namespace and per-interface:
- net.ipv6.ioam6_id
- net.ipv6.conf.XXX.ioam6_id
The value of the first one represents the IOAM ID of the node itself (u32; max
and default value = U32_MAX>>8, due to hop limit concatenation) while the other
represents the IOAM ID of an interface (u16; max and default value = U16_MAX).
Each "ioam6_id" sysctl has a "_wide" equivalent:
- net.ipv6.ioam6_id_wide
- net.ipv6.conf.XXX.ioam6_id_wide
The value of the first one represents the wide IOAM ID of the node itself (u64;
max and default value = U64_MAX>>8, due to hop limit concatenation) while the
other represents the wide IOAM ID of an interface (u32; max and default value
= U32_MAX).
The use of short and wide equivalents is not exclusive, a deployment could
choose to leverage both. For example, net.ipv6.conf.XXX.ioam6_id (short format)
could be an identifier for a physical interface, whereas
net.ipv6.conf.XXX.ioam6_id_wide (wide format) could be an identifier for a
logical sub-interface. Documentation about new sysctls is provided at the end
of this patchset.
Two relativistic hash tables are used: one for IOAM namespaces, the other for
IOAM schemas. A namespace can only have a single active schema and a schema
can only be attached to a single namespace (1:1 relationship).
[1] https://tools.ietf.org/html/draft-ietf-ippm-ioam-ipv6-options
[2] https://tools.ietf.org/html/draft-ietf-ippm-ioam-data
[3] https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml#ipv6-parameters-2
Signed-off-by: Justin Iurman <justin.iurman@uliege.be>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-07-20 19:42:57 +00:00
|
|
|
u32 ioam6_id;
|
|
|
|
|
u64 ioam6_id_wide;
|
2018-10-12 03:17:21 +00:00
|
|
|
bool skip_notify_on_dev_down;
|
2021-03-31 17:52:12 +00:00
|
|
|
u8 fib_notify_on_flag_change;
|
2008-01-10 10:53:43 +00:00
|
|
|
};
|
|
|
|
|
|
2008-01-10 10:49:06 +00:00
|
|
|
struct netns_ipv6 {
|
2021-03-31 17:52:13 +00:00
|
|
|
/* Keep ip6_dst_ops at the beginning of netns_sysctl_ipv6 */
|
|
|
|
|
struct dst_ops ip6_dst_ops;
|
|
|
|
|
|
2008-01-10 10:53:43 +00:00
|
|
|
struct netns_sysctl_ipv6 sysctl;
|
2008-01-11 01:42:55 +00:00
|
|
|
struct ipv6_devconf *devconf_all;
|
|
|
|
|
struct ipv6_devconf *devconf_dflt;
|
2012-06-08 01:20:41 +00:00
|
|
|
struct inet_peer_base *peers;
|
2019-05-24 16:03:39 +00:00
|
|
|
struct fqdir *fqdir;
|
2018-04-18 00:33:26 +00:00
|
|
|
struct fib6_info *fib6_null_entry;
|
2018-04-18 00:33:18 +00:00
|
|
|
struct rt6_info *ip6_null_entry;
|
2008-03-04 07:34:17 +00:00
|
|
|
struct rt6_statistics *rt6_stats;
|
2008-07-22 21:33:45 +00:00
|
|
|
struct timer_list ip6_fib_timer;
|
2008-03-04 07:25:27 +00:00
|
|
|
struct hlist_head *fib_table_hash;
|
|
|
|
|
struct fib6_table *fib6_main_tbl;
|
2016-03-08 13:44:35 +00:00
|
|
|
struct list_head fib6_walkers;
|
|
|
|
|
rwlock_t fib6_walker_lock;
|
2016-03-08 13:44:45 +00:00
|
|
|
spinlock_t fib6_gc_lock;
|
2008-03-04 21:49:47 +00:00
|
|
|
unsigned int ip6_rt_gc_expire;
|
|
|
|
|
unsigned long ip6_rt_last_gc;
|
2008-03-04 07:25:27 +00:00
|
|
|
#ifdef CONFIG_IPV6_MULTIPLE_TABLES
|
2018-03-01 03:43:22 +00:00
|
|
|
unsigned int fib6_rules_require_fldissect;
|
|
|
|
|
bool fib6_has_custom_rules;
|
2019-11-20 12:47:34 +00:00
|
|
|
#ifdef CONFIG_IPV6_SUBTREES
|
|
|
|
|
unsigned int fib6_routes_require_src;
|
|
|
|
|
#endif
|
2008-03-04 21:48:30 +00:00
|
|
|
struct rt6_info *ip6_prohibit_entry;
|
|
|
|
|
struct rt6_info *ip6_blk_hole_entry;
|
2008-03-04 07:25:27 +00:00
|
|
|
struct fib6_table *fib6_local_tbl;
|
2008-03-04 07:33:08 +00:00
|
|
|
struct fib_rules_ops *fib6_rules_ops;
|
2008-01-31 12:04:13 +00:00
|
|
|
#endif
|
2019-02-23 07:28:28 +00:00
|
|
|
struct sock * __percpu *icmp_sk;
|
2008-03-07 19:15:34 +00:00
|
|
|
struct sock *ndisc_sk;
|
2008-03-07 19:16:02 +00:00
|
|
|
struct sock *tcp_sk;
|
2008-03-07 19:16:55 +00:00
|
|
|
struct sock *igmp_sk;
|
2015-02-25 17:58:35 +00:00
|
|
|
struct sock *mc_autojoin_sk;
|
2008-12-11 00:07:08 +00:00
|
|
|
#ifdef CONFIG_IPV6_MROUTE
|
ipv6: ip6mr: support multiple tables
This patch adds support for multiple independant multicast routing instances,
named "tables".
Userspace multicast routing daemons can bind to a specific table instance by
issuing a setsockopt call using a new option MRT6_TABLE. The table number is
stored in the raw socket data and affects all following ip6mr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT6_TABLE_DFLT)
is created with a default routing rule pointing to it. Newly created pim6reg
devices have the table number appended ("pim6regX"), with the exception of
devices created in the default table, which are named just "pim6reg" for
compatibility reasons.
Packets are directed to a specific table instance using routing rules,
similar to how regular routing rules work. Currently iif, oif and mark
are supported as keys, source and destination addresses could be supported
additionally.
Example usage:
- bind pimd/xorp/... to a specific table:
uint32_t table = 123;
setsockopt(fd, SOL_IPV6, MRT6_TABLE, &table, sizeof(table));
- create routing rules directing packets to the new table:
# ip -6 mrule add iif eth0 lookup 123
# ip -6 mrule add oif eth0 lookup 123
Signed-off-by: Patrick McHardy <kaber@trash.net>
2010-05-11 12:40:55 +00:00
|
|
|
#ifndef CONFIG_IPV6_MROUTE_MULTIPLE_TABLES
|
2018-02-28 21:29:32 +00:00
|
|
|
struct mr_table *mrt6;
|
ipv6: ip6mr: support multiple tables
This patch adds support for multiple independant multicast routing instances,
named "tables".
Userspace multicast routing daemons can bind to a specific table instance by
issuing a setsockopt call using a new option MRT6_TABLE. The table number is
stored in the raw socket data and affects all following ip6mr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT6_TABLE_DFLT)
is created with a default routing rule pointing to it. Newly created pim6reg
devices have the table number appended ("pim6regX"), with the exception of
devices created in the default table, which are named just "pim6reg" for
compatibility reasons.
Packets are directed to a specific table instance using routing rules,
similar to how regular routing rules work. Currently iif, oif and mark
are supported as keys, source and destination addresses could be supported
additionally.
Example usage:
- bind pimd/xorp/... to a specific table:
uint32_t table = 123;
setsockopt(fd, SOL_IPV6, MRT6_TABLE, &table, sizeof(table));
- create routing rules directing packets to the new table:
# ip -6 mrule add iif eth0 lookup 123
# ip -6 mrule add oif eth0 lookup 123
Signed-off-by: Patrick McHardy <kaber@trash.net>
2010-05-11 12:40:55 +00:00
|
|
|
#else
|
|
|
|
|
struct list_head mr6_tables;
|
|
|
|
|
struct fib_rules_ops *mr6_rules_ops;
|
|
|
|
|
#endif
|
2008-12-11 00:07:08 +00:00
|
|
|
#endif
|
2013-03-22 06:28:43 +00:00
|
|
|
atomic_t dev_addr_genid;
|
2014-10-06 17:58:37 +00:00
|
|
|
atomic_t fib6_sernum;
|
2016-11-08 13:57:40 +00:00
|
|
|
struct seg6_pernet_data *seg6_data;
|
2017-08-03 11:28:16 +00:00
|
|
|
struct fib_notifier_ops *notifier_ops;
|
2018-03-26 12:01:34 +00:00
|
|
|
struct fib_notifier_ops *ip6mr_notifier_ops;
|
|
|
|
|
unsigned int ipmr_seq; /* protected by rtnl_mutex */
|
2017-09-19 23:27:06 +00:00
|
|
|
struct {
|
|
|
|
|
struct hlist_head head;
|
|
|
|
|
spinlock_t lock;
|
|
|
|
|
u32 seq;
|
|
|
|
|
} ip6addrlbl_table;
|
ipv6: ioam: Data plane support for Pre-allocated Trace
Implement support for processing the IOAM Pre-allocated Trace with IPv6,
see [1] and [2]. Introduce a new IPv6 Hop-by-Hop TLV option, see IANA [3].
A new per-interface sysctl is introduced. The value is a boolean to accept (=1)
or ignore (=0, by default) IPv6 IOAM options on ingress for an interface:
- net.ipv6.conf.XXX.ioam6_enabled
Two other sysctls are introduced to define IOAM IDs, represented by an integer.
They are respectively per-namespace and per-interface:
- net.ipv6.ioam6_id
- net.ipv6.conf.XXX.ioam6_id
The value of the first one represents the IOAM ID of the node itself (u32; max
and default value = U32_MAX>>8, due to hop limit concatenation) while the other
represents the IOAM ID of an interface (u16; max and default value = U16_MAX).
Each "ioam6_id" sysctl has a "_wide" equivalent:
- net.ipv6.ioam6_id_wide
- net.ipv6.conf.XXX.ioam6_id_wide
The value of the first one represents the wide IOAM ID of the node itself (u64;
max and default value = U64_MAX>>8, due to hop limit concatenation) while the
other represents the wide IOAM ID of an interface (u32; max and default value
= U32_MAX).
The use of short and wide equivalents is not exclusive, a deployment could
choose to leverage both. For example, net.ipv6.conf.XXX.ioam6_id (short format)
could be an identifier for a physical interface, whereas
net.ipv6.conf.XXX.ioam6_id_wide (wide format) could be an identifier for a
logical sub-interface. Documentation about new sysctls is provided at the end
of this patchset.
Two relativistic hash tables are used: one for IOAM namespaces, the other for
IOAM schemas. A namespace can only have a single active schema and a schema
can only be attached to a single namespace (1:1 relationship).
[1] https://tools.ietf.org/html/draft-ietf-ippm-ioam-ipv6-options
[2] https://tools.ietf.org/html/draft-ietf-ippm-ioam-data
[3] https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml#ipv6-parameters-2
Signed-off-by: Justin Iurman <justin.iurman@uliege.be>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-07-20 19:42:57 +00:00
|
|
|
struct ioam6_pernet_data *ioam6_data;
|
2008-01-10 10:49:06 +00:00
|
|
|
};
|
2012-09-18 16:50:08 +00:00
|
|
|
|
|
|
|
|
#if IS_ENABLED(CONFIG_NF_DEFRAG_IPV6)
|
|
|
|
|
struct netns_nf_frag {
|
2019-05-24 16:03:39 +00:00
|
|
|
struct fqdir *fqdir;
|
2012-09-18 16:50:08 +00:00
|
|
|
};
|
|
|
|
|
#endif
|
|
|
|
|
|
2008-01-10 10:49:06 +00:00
|
|
|
#endif
|
