Changes in Makefile

66cda7ec9abec7ec3b81678c48deab3450d038a6 - selftests/filesystems: check that an immutable inode takes no write hint

Fri, 02 Oct 2026 15:52:35 +0200

selftests/filesystems: check that an immutable inode takes no write hintCheck that an immutable inode takes no write hint.Link: https://patch.msgid.link/20261002-work-mount-fixes-4-v1-4-dd44b89d44ce@kernel.orgSigned-off-by: Christian Brauner (Amutable) List of files: /linux/tools/testing/selftests/filesystems/Makefile

1781f0b3d75caa22376cf7fa0224f9aca696580d - Merge tag 'vfs-7.3-rc1.super' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs

Mon, 17 Aug 2026 22:57:04 +0200

Merge tag 'vfs-7.3-rc1.super' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfsPull vfs superblock updates from Christian Brauner: - Make it possible to share a block device between multiple filesystems. erofs can mount read-only blob devices shared between many superblocks, but because we only tracked a single superblock a freeze, thaw, removal or sync on such a device was never propagated to all the superblocks using it, and there was no way to find them. Add an efficient table to lookup all superblocks using a given block device. - A bunch of pre-existing fixes fell out of this work: A block-device freeze racing a btrfs device change could leave the whole filesystem stuck frozen. A bdev_freeze() issued by "dmsetup suspend" or an LVM snapshot resolves that holder to freeze the filesystem. and bdev_thaw() resolves it again to thaw. A freeze landing while btrfs is adding, removing or replacing a device freezes the filesystem. The membership change then drops that link. So the matching thaw could no longer find the superblock. Forbid freezing a device for the duration of a membership change, modelled on deny_write_access()/allow_write_access().* tag 'vfs-7.3-rc1.super' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs: (24 commits) super: fix dying superblock warning messages block: reject block device inodes with i_rdev == 0 in lookup_bdev() selftests/filesystems: add ustat() coverage fs: look up the superblock via the device table in user_get_super() super: make fs_holder_ops private f2fs: open via dedicated fs bdev helpers erofs: open via dedicated fs bdev helpers fs: tolerate per-superblock freeze errors on shared devices fs: look up superblocks via the device table in fs_holder_ops ext4: open via dedicated fs bdev helpers btrfs: open via dedicated fs bdev helpers xfs: port to fs_bdev_file_open_by_path() fs: add dedicated block device open helpers for filesystems fs: maintain a global device-to-superblock table ocfs2: don't reset s_dev on dismount ext4: use anonymous devices for KUnit test superblocks fs, block: move blk_mode_t and fop_flags_t into super: take lock after last reference count super: convert s_count to refcount_t s_passive btrfs: deny freezing devices undergoing a replace ... List of files: /linux/tools/testing/selftests/filesystems/Makefile

d943e68edc5cb98192d38e31373bb6b6a73230c6 - selftests/filesystems: test O_TMPFILE creation on idmapped mounts

Mon, 15 Jun 2026 14:52:19 +0200

selftests/filesystems: test O_TMPFILE creation on idmapped mountsAdd a regression test for the fsuidgid_has_mapping() check invfs_tmpfile(). It idmaps a detached tmpfs mount so that thecaller-visible id range [0, 10000) maps onto the on-disk range[10000, 20000) and checks that: - a caller whose fsuid/fsgid fall outside that range cannot create an O_TMPFILE through the mount and gets -EOVERFLOW instead of an inode owned by (uid_t)-1; - a mapped caller can create an O_TMPFILE, link it into the namespace, and the ownership round-trips through the mount idmap: it is reported as 0 through the mount and stored as 10000 on the underlying tmpfs.The test runs entirely as root and uses setfsuid()/setfsgid() to becomethe unmapped caller, so it needs no helper user. The layer directory isworld-writable so that an unmapped caller still clears the directorypermission check and reaches the fsuidgid_has_mapping() test.Link: https://patch.msgid.link/20260615-work-idmapped-tmpfile-v1-2-754a94d81f83@kernel.orgReviewed-by: Jan Kara Signed-off-by: Christian Brauner (Amutable) List of files: /linux/tools/testing/selftests/filesystems/Makefile

