Changes in Makefile

4954f17d - net/tcp: Introduce TCP_AO setsockopt()s

Mon, 23 Oct 2023 19:21:55 +0000

net/tcp: Introduce TCP_AO setsockopt()sAdd 3 setsockopt()s:1. TCP_AO_ADD_KEY to add a new Master Key Tuple (MKT) on a socket2. TCP_AO_DEL_KEY to delete present MKT from a socket3. TCP_AO_INFO to change flags, Current_key/RNext_key on a TCP-AO skUserspace has to introduce keys on every socket it wants to use TCP-AOoption on, similarly to TCP_MD5SIG/TCP_MD5SIG_EXT.RFC5925 prohibits definition of MKTs that would match the same peer,so do sanity checks on the data provided by userspace. Be asconservative as possible, including refusal of defining MKT onan established connection with no AO, removing the key in-use and etc.(1) and (2) are to be used by userspace key manager to add/remove keys.(3) main purpose is to set RNext_key, which (as prescribed by RFC5925)is the KeyID that will be requested in TCP-AO header from the peer tosign their segments with.At this moment the life of ao_info ends in tcp_v4_destroy_sock().Co-developed-by: Francesco Ruggeri Signed-off-by: Francesco Ruggeri Co-developed-by: Salam Noureddine Signed-off-by: Salam Noureddine Signed-off-by: Dmitry Safonov Acked-by: David Ahern Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

1817750b - net: ipv6: use ipv6-y directly instead of ipv6-objs

Mon, 27 Sep 2021 14:28:40 +0000

net: ipv6: use ipv6-y directly instead of ipv6-objsKbuild supports -y as well as -objs.This simplifies the Makefile.Signed-off-by: Masahiro Yamada Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

9a121384 - net: ipv6: squash $(ipv6-offload) in Makefile

Mon, 27 Sep 2021 14:28:39 +0000

net: ipv6: squash $(ipv6-offload) in MakefileAssign the objects directly to obj-$(CONFIG_INET).Signed-off-by: Masahiro Yamada Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

3edede08 - ipv6: ioam: Support for IOAM injection with lwtunnels

Tue, 20 Jul 2021 19:42:59 +0000

ipv6: ioam: Support for IOAM injection with lwtunnelsAdd support for the IOAM inline insertion (only for the host-to-host use case)which is per-route configured with lightweight tunnels. The target is iproute2and the patch is ready. It will be posted as soon as this patchset is merged.Here is an overview:$ ip -6 ro ad fc00::1/128 encap ioam6 trace type 0x800000 ns 1 size 12 dev eth0This example configures an IOAM Pre-allocated Trace option attached to thefc00::1/128 prefix. The IOAM namespace (ns) is 1, the size of the pre-allocatedtrace data block is 12 octets (size) and only the first IOAM data (bit 0:hop_limit + node id) is included in the trace (type) represented as a bitfield.The reason why the in-transit (IPv6-in-IPv6 encapsulation) use case is notimplemented is explained on the patchset cover.Signed-off-by: Justin Iurman Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

9ee11f0f - ipv6: ioam: Data plane support for Pre-allocated Trace

Tue, 20 Jul 2021 19:42:57 +0000

ipv6: ioam: Data plane support for Pre-allocated TraceImplement 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_enabledTwo 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_idThe value of the first one represents the IOAM ID of the node itself (u32; maxand default value = U32_MAX>>8, due to hop limit concatenation) while the otherrepresents 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_wideThe 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 theother 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 couldchoose to leverage both. For example, net.ipv6.conf.XXX.ioam6_id (short format)could be an identifier for a physical interface, whereasnet.ipv6.conf.XXX.ioam6_id_wide (wide format) could be an identifier for alogical sub-interface. Documentation about new sysctls is provided at the endof this patchset.Two relativistic hash tables are used: one for IOAM namespaces, the other forIOAM schemas. A namespace can only have a single active schema and a schemacan 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-2Signed-off-by: Justin Iurman Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

a7a29f9c - net: ipv6: add rpl sr tunnel

Fri, 27 Mar 2020 22:00:22 +0000

net: ipv6: add rpl sr tunnelThis patch adds functionality to configure routes for RPL source routingfunctionality. There is no IPIP functionality yet implemented which canbe added later when the cases when to use IPv6 encapuslation comes moreclear.Signed-off-by: Alexander Aring Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

