Changes in Makefile

9a28ac17 - lockd: add netlink control interface

Wed, 08 Jan 2025 21:00:15 +0000

lockd: add netlink control interfaceThe legacy rpc.nfsd tool will set the nlm_grace_period if the NFSv4grace period is set. nfsdctl is missing this functionality, so add a newnetlink control interface for lockd that it can use. For now, it onlyallows setting the grace period, and the tcp and udp listener ports.lockd currently uses module parameters and sysctls for configuration, soall of its settings are global. With this change, lockd now tracks thesevalues on a per-net-ns basis. It will only fall back to using the globalvalues if any of them are 0.Finally, as a backward compatibility measure, if updating the nlmsettings in the init_net namespace, also update the legacy globalvalues to match.Link: https://issues.redhat.com/browse/RHEL-71698Signed-off-by: Jeff Layton Signed-off-by: Chuck Lever List of files: /linux-6.15/fs/lockd/Makefile

e5d85ec5 - lockd: Use -y instead of -objs in Makefile

Wed, 08 May 2024 15:19:38 +0000

lockd: Use *-y instead of *-objs in Makefile*-objs suffix is reserved rather for (user-space) host programs whileusually *-y suffix is used for kernel drivers (although *-objs worksfor that purpose for now).Let's correct the old usages of *-objs in Makefiles.Signed-off-by: Andy Shevchenko Reviewed-by: Benjamin Coddington Signed-off-by: Chuck Lever List of files: /linux-6.15/fs/lockd/Makefile

2f90e18f - lockd: add some client-side tracepoints

Fri, 03 Mar 2023 12:16:03 +0000

lockd: add some client-side tracepointsSigned-off-by: Jeff Layton Signed-off-by: Chuck Lever List of files: /linux-6.15/fs/lockd/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/fs/lockd/Makefile

d68e3c4a - lockd: add a /proc/fs/lockd/nlm_end_grace file

Fri, 12 Sep 2014 20:40:20 +0000

lockd: add a /proc/fs/lockd/nlm_end_grace fileAdd a new procfile that will allow a (privileged) userland process toend the NLM grace period early. The basic idea here will be to havesm-notify write to this file, if it sent out no NOTIFY requests whenit runs. In that situation, we can generally expect that there will beno reclaim requests so the grace period can be lifted early.Signed-off-by: Jeff Layton List of files: /linux-6.15/fs/lockd/Makefile

f7790029 - lockd: move lockd's grace period handling into its own module

Fri, 12 Sep 2014 20:40:20 +0000

lockd: move lockd's grace period handling into its own moduleCurrently, all of the grace period handling is part of lockd. Eventuallythough we'd like to be able to build v4-only servers, at which pointwe'll need to put all of this elsewhere.Move the code itself into fs/nfs_common and have it build a grace.komodule. Then, rejigger the Kconfig options so that both nfsd and lockdenable it automatically.Signed-off-by: Jeff Layton List of files: /linux-6.15/fs/lockd/Makefile

3460f29a - lockd: Introduce new-style XDR functions for NLMv4

Tue, 14 Dec 2010 14:57:12 +0000

lockd: Introduce new-style XDR functions for NLMv4We'd like to prevent local buffer overflows caused by malicious orbroken servers. New xdr_stream style decoders can do that.For efficiency, we also want to be able to pass xdr_streams fromcall_encode() to all XDR encoding functions, rather than buildingan xdr_stream in every XDR encoding function in the kernel.Same idea as the NLM v3 XDR overhaul.Signed-off-by: Chuck Lever Tested-by: J. Bruce Fields Signed-off-by: Trond Myklebust List of files: /linux-6.15/fs/lockd/Makefile

2b061f9e - lockd: Introduce new-style XDR functions for NLMv3

Tue, 14 Dec 2010 14:55:40 +0000

lockd: Introduce new-style XDR functions for NLMv3We'd like to prevent local buffer overflows caused by malicious orbroken servers. New xdr_stream style decoders can do that.For efficiency, we also eventually want to be able to pass xdr_streamsfrom call_encode() and call_decode() to all XDR encoding functions,rather than building an xdr_stream in every XDR encoding and decodingfunction in the kernel.To do all of this, rewrite the XDR encoding and decoding functions infs/lockd/xdr.c to use xdr_streams. This makes them more or lessincompatible with server-side XDR helper functions, so break them outinto a separate source file.Static helper functions are left without the "inline" directive. Thisallows the compiler to choose automatically how to optimize these forsize or speed.SHARE-related functionality doesn't seem to be used, as thosefunctions are hiding behind a #define that isn't set anywhere that Ican find. And, they've been in there forever (at least as far back asthe kernel's git history goes), yet remain unused. Let's take theopportunity to bin them. It should be easy enough for someone tointroduce proper XDR functions if at some point SHARE-related NLMfunctionality is desired.Signed-off-by: Chuck Lever Tested-by: J. Bruce Fields Signed-off-by: Trond Myklebust List of files: /linux-6.15/fs/lockd/Makefile

af558e33 - nfsd: common grace period control

Thu, 06 Sep 2007 16:34:25 +0000

nfsd: common grace period controlRewrite grace period code to unify management of grace period acrosslockd and nfsd. The current code has lockd and nfsd cooperate tocompute a grace period which is satisfactory to them both, and thenindividually enforce it. This creates a slight race condition, sincethe enforcement is not coordinated. It's also more complicated thannecessary.Here instead we have lockd and nfsd each inform common code when theyenter the grace period, and when they're ready to leave the graceperiod, and allow normal locking only after both of them are ready toleave.We also expect the locks_start_grace()/locks_end_grace() interface hereto be simpler to build on for future cluster/high-availability work,which may require (for example) putting individual filesystems intograce, or enforcing grace periods across multiple cluster nodes.Signed-off-by: J. Bruce Fields List of files: /linux-6.15/fs/lockd/Makefile

1da177e4 - Linux-2.6.12-rc2

Sat, 16 Apr 2005 22:20:36 +0000

Linux-2.6.12-rc2Initial git repository build. I'm not bothering with the full history,even though we have it. We can create a separate "historical" gitarchive of that later if we want to, and in the meantime it's about3.2GB when imported into git - space that would just make the earlygit days unnecessarily complicated, when we don't have a lot of goodinfrastructure for it.Let it rip! List of files: /linux-6.15/fs/lockd/Makefile