a21db4dcaf4ad617c6f7aa9e4c879cf0d797631b - selftests/filesystems: add ustat() coverage

Tue, 16 Jun 2026 16:08:34 +0200

selftests/filesystems: add ustat() coverageuser_get_super() is now backed by the global device-to-superblock tableinstead of a walk of the super_blocks list. ustat(2) is its most directuser-visible consumer but nothing in the tree exercises it.Add a small regression test: the device number of a mounted tmpfs (ananonymous device, registered in the table by sget_fc()) must resolve,it must stop resolving after the unmount (the entry is dropped again inkill_super_notify()), and bogus device numbers keep reporting EINVAL.The test passes on kernels before the conversion: it pins down thesemantics the table-backed lookup must preserve.Link: https://patch.msgid.link/20260616-work-super-bdev_holder_global-v2-18-7df6b864028e@kernel.orgSigned-off-by: Christian Brauner (Amutable) List of files: /linux/tools/testing/selftests/filesystems/Makefile

df579e471111b9f8691d75c980f59cc085fa97a3 - selftests/filesystems: add basic fscontext log tests

Wed, 06 Aug 2025 19:55:24 +0200

selftests/filesystems: add basic fscontext log testsSigned-off-by: Aleksa Sarai Link: https://lore.kernel.org/20250807-fscontext-log-cleanups-v3-2-8d91d6242dc3@cyphar.comSigned-off-by: Christian Brauner List of files: /linux/tools/testing/selftests/filesystems/Makefile

70619d40e8307b4b2ce1d08405e7b827c61ba4a8 - selftests/kernfs: test xattr retrieval

Wed, 02 Jul 2025 13:53:21 +0200

selftests/kernfs: test xattr retrievalMake sure that listxattr() returns zero and that getxattr() returnsENODATA when no extended attributs are set. Use /sys/kernel/warn_countas that always exists and is a read-only file.Link: https://lore.kernel.org/20250702-hochmoderne-abklatsch-af9c605b57b2@braunerSigned-off-by: Christian Brauner List of files: /linux/tools/testing/selftests/filesystems/Makefile

c784159750bc83aa91d49ceeb2dbd627d22c0587 - selftests/filesystems: add chown() test for anonymous inodes

Mon, 07 Apr 2025 11:54:20 +0200

selftests/filesystems: add chown() test for anonymous inodesTest that anonymous inodes cannot be chown()ed.Link: https://lore.kernel.org/20250407-work-anon_inode-v1-6-53a44c20d44e@kernel.orgReviewed-by: Jeff Layton Signed-off-by: Christian Brauner List of files: /linux/tools/testing/selftests/filesystems/Makefile

aab154a442f9ba2a08fc130dbc8d178a33e10345 - selftests: add file SLAB_TYPESAFE_BY_RCU recycling stressor

Mon, 21 Oct 2024 13:54:46 +0200

selftests: add file SLAB_TYPESAFE_BY_RCU recycling stressorAdd a simple file stressor that lives directly in-tree. This will createa bunch of processes that each open 500 file descriptors and then useclose_range() to close them all.Concurrently, other processes read /proc//fd/ which rougly does f = fget_task_next(p, &fd); if (!f) break; data.mode = f->f_mode; fput(f);Which means that it'll try to get a reference to a file in anothertask's file descriptor table.Under heavy file load it is increasingly likely that the other task willmanage to close @file and @file will be recycled due toSLAB_TYPEAFE_BY_RCU concurrently. This will trigger various warnings inthe file reference counting code.Link: https://lore.kernel.org/r/20241021-vergab-streuen-924df15dceb9@braunerSigned-off-by: Christian Brauner List of files: /linux/tools/testing/selftests/filesystems/Makefile