8610c7c6 - net: ipv6: add support for rpl sr exthdr

Fri, 27 Mar 2020 22:00:20 +0000

net: ipv6: add support for rpl sr exthdrThis patch adds rpl source routing receive handling. Everything worksonly if sysconf "rpl_seg_enabled" and source routing is enabled. Mostlythe same behaviour as IPv6 segmentation routing. To handle compressionand uncompression a rpl.c file is created which contains the necessaryfunctionality. The receive handling will also care about IPv6encapsulated so far it's specified as possible nexthdr in RFC 6554.Signed-off-by: Alexander Aring Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

4c145dce - xfrm: make xfrm modes builtin

Fri, 29 Mar 2019 20:16:31 +0000

xfrm: make xfrm modes builtinafter previous changes, xfrm_mode contains no function pointers anymoreand all modules defining such struct contain no code except an init/exitfunctions to register the xfrm_mode struct with the xfrm core.Just place the xfrm modes core and remove the modules,the run-time xfrm_mode register/unregister functionality is removed.Before: text data bss dec filename 7523 200 2364 10087 net/xfrm/xfrm_input.o 40003 628 440 41071 net/xfrm/xfrm_state.o15730338 6937080 4046908 26714326 vmlinux 7389 200 2364 9953 net/xfrm/xfrm_input.o 40574 656 440 41670 net/xfrm/xfrm_state.o15730084 6937068 4046908 26714060 vmlinuxThe xfrm*_mode_{transport,tunnel,beet} modules are gone.v2: replace CONFIG_INET6_XFRM_MODE_* IS_ENABLED guards with CONFIG_IPV6 ones rather than removing them.Signed-off-by: Florian Westphal Reviewed-by: Sabrina Dubroca Signed-off-by: Steffen Klassert List of files: /linux-6.15/net/ipv6/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense 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 bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe 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 caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase 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 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately 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 licenseidentifiers 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 thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion 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 correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/net/ipv6/Makefile

d1df6fd8 - ipv6: sr: define core operations for seg6local lightweight tunnel

Sat, 05 Aug 2017 10:38:26 +0000

ipv6: sr: define core operations for seg6local lightweight tunnelThis patch implements a new type of lightweight tunnel named seg6local.A seg6local lwt is defined by a type of action and a set of parameters.The action represents the operation to perform on the packets matching thelwt's route, and is not necessarily an encapsulation. The set of parametersare arguments for the processing function.Each action is defined in a struct seg6_action_desc withinseg6_action_table[]. This structure contains the action, mandatoryattributes, the processing function, and a static headroom size required bythe action. The mandatory attributes are encoded as a bitmask field. Thestatic headroom is set to a non-zero value when the processing functionalways add a constant number of bytes to the skb (e.g. the header size forencapsulations).To facilitate rtnetlink-related operations such as parsing, fill_encap,and cmp_encap, each type of action parameter is associated to threefunction pointers, in seg6_action_params[].All actions defined in seg6_local.h are detailed in [1].[1] https://tools.ietf.org/html/draft-filsfils-spring-srv6-network-programming-01Signed-off-by: David Lebrun Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

16ab6d7d - ipv6: fib: Add FIB notifiers callbacks

Thu, 03 Aug 2017 11:28:16 +0000

ipv6: fib: Add FIB notifiers callbacksWe're about to add IPv6 FIB offload support, so implement the necessarycallbacks in IPv6 code, which will later allow us to add routes andrules notifications.Signed-off-by: Ido Schimmel Signed-off-by: Jiri Pirko Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

7785bba2 - esp: Add a software GRO codepath

Wed, 15 Feb 2017 08:40:00 +0000

esp: Add a software GRO codepathThis patch adds GRO ifrastructure and callbacks for ESP onipv4 and ipv6.In case the GRO layer detects an ESP packet, theesp{4,6}_gro_receive() function does a xfrm state lookupand calls the xfrm input layer if it finds a matching state.The packet will be decapsulated and reinjected it into layer 2.Signed-off-by: Steffen Klassert List of files: /linux-6.15/net/ipv6/Makefile

46738b13 - ipv6: sr: add option to control lwtunnel support

