Changes in Makefile

b1241c8e - ext4: move ext4 crypto code to its own file crypto.c

Sun, 15 May 2022 06:37:46 +0000

ext4: move ext4 crypto code to its own file crypto.cThis is to cleanup super.c file which has grown quite large.So, start moving ext4 crypto related code to where it shouldbe in the first place i.e. fs/ext4/crypto.cReviewed-by: Eric Biggers Signed-off-by: Ritesh Harjani Link: https://lore.kernel.org/r/7d637e093cbc34d727397e8d41a53a1b9ca7d7a4.1652595565.git.ritesh.list@gmail.comSigned-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

25c6d98f - ext4: Move orphan inode handling into a separate file

Mon, 16 Aug 2021 09:57:05 +0000

ext4: Move orphan inode handling into a separate fileMove functions for handling orphan inodes into a new filefs/ext4/orphan.c to have them in one place and somewhat reduce size ofother files. No code changes.Reviewed-by: Andreas Dilger Reviewed-by: Theodore Ts'o Signed-off-by: Jan Kara Link: https://lore.kernel.org/r/20210816095713.16537-2-jack@suse.czSigned-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

6866d7b3 - ext4 / jbd2: add fast commit initialization

Thu, 15 Oct 2020 20:37:55 +0000

ext4 / jbd2: add fast commit initializationThis patch adds fast commit area trackers in the journal_tstructure. These are initialized via the jbd2_fc_init() routine thatthis patch adds. This patch also adds ext4/fast_commit.c andext4/fast_commit.h files for fast commit code that will be added insubsequent patches in this series.Reported-by: kernel test robot Signed-off-by: Harshad Shirwadkar Link: https://lore.kernel.org/r/20201015203802.3597742-4-harshadshirwadkar@gmail.comSigned-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

88ee9d57 - ext4: support xattr gnu.* namespace for the Hurd

Mon, 25 May 2020 19:39:40 +0000

ext4: support xattr gnu.* namespace for the HurdThe Hurd gained[0] support for moving the translator and authorfields out of the inode and into the "gnu.*" xattr namespace.In anticipation of that, an xattr INDEX was reserved[1]. The Hurd hasnow been brought into compliance[2] with that.This patch adds support for reading and writing such attributes fromLinux; you can now do something like mkdir -p hurd-root/servers/socket touch hurd-root/servers/socket/1 setfattr --name=gnu.translator --value='"/hurd/pflocal\0"' \ hurd-root/servers/socket/1 getfattr --name=gnu.translator hurd-root/servers/socket/1 # file: 1 gnu.translator="/hurd/pflocal"to setup a pipe translator, which is being used to create[3] avm-image for the Hurd from GNU Guix.[0] https://summerofcode.withgoogle.com/projects/#5869799859027968[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3980bd3b406addb327d858aebd19e229ea340b9a[2] https://git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=a04c7bf83172faa7cb080fbe3b6c04a8415ca645[3] https://git.savannah.gnu.org/cgit/guix.git/log/?h=wip-hurd-vmSigned-off-by: Jan Nieuwenhuizen Link: https://lore.kernel.org/r/20200525193940.878-1-janneke@gnu.orgSigned-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

c475c77d - kunit: allow kunit tests to be loaded as a module

Mon, 06 Jan 2020 22:28:20 +0000

kunit: allow kunit tests to be loaded as a moduleAs tests are added to kunit, it will become less feasible to executeall built tests together. By supporting modular tests we providea simple way to do selective execution on a running system; specifyingCONFIG_KUNIT=yCONFIG_KUNIT_EXAMPLE_TEST=m...means we can simply "insmod example-test.ko" to run the tests.To achieve this we need to do the following:o export the required symbols in kunito string-stream tests utilize non-exported symbols so for now we skip building them when CONFIG_KUNIT_TEST=m.o drivers/base/power/qos-test.c contains a few unexported interface references, namely freq_qos_read_value() and freq_constraints_init(). Both of these could be potentially defined as static inline functions in include/linux/pm_qos.h, but for now we simply avoid supporting module build for that test suite.o support a new way of declaring test suites. Because a module cannot do multiple late_initcall()s, we provide a kunit_test_suites() macro to declare multiple suites within the same module at once.o some test module names would have been too general ("test-test" and "example-test" for kunit tests, "inode-test" for ext4 tests); rename these as appropriate ("kunit-test", "kunit-example-test" and "ext4-inode-test" respectively).Also define kunit_test_suite() via kunit_test_suites()as callers in other trees may need the old definition.Co-developed-by: Knut Omang Signed-off-by: Knut Omang Signed-off-by: Alan Maguire Reviewed-by: Brendan Higgins Acked-by: Theodore Ts'o # for ext4 bitsAcked-by: David Gow # For list-testReported-by: kbuild test robot Signed-off-by: Shuah Khan List of files: /linux-6.15/fs/ext4/Makefile