c2d3cf3653a8ff6e4b402d55e7f84790ac08a8ad - selftests: filesystems: Fix incorrect kernel headers search path

Fri, 27 Jan 2023 14:57:29 +0100

selftests: filesystems: Fix incorrect kernel headers search pathUse $(KHDR_INCLUDES) as lookup path for kernel headers. This preventsbuilding against kernel headers from the build environment in scenarioswhere kernel headers are installed into a specific output directory(O=...).Signed-off-by: Mathieu Desnoyers Cc: Shuah Khan Cc: linux-kselftest@vger.kernel.orgCc: Ingo Molnar Cc: # 5.18+Signed-off-by: Shuah Khan List of files: /linux/tools/testing/selftests/filesystems/Makefile

dd4b16b4f9b1b7d9f4a185cb8222e42f3a5daf00 - selftests/filesystems: devpts_pts included wrong header

Wed, 18 Apr 2018 09:52:55 +0200

selftests/filesystems: devpts_pts included wrong headerWe were picking up the wrong header should use asm/ioctls.h form the kerneland not the header from the system (sys/ioctl.h). In the current code weadded the correct include and we added the kernel headers path to the CFLAGS.Fixes: ce290a19609d ("selftests: add devpts selftests")Signed-off-by: Anders Roxell Acked-by: Christian Brauner Signed-off-by: Shuah Khan (Samsung OSG) List of files: /linux/tools/testing/selftests/filesystems/Makefile

8bf24e8319613bbe950d4188682b3a0d9441b76b - selftests/filesystems: Don't run dnotify_test by default

Tue, 10 Apr 2018 08:20:53 +0200

selftests/filesystems: Don't run dnotify_test by defaultIn commit ce290a19609d ("selftests: add devpts selftests"), thefilesystems directory was added to the top-level selftests Makefile.That had the effect of causing the existing dnotify_test in thefilesystems directory to now be run as part of the default selfteststest-run. Unfortunately dnotify_test is actually an infinite loop.Fix it by moving dnotify_test to TEST_GEN_PROGS_EXTENDED, which saysthat it's a generated file (ie. built) but should not be run as partof the default test suite run (it's an "extended" test).While we're here cleanup a few other things, devpts_pts should be inTEST_GEN_PROGS to indicate that it's built, and with the above twochanges we no longer need a custom all or clean rule.Fixes: ce290a19609d ("selftests: add devpts selftests")Signed-off-by: Michael Ellerman Acked-by: Christian brauner Signed-off-by: Shuah Khan List of files: /linux/tools/testing/selftests/filesystems/Makefile

ce290a19609d5ecd4a240a4750e0ed9a476cf015 - selftests: add devpts selftests

Tue, 13 Mar 2018 17:55:27 +0100

selftests: add devpts selftestsThis adds tests to check:- bind-mounts from /dev/pts/ptmx to /dev/ptmx work- non-standard mounts of devpts work- bind-mounts of /dev/pts/ptmx to locations that do not resolve to a valid slave pty path under the originating devpts mount failSigned-off-by: Christian Brauner Acked-by: "Eric W. Biederman" Acked-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman List of files: /linux/tools/testing/selftests/filesystems/Makefile

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

Wed, 01 Nov 2017 15:07:57 +0100

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/tools/testing/selftests/filesystems/Makefile

10924bc6448760b355492f05ea414a65d924a72c - selftests: move dnotify_test from Documentation/filesystems

Tue, 13 Sep 2016 18:08:36 +0200

selftests: move dnotify_test from Documentation/filesystemsMove dnotify_test.c, Makefile, and .gitignore from Documentation/filesystemsto selftests/filesystems.Remove filesystems build target from Documentation/Makefile and updateselftests/filesystems/Makefile to work under selftests. dnotify_test willnot be run as part of selftests suite and will not be included in installtargets. It can be built separately for now.Acked-by: Jonathan Corbet Signed-off-by: Shuah Khan List of files: /linux/tools/testing/selftests/filesystems/Makefile