Changes in Makefile

8ec90bfd - selftests: mount: add nosymfollow tests

Thu, 27 Aug 2020 17:09:47 +0000

selftests: mount: add nosymfollow testsAdd tests for the new 'nosymfollow' mount option. We test to make surethat symlink traversal fails with ELOOP when 'nosymfollow' is set, butthat readlink(2) and realpath(3) still work as expected. We also verifythat statfs(2) correctly returns ST_NOSYMFOLLOW when we are mounted withthe 'nosymfollow' option.Signed-off-by: Ross Zwisler Signed-off-by: Al Viro List of files: /linux-6.15/tools/testing/selftests/mount/Makefile

addee42a - selftests: mount: delete RUN_TESTS and EMIT_TESTS overrides

Wed, 02 May 2018 02:46:03 +0000

selftests: mount: delete RUN_TESTS and EMIT_TESTS overridesDelete RUN_TESTS and EMIT_TESTS overrides and use common defines inlib.mk. Add new run_tests.sh to do the dependency checks the customRUN_TESTS did. Common defines work with the run_tests.sh set as theTEST_PROGS and defining unprivileged-remount-test in TEST_GEN_FILES.Kselftest framework builds and installs TEST_GEN_FILES and doesn't runthem via RUN_TESTS and include it in EMIT_TESTS. With this change thenew run_tests.sh runs the test after checking dependencies.This change also adds Skip handling to return kselftest skip code whentest is skipped to clearly identify when the test is skipped instead ofreporting it as failed.Output with this change:TAP version 13selftests: mount: run_tests.sh========================================WARN: No /proc/self/uid_map exist, test skipped.not ok 1..1 selftests: mount: run_tests.sh [SKIP]Signed-off-by: Shuah Khan (Samsung OSG) Reviewed-by: Anders Roxell Signed-off-by: Shuah Khan (Samsung OSG) List of files: /linux-6.15/tools/testing/selftests/mount/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/tools/testing/selftests/mount/Makefile

7d758af2 - selftests: add default rules for c source file

Tue, 29 Nov 2016 11:55:49 +0000

selftests: add default rules for c source fileThere are difference rules for compiling c source file in differenttestcases. In order to enable KBUILD_OUTPUT support in later patch,this patch introduce the default rules in"tools/testing/selftest/lib.mk" and remove the existing rules in eachtestcase.Acked-by: Michael Ellerman Signed-off-by: Bamvor Jian Zhang Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mount/Makefile

88baa78d - selftests: remove duplicated all and clean target

Tue, 29 Nov 2016 11:55:47 +0000

selftests: remove duplicated all and clean targetCurrently, kselftest use TEST_PROGS, TEST_PROGS_EXTENDED, TEST_FILES toindicate the test program, extended test program and test files. It iseasy to understand the purpose of these files. But mix of compiled anduncompiled files lead to duplicated "all" and "clean" targets.In order to remove the duplicated targets, introduce TEST_GEN_PROGS,TEST_GEN_PROGS_EXTENDED, TEST_GEN_FILES to indicate the compiledobjects.Also, the later patch will make use of TEST_GEN_XXX to redirect thesefiles to output directory indicated by KBUILD_OUTPUT or O.And add this changes to "Contributing new tests(details)" ofDocumentation/kselftest.txt.Signed-off-by: Bamvor Jian Zhang Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mount/Makefile

d0bd7f2a - selftests/mount: output WARN messages when mount test skipped

Fri, 03 Apr 2015 01:39:36 +0000

selftests/mount: output WARN messages when mount test skippedIf /proc/self/uid_map doesn't exist, mount test case exitswthout any warning. Fix it to print a warning that the testis skipped because /proc/self/uid_map doesn't exist.Signed-off-by: Zhang Zhen Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mount/Makefile

365ce999 - selftest/mount: enable cross compilation

Wed, 01 Apr 2015 23:20:17 +0000

selftest/mount: enable cross compilationUse the CC variable instead of hard coding gcc. Also clean up the compileroptions by creating a CFLAGS variable.Signed-off-by: Tyler Baker Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mount/Makefile

32dcfba6 - selftests: Add install target

Wed, 11 Mar 2015 04:06:00 +0000

selftests: Add install targetThis adds make install support to selftests. The basic usage is:$ cd tools/testing/selftests$ make installThat installs into tools/testing/selftests/install, which can then becopied where ever necessary.The install destination is also configurable using eg:$ INSTALL_PATH=/mnt/selftests make installThe implementation uses two targets in the child makefiles. The first"install" is expected to install all files into $(INSTALL_PATH).The second, "emit_tests", is expected to emit the test instructions (ie.bash script) on stdout. Separating this from install means the childmakefiles need no knowledge of the location of the test script.Signed-off-by: Michael Ellerman Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mount/Makefile

5e29a910 - selftests: Introduce minimal shared logic for running tests

Wed, 11 Mar 2015 04:05:59 +0000

selftests: Introduce minimal shared logic for running testsThis adds a Make include file which most selftests can then include toget the run_tests logic.On its own this has the advantage of some reduction in repetition, andalso means the pass/fail message is defined in fewer places.However the key advantage is it will allow us to implement install verysimply in a subsequent patch.The default implementation just executes each program in $(TEST_PROGS).We use a variable to hold the default implementation of $(RUN_TESTS)because that gives us a clean way to override it if necessary, ie. usingoverride. The mount, memory-hotplug and mqueue tests use that to providea different implementation.Tests are not run via /bin/bash, so if they are scripts they must beexecutable, we add a+x to several.Signed-off-by: Michael Ellerman Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mount/Makefile

db181ce0 - mnt: Add tests for unprivileged remount cases that have found to be faulty

Tue, 29 Jul 2014 22:50:44 +0000

mnt: Add tests for unprivileged remount cases that have found to be faultyKenton Varda discovered that by remounting aread-only bind mount read-only in a user namespace theMNT_LOCK_READONLY bit would be cleared, allowing an unprivileged userto the remount a read-only mount read-write.Upon review of the code in remount it was discovered that the code allowednosuid, noexec, and nodev to be cleared. It was also discovered thatthe code was allowing the per mount atime flags to be changed.The first naive patch to fix these issues contained the flaw that usingdefault atime settings when remounting a filesystem could be disallowed.To avoid this problems in the future add tests to ensure unprivilegedremounts are succeeding and failing at the appropriate times.Cc: stable@vger.kernel.orgAcked-by: Serge E. Hallyn Signed-off-by: "Eric W. Biederman" List of files: /linux-6.15/tools/testing/selftests/mount/Makefile