linux.git/fs/ext4/Makefile, branch v4.9

ext4 crypto: migrate into vfs's crypto engine

2016-07-10T18:01:03+00:00

This patch removes the most parts of internal crypto codes.
And then, it modifies and adds some ext4-specific crypt codes to use the generic
facility.

Signed-off-by: Jaegeuk Kim 
Signed-off-by: Theodore Ts'o

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

2015-09-23T16:44:17+00:00

Also statically allocate the ext4_kset and ext4_feat objects, since we
only need exactly one of each, and it's simpler and less code if we
drop the dynamic allocation and deallocation when it's not needed.

Signed-off-by: Theodore Ts'o

ext4 crypto: filename encryption facilities

2015-04-12T04:56:17+00:00

Signed-off-by: Uday Savagaonkar 
Signed-off-by: Ildar Muslukhov 
Signed-off-by: Michael Halcrow 
Signed-off-by: Theodore Ts'o

ext4 crypto: add encryption key management facilities

2015-04-12T04:55:06+00:00

Signed-off-by: Michael Halcrow 
Signed-off-by: Ildar Muslukhov 
Signed-off-by: Theodore Ts'o

ext4 crypto: add ext4 encryption facilities

2015-04-12T04:43:56+00:00

On encrypt, we will re-assign the buffer_heads to point to a bounce
page rather than the control_page (which is the original page to write
that contains the plaintext). The block I/O occurs against the bounce
page.  On write completion, we re-assign the buffer_heads to the
original plaintext page.

On decrypt, we will attach a read completion callback to the bio
struct. This read completion will decrypt the read contents in-place
prior to setting the page up-to-date.

The current encryption mode, AES-256-XTS, lacks cryptographic
integrity. AES-256-GCM is in-plan, but we will need to devise a
mechanism for handling the integrity data.

Signed-off-by: Michael Halcrow 
Signed-off-by: Ildar Muslukhov 
Signed-off-by: Theodore Ts'o

ext4 crypto: add encryption policy and password salt support

2015-04-11T11:48:01+00:00

Signed-off-by: Michael Halcrow 
Signed-off-by: Theodore Ts'o 
Signed-off-by: Ildar Muslukhov

ext4 crypto: add ext4_mpage_readpages()

2015-04-08T04:00:32+00:00

This takes code from fs/mpage.c and optimizes it for ext4.  Its
primary reason is to allow us to more easily add encryption to ext4's
read path in an efficient manner.

Signed-off-by: Theodore Ts'o

ext4: Remove CONFIG_EXT4_FS_XATTR

2012-12-10T21:30:43+00:00

Ted has sent out a RFC about removing this feature. Eric and Jan
confirmed that both RedHat and SUSE enable this feature in all their
product.  David also said that "As far as I know, it's enabled in all
Android 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 while
xattr disabled.  So I think we should add inline data and remove this
config 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"

ext4: add the basic function for inline data support

2012-12-10T19:04:46+00:00

Implement inline data with xattr.

Now we use "system.data" to store xattr, and the xattr will
be extended if the i_size is increased while we don't release
the space during truncate.

Signed-off-by: Tao Ma 
Signed-off-by: "Theodore Ts'o"

ext4: add operations on extent status tree

2012-11-09T02:57:20+00:00

This 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"