Changes in Makefile

3f117d6f - l2tp: add tracepoint infrastructure to core

Sat, 22 Aug 2020 14:59:04 +0000

l2tp: add tracepoint infrastructure to coreThe l2tp subsystem doesn't currently make use of tracepoints.As a starting point for adding tracepoints, add skeleton infrastructurefor defining tracepoints for the subsystem, and for having them buildappropriately whether compiled into the kernel or built as a module.Signed-off-by: Tom Parkin Signed-off-by: David S. Miller List of files: /linux-6.15/net/l2tp/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/l2tp/Makefile

a32e0eec - l2tp: introduce L2TPv3 IP encapsulation support for IPv6

Sun, 29 Apr 2012 21:48:54 +0000

l2tp: introduce L2TPv3 IP encapsulation support for IPv6L2TPv3 defines an IP encapsulation packet format where data is carrieddirectly over IP (no UDP). The kernel already has support for L2TP IPencapsulation over IPv4 (l2tp_ip). This patch introduces support forL2TP IP encapsulation over IPv6.The implementation is derived from ipv6/raw and ipv4/l2tp_ip.Signed-off-by: Chris Elston Signed-off-by: James Chapman Signed-off-by: David S. Miller List of files: /linux-6.15/net/l2tp/Makefile

0ad66140 - l2tp: Add debugfs files for dumping l2tp debug info

Fri, 02 Apr 2010 06:19:33 +0000

l2tp: Add debugfs files for dumping l2tp debug infoThe existing pppol2tp driver exports debug info to/proc/net/pppol2tp. Rather than adding info to that file for the newfunctionality added in this patch series, we add new files in debugfs,leaving the old /proc file for backwards compatibility (L2TPv2 only).Currently only one file is provided: l2tp/tunnels, which listsinternal debug info for all l2tp tunnels and sessions. More files maybe added later. The info is for debug and problem analysis only -userspace apps should use netlink to obtain status about l2tp tunnelsand sessions.Although debugfs does not support net namespaces, the tunnels andsessions dumped in l2tp/tunnels are only those in the net namespace ofthe process reading the file.Signed-off-by: James Chapman Signed-off-by: David S. Miller List of files: /linux-6.15/net/l2tp/Makefile

d9e31d17 - l2tp: Add L2TP ethernet pseudowire support

Fri, 02 Apr 2010 06:19:26 +0000

l2tp: Add L2TP ethernet pseudowire supportThis driver presents a regular net_device for each L2TP ethernetpseudowire instance. These interfaces are named l2tpethN by default,though userspace can specify an alternative name when the L2TPsession is created, if preferred. When the pseudowire is established,regular Linux networking utilities may be used to configure theinterface, i.e. give it IP address info or add it to a bridge. Anydata passed over the interface is carried over an L2TP tunnel.Signed-off-by: James Chapman Reviewed-by: Randy Dunlap Signed-off-by: David S. Miller List of files: /linux-6.15/net/l2tp/Makefile

309795f4 - l2tp: Add netlink control API for L2TP

Fri, 02 Apr 2010 06:19:10 +0000

l2tp: Add netlink control API for L2TPIn L2TPv3, we need to create/delete/modify/query L2TP tunnel andsession contexts. The number of parameters is significant. So let'suse netlink. Userspace uses this API to control L2TP tunnel/sessioncontexts in the kernel.The previous pppol2tp driver was managed using [gs]etsockopt(). ThisAPI is retained for backwards compatibility. Unlike L2TPv2 whichcarries only PPP frames, L2TPv3 can carry raw ethernet frames or otherframe types and these do not always have an associated socketfamily. Therefore, we need a way to use L2TP sessions that doesn'trequire a socket type for each supported frame type. Hence netlink isused.Signed-off-by: James Chapman Reviewed-by: Randy Dunlap Signed-off-by: David S. Miller List of files: /linux-6.15/net/l2tp/Makefile

0d76751f - l2tp: Add L2TPv3 IP encapsulation (no UDP) support

Fri, 02 Apr 2010 06:19:00 +0000

l2tp: Add L2TPv3 IP encapsulation (no UDP) supportThis patch adds a new L2TPIP socket family and modifies the core tohandle the case where there is no UDP header in the L2TPpacket. L2TP/IP uses IP protocol 115. Since L2TP/UDP and L2TP/IPpackets differ in layout, the datapath packet handling code needschanges too. Userspace uses an L2TPIP socket instead of a UDP socketwhen IP encapsulation is required.We can't use raw sockets for this because the semantics of raw socketsdon't lend themselves to the socket-per-tunnel model - we need toSigned-off-by: David S. Miller List of files: /linux-6.15/net/l2tp/Makefile

fd558d18 - l2tp: Split pppol2tp patch into separate l2tp and ppp parts

Fri, 02 Apr 2010 06:18:33 +0000

l2tp: Split pppol2tp patch into separate l2tp and ppp partsThis patch splits the pppol2tp driver into separate L2TP and PPP partsto prepare for L2TPv3 support. In L2TPv3, protocols other than PPP canbe carried, so this split creates a common L2TP core that will handlethe common L2TP bits which protocol support modules such as PPP willuse.Note that the existing pppol2tp module is split into l2tp_core andl2tp_ppp by this change.There are no feature changes here. Internally, however, there aresignificant changes, mostly to handle the separation of PPP-specificdata from the L2TP session and to provide hooks in the core formodules like PPP to access.Signed-off-by: James Chapman Reviewed-by: Randy Dunlap Signed-off-by: David S. Miller List of files: /linux-6.15/net/l2tp/Makefile

21b4aaa1 - l2tp: Relocate pppol2tp driver to new net/l2tp directory

Fri, 02 Apr 2010 06:18:28 +0000

l2tp: Relocate pppol2tp driver to new net/l2tp directoryThis patch moves the existing pppol2tp driver from drivers/net into anew net/l2tp directory, which is where the upcoming L2TPv3 code willlive. The existing CONFIG_PPPOL2TP config option is left in itscurrent place to avoid "make oldconfig" issues when an existingpppol2tp user takes this change. (This is the same approach used forthe pppoatm driver, which moved to net/atm.)There are no code changes. The existing drivers/net/pppol2tp.c issimply moved to net/l2tp.Signed-off-by: James Chapman Reviewed-by: Randy Dunlap Signed-off-by: David S. Miller List of files: /linux-6.15/net/l2tp/Makefile