1cbeab1b - ext4: add kunit test for decoding extended timestamps

Thu, 17 Oct 2019 22:12:33 +0000

ext4: add kunit test for decoding extended timestampsKUnit tests for decoding extended 64 bit timestamps that verify theseconds part of [a/c/m] timestamps in ext4 inode structs are decodedcorrectly.Test data is derived from the table in the Inode Timestamps section ofDocumentation/filesystems/ext4/inodes.rst.KUnit tests run during boot and output the results to the debug login TAP format (http://testanything.org/). Only useful for kernel devsrunning KUnit test harness and are not for inclusion into a productionbuild.Signed-off-by: Iurii Zaikin Reviewed-by: Theodore Ts'o Reviewed-by: Brendan Higgins Tested-by: Brendan Higgins Reviewed-by: Shuah Khan Signed-off-by: Shuah Khan List of files: /linux-6.15/fs/ext4/Makefile

c93d8f88 - ext4: add basic fs-verity support

Mon, 22 Jul 2019 16:26:24 +0000

ext4: add basic fs-verity supportAdd most of fs-verity support to ext4. fs-verity is a filesystemfeature that enables transparent integrity protection and authenticationof read-only files. It uses a dm-verity like mechanism at the filelevel: a Merkle tree is used to verify any block in the file inlog(filesize) time. It is implemented mainly by helper functions infs/verity/. See Documentation/filesystems/fsverity.rst for the fulldocumentation.This commit adds all of ext4 fs-verity support except for the actualdata verification, including:- Adding a filesystem feature flag and an inode flag for fs-verity.- Implementing the fsverity_operations to support enabling verity on an inode and reading/writing the verity metadata.- Updating ->write_begin(), ->write_end(), and ->writepages() to support writing verity metadata pages.- Calling the fs-verity hooks for ->open(), ->setattr(), and ->ioctl().ext4 stores the verity metadata (Merkle tree and fsverity_descriptor)past the end of the file, starting at the first 64K boundary beyondi_size. This approach works because (a) verity files are readonly, and(b) pages fully beyond i_size aren't visible to userspace but can beread/written internally by ext4 with only some relatively small changesto ext4. This approach avoids having to depend on the EA_INODE featureand on rearchitecturing ext4's xattr support to support pagingmulti-gigabyte xattrs into memory, and to support encrypting xattrs.Note that the verity metadata *must* be encrypted when the file is,since it contains hashes of the plaintext data.This patch incorporates work by Theodore Ts'o and Chandan Rajendra.Reviewed-by: Theodore Ts'o Signed-off-by: Eric Biggers List of files: /linux-6.15/fs/ext4/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/ext4/Makefile

0c9ec4be - ext4: support GETFSMAP ioctls

Sun, 30 Apr 2017 04:36:53 +0000

ext4: support GETFSMAP ioctlsSupport the GETFSMAP ioctls so that we can use the xfs free spacemanagement tools to probe ext4 as well. Note that this is a partialimplementation -- we only report fixed-location metadata and free space;everything else is reported as "unknown".Signed-off-by: Darrick J. Wong Signed-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

a7550b30 - ext4 crypto: migrate into vfs's crypto engine

Sun, 10 Jul 2016 18:01:03 +0000

ext4 crypto: migrate into vfs's crypto engineThis patch removes the most parts of internal crypto codes.And then, it modifies and adds some ext4-specific crypt codes to use the genericfacility.Signed-off-by: Jaegeuk Kim Signed-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

b5799018 - ext4: move sysfs code from super.c to fs/ext4/sysfs.c

Wed, 23 Sep 2015 16:44:17 +0000

ext4: move sysfs code from super.c to fs/ext4/sysfs.cAlso statically allocate the ext4_kset and ext4_feat objects, since weonly need exactly one of each, and it's simpler and less code if wedrop the dynamic allocation and deallocation when it's not needed.Signed-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

d5d0e8c7 - ext4 crypto: filename encryption facilities

Sun, 12 Apr 2015 04:56:17 +0000

ext4 crypto: filename encryption facilitiesSigned-off-by: Uday Savagaonkar Signed-off-by: Ildar Muslukhov Signed-off-by: Michael Halcrow Signed-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

88bd6ccd - ext4 crypto: add encryption key management facilities

Sun, 12 Apr 2015 04:55:06 +0000

ext4 crypto: add encryption key management facilitiesSigned-off-by: Michael Halcrow Signed-off-by: Ildar Muslukhov Signed-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

b30ab0e0 - ext4 crypto: add ext4 encryption facilities

Sun, 12 Apr 2015 04:43:56 +0000

ext4 crypto: add ext4 encryption facilitiesOn encrypt, we will re-assign the buffer_heads to point to a bouncepage rather than the control_page (which is the original page to writethat contains the plaintext). The block I/O occurs against the bouncepage. On write completion, we re-assign the buffer_heads to theoriginal plaintext page.On decrypt, we will attach a read completion callback to the biostruct. This read completion will decrypt the read contents in-placeprior to setting the page up-to-date.The current encryption mode, AES-256-XTS, lacks cryptographicintegrity. AES-256-GCM is in-plan, but we will need to devise amechanism for handling the integrity data.Signed-off-by: Michael Halcrow Signed-off-by: Ildar Muslukhov Signed-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

9bd8212f - ext4 crypto: add encryption policy and password salt support

Sat, 11 Apr 2015 11:48:01 +0000

ext4 crypto: add encryption policy and password salt supportSigned-off-by: Michael Halcrow Signed-off-by: Theodore Ts'o Signed-off-by: Ildar Muslukhov List of files: /linux-6.15/fs/ext4/Makefile

f64e02fe - ext4 crypto: add ext4_mpage_readpages()

Wed, 08 Apr 2015 04:00:32 +0000

ext4 crypto: add ext4_mpage_readpages()This takes code from fs/mpage.c and optimizes it for ext4. Itsprimary reason is to allow us to more easily add encryption to ext4'sread path in an efficient manner.Signed-off-by: Theodore Ts'o List of files: /linux-6.15/fs/ext4/Makefile

939da108 - ext4: Remove CONFIG_EXT4_FS_XATTR

Mon, 10 Dec 2012 21:30:43 +0000

ext4: Remove CONFIG_EXT4_FS_XATTRTed has sent out a RFC about removing this feature. Eric and Janconfirmed that both RedHat and SUSE enable this feature in all theirproduct. David also said that "As far as I know, it's enabled in allAndroid kernels that use ext4." So it seems OK for us.And what's more, as inline data depends its implementation on xattr,and to be frank, I don't run any test again inline data enabled whilexattr disabled. So I think we should add inline data and remove thisconfig option in the same release.[ The savings if you disable CONFIG_EXT4_FS_XATTR is only 27k, which isn't much in the grand scheme of things. Since no one seems to be testing this configuration except for some automated compile farms, on balance we are better removing this config option, and so that it is effectively always enabled. -- tytso ]Cc: David Brown Cc: Eric Sandeen Reviewed-by: Jan Kara Signed-off-by: Tao Ma Signed-off-by: "Theodore Ts'o" List of files: /linux-6.15/fs/ext4/Makefile

67cf5b09 - ext4: add the basic function for inline data support

Mon, 10 Dec 2012 19:04:46 +0000

ext4: add the basic function for inline data supportImplement inline data with xattr.Now we use "system.data" to store xattr, and the xattr willbe extended if the i_size is increased while we don't releasethe space during truncate.Signed-off-by: Tao Ma Signed-off-by: "Theodore Ts'o" List of files: /linux-6.15/fs/ext4/Makefile

654598be - ext4: add operations on extent status tree

Fri, 09 Nov 2012 02:57:20 +0000

ext4: add operations on extent status treeThis patch adds operations on a extent status tree.CC: Lukas Czerner Signed-off-by: Yongqiang Yang Signed-off-by: Allison Henderson Signed-off-by: Hugh Dickins Signed-off-by: Zheng Liu Signed-off-by: "Theodore Ts'o" List of files: /linux-6.15/fs/ext4/Makefile

dae1e52c - ext4: move ext4_ind_* functions from inode.c to indirect.c

Mon, 27 Jun 2011 23:40:50 +0000

ext4: move ext4_ind_* functions from inode.c to indirect.cThis patch moves functions from inode.c to indirect.c.The moved functions are ext4_ind_* functions and their helpers.Functions called from inode.c are declared extern.Signed-off-by: Amir Goldstein Signed-off-by: "Theodore Ts'o" List of files: /linux-6.15/fs/ext4/Makefile