Tue, 15 Nov 2016 15:14:04 +0000

ipv6: sr: add option to control lwtunnel supportThis patch adds a new option CONFIG_IPV6_SEG6_LWTUNNEL to enable/disablesupport of encapsulation with the lightweight tunnels. When this optionis enabled, CONFIG_LWTUNNEL is automatically selected.Fix commit 6c8702c60b88 ("ipv6: sr: add support for SRH encapsulation and injection with lwtunnels")Without a proper option to control lwtunnel support for SR-IPv6, ifCONFIG_LWTUNNEL=n then the IPv6 initialization fails as a consequenceof seg6_iptunnel_init() failure with EOPNOTSUPP:NET: Registered protocol family 10IPv6: Attempt to unregister permanent protocol 6IPv6: Attempt to unregister permanent protocol 136IPv6: Attempt to unregister permanent protocol 17NET: Unregistered protocol family 10Tested (compiling, booting, and loading ipv6 module when relevant)with possible combinations of CONFIG_IPV6={y,m,n},CONFIG_IPV6_SEG6_LWTUNNEL={y,n} and CONFIG_LWTUNNEL={y,n}.Reported-by: Lorenzo Colitti Suggested-by: Roopa Prabhu Signed-off-by: David Lebrun Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

bf355b8d - ipv6: sr: add core files for SR HMAC support

Tue, 08 Nov 2016 13:57:42 +0000

ipv6: sr: add core files for SR HMAC supportThis patch adds the necessary functions to compute and check the HMAC signatureof an SR-enabled packet. Two HMAC algorithms are supported: hmac(sha1) andhmac(sha256).In order to avoid dynamic memory allocation for each HMAC computation,a per-cpu ring buffer is allocated for this purpose.A new per-interface sysctl called seg6_require_hmac is added, allowing auser-defined policy for processing HMAC-signed SR-enabled packets.A value of -1 means that the HMAC field will always be ignored.A value of 0 means that if an HMAC field is present, its validity willbe enforced (the packet is dropped is the signature is incorrect).Finally, a value of 1 means that any SR-enabled packet that does notcontain an HMAC signature or whose signature is incorrect will be dropped.Signed-off-by: David Lebrun Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

6c8702c6 - ipv6: sr: add support for SRH encapsulation and injection with lwtunnels

Tue, 08 Nov 2016 13:57:41 +0000

ipv6: sr: add support for SRH encapsulation and injection with lwtunnelsThis patch creates a new type of interfaceless lightweight tunnel (SEG6),enabling the encapsulation and injection of SRH within locally emittedpackets and forwarded packets.>From a configuration viewpoint, a seg6 tunnel would be configured as follows: ip -6 ro ad fc00::1/128 encap seg6 mode encap segs fc42::1,fc42::2,fc42::3 dev eth0Any packet whose destination address is fc00::1 would thus be encapsulatedwithin an outer IPv6 header containing the SRH with three segments, and wouldactually be routed to the first segment of the list. If `mode inline' wasspecified instead of `mode encap', then the SRH would be directly insertedafter the IPv6 header without outer encapsulation.The inline mode is only available if CONFIG_IPV6_SEG6_INLINE is enabled. Thisfeature was made configurable because direct header insertion may breakseveral mechanisms such as PMTUD or IPSec AH.Signed-off-by: David Lebrun Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

915d7e5e - ipv6: sr: add code base for control plane support of SR-IPv6

Tue, 08 Nov 2016 13:57:40 +0000

ipv6: sr: add code base for control plane support of SR-IPv6This patch adds the necessary hooks and structures to provide supportfor SR-IPv6 control plane, essentially the Generic Netlink commandsthat will be used for userspace control over the Segment Routingkernel structures.The genetlink commands provide control over two different structures:tunnel source and HMAC data. The tunnel source is the source addressthat will be used by default when encapsulating packets into anouter IPv6 header + SRH. If the tunnel source is set to :: then anaddress of the outgoing interface will be selected as the source.The HMAC commands currently just return ENOTSUPP and will be implementedin a future patch.Signed-off-by: David Lebrun Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

cb72d382 - netlabel: Initial support for the CALIPSO netlink protocol.

Mon, 27 Jun 2016 19:02:46 +0000

netlabel: Initial support for the CALIPSO netlink protocol.CALIPSO is a packet labelling protocol for IPv6 which is very similarto CIPSO. It is specified in RFC 5570. Much of the code is based onthe current CIPSO code.This adds support for adding passthrough-type CALIPSO DOIs through theNLBL_CALIPSO_C_ADD command. It requires attributes: NLBL_CALIPSO_A_TYPE which must be CALIPSO_MAP_PASS. NLBL_CALIPSO_A_DOI.In passthrough mode the CALIPSO engine will map MLS secattr levelsand categories directly to the packet label.At this stage, the major difference between this and the CIPSOcode is that IPv6 may be compiled as a module. To allow forthis the CALIPSO functions are registered at module init time.Signed-off-by: Huw Davies Signed-off-by: Paul Moore List of files: /linux-6.15/net/ipv6/Makefile

95e4daa8 - fou: fix IPv6 Kconfig options

Tue, 31 May 2016 20:42:11 +0000

fou: fix IPv6 Kconfig optionsThe Kconfig options I added to work around broken compilation endedup screwing up things more, as I used the wrong symbol to controlcompilation of the file, resulting in IPv6 fou support to never be builtinto the kernel.Changing CONFIG_NET_FOU_IPV6_TUNNELS to CONFIG_IPV6_FOU fixes thatproblem, I had renamed the symbol in one location but not the other,and as the file is never being used by other kernel code, this did notlead to a build failure that I would have caught.After that fix, another issue with the same patch becomes obvious, as we'select INET6_TUNNEL', which is related to IPV6_TUNNEL, but not the same,and this can still cause the original build failure when IPV6_TUNNEL isnot built-in but IPV6_FOU is. The fix is equally trivial, we just needto select the right symbol.I have successfully build 350 randconfig kernels with this patchand verified that the driver is now being built.Signed-off-by: Arnd Bergmann Reported-by: Valentin Rothberg Fixes: fabb13db448e ("fou: add Kconfig options for IPv6 support")Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

fabb13db - fou: add Kconfig options for IPv6 support

Wed, 25 May 2016 14:50:46 +0000

fou: add Kconfig options for IPv6 supportA previous patch added the fou6.ko module, but that failed to linkin a couple of configurations:net/built-in.o: In function `ip6_tnl_encap_add_fou_ops':net/ipv6/fou6.c:88: undefined reference to `ip6_tnl_encap_add_ops'net/ipv6/fou6.c:94: undefined reference to `ip6_tnl_encap_add_ops'net/ipv6/fou6.c:97: undefined reference to `ip6_tnl_encap_del_ops'net/built-in.o: In function `ip6_tnl_encap_del_fou_ops':net/ipv6/fou6.c:106: undefined reference to `ip6_tnl_encap_del_ops'net/ipv6/fou6.c:107: undefined reference to `ip6_tnl_encap_del_ops'If CONFIG_IPV6=m, ip6_tnl_encap_add_ops/ip6_tnl_encap_del_opsare in a module, but fou6.c can still be built-in, and thatobviously fails to link.Also, if CONFIG_IPV6=y, but CONFIG_IPV6_TUNNEL=m orCONFIG_IPV6_TUNNEL=n, the same problem happens for a differentreason.This adds two new silent Kconfig symbols to work around bothproblems:- CONFIG_IPV6_FOU is now always set to 'm' if either CONFIG_NET_FOU=m or CONFIG_IPV6=m- CONFIG_IPV6_FOU_TUNNEL is set implicitly when IPV6_FOU is enabled and NET_FOU_IP_TUNNELS is also turned out, and it will ensure that CONFIG_IPV6_TUNNEL is also available.The options could be made user-visible as well, to give additionalroom for configuration, but it seems easier not to bother userswith more choice here.Signed-off-by: Arnd Bergmann Fixes: aa3463d65e7b ("fou: Add encap ops for IPv6 tunnels")Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile

aa3463d6 - fou: Add encap ops for IPv6 tunnels

Wed, 18 May 2016 16:06:18 +0000

fou: Add encap ops for IPv6 tunnelsThis patch add a new fou6 module that provides encapsulationoperations for IPv6.Signed-off-by: Tom Herbert Signed-off-by: David S. Miller List of files: /linux-6.15/net/ipv6/Makefile