88205c5d99
These changes integrate new file encryption framework to use new V2 encryption policies. These changes were earlier reverted in 'commit4211691d29("Reverting crypto and incrementalfs changes")', as part of android-4.14.171 merge from Android common kernel. This patch attempts to bring them back post validation. commita9a5450ANDROID: dm: prevent default-key from being enabled without needed hooks commite1a94e6ANDROID: dm: add dm-default-key target for metadata encryption commit commit232fd35ANDROID: dm: enable may_passthrough_inline_crypto on some targets commit53bc059ANDROID: dm: add support for passing through inline crypto support commitaeed6dbANDROID: block: Introduce passthrough keyslot manager commit4f27c8bANDROID: ext4, f2fs: enable direct I/O with inline encryption commitc91db46BACKPORT: FROMLIST: scsi: ufs: add program_key() variant op commitf9a8e4aANDROID: block: export symbols needed for modules to use inline crypto commit75fea5fANDROID: block: fix some inline crypto bugs commit2871f73ANDROID: fscrypt: add support for hardware-wrapped keys commitbb5a657ANDROID: block: add KSM op to derive software secret from wrapped key commitd42ba87ANDROID: block: provide key size as input to inline crypto APIs commit86646ebANDROID: ufshcd-crypto: export cap find API commit83bc20eANDROID: scsi: ufs-qcom: Enable BROKEN_CRYPTO quirk flag commitc266a13ANDROID: scsi: ufs: Add quirk bit for controllers that don't play well with inline crypto commitea09b99ANDROID: cuttlefish_defconfig: Enable blk-crypto fallback commite12563cBACKPORT: FROMLIST: Update Inline Encryption from v5 to v6 of patch series commit8e8f55dANDROID: scsi: ufs: UFS init should not require inline crypto commitdae9899ANDROID: scsi: ufs: UFS crypto variant operations API commita69516dANDROID: cuttlefish_defconfig: enable inline encryption commitb8f7b23BACKPORT: FROMLIST: ext4: add inline encryption support commite64327fBACKPORT: FROMLIST: f2fs: add inline encryption support commita0dc8daBACKPORT: FROMLIST: fscrypt: add inline encryption support commit19c3c62BACKPORT: FROMLIST: scsi: ufs: Add inline encryption support to UFS commitf858a99BACKPORT: FROMLIST: scsi: ufs: UFS crypto API commit011b834BACKPORT: FROMLIST: scsi: ufs: UFS driver v2.1 spec crypto additions commitec0b569BACKPORT: FROMLIST: block: blk-crypto for Inline Encryption commit760b328ANDROID: block: Fix bio_crypt_should_process WARN_ON commit138adbbBACKPORT: FROMLIST: block: Add encryption context to struct bio commit66b5609BACKPORT: FROMLIST: block: Keyslot Manager for Inline Encryption Git-repo: https://android.googlesource.com/kernel/common/+/refs/heads/android-4.14-stable Git-commit:a9a545067aGit-commit:e1a94e6b17Git-commit:232fd353e4Git-commit:53bc059bc6Git-commit:aeed6db424Git-commit:4f27c8b90bGit-commit:c91db466b5Git-commit:f9a8e4a5c5Git-commit:75fea5f605Git-commit:2871f73194Git-commit:bb5a65771aGit-commit:d42ba87e29Git-commit:86646ebb17Git-commit:83bc20ed4bGit-commit:c266a1311eGit-commit:ea09b9954cGit-commit:e12563c18dGit-commit:8e8f55d1a7Git-commit:dae9899044Git-commit:a69516d091Git-commit:b8f7b23674Git-commit:e64327f571Git-commit:a0dc8da519Git-commit:19c3c62836Git-commit:f858a9981aGit-commit:011b8344c3Git-commit:ec0b569b5cGit-commit:760b3283e8Git-commit:138adbbe5eGit-commit:66b5609826Change-Id: I171d90de41185824e0c7515f3a3b43ab88f4e058 Signed-off-by: Neeraj Soni <neersoni@codeaurora.org>
233 lines
6.7 KiB
Plaintext
233 lines
6.7 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
#
|
|
# Block layer core configuration
|
|
#
|
|
menuconfig BLOCK
|
|
bool "Enable the block layer" if EXPERT
|
|
default y
|
|
select SBITMAP
|
|
select SRCU
|
|
help
|
|
Provide block layer support for the kernel.
|
|
|
|
Disable this option to remove the block layer support from the
|
|
kernel. This may be useful for embedded devices.
|
|
|
|
If this option is disabled:
|
|
|
|
- block device files will become unusable
|
|
- some filesystems (such as ext3) will become unavailable.
|
|
|
|
Also, SCSI character devices and USB storage will be disabled since
|
|
they make use of various block layer definitions and facilities.
|
|
|
|
Say Y here unless you know you really don't want to mount disks and
|
|
suchlike.
|
|
|
|
if BLOCK
|
|
|
|
config LBDAF
|
|
bool "Support for large (2TB+) block devices and files"
|
|
depends on !64BIT
|
|
default y
|
|
help
|
|
Enable block devices or files of size 2TB and larger.
|
|
|
|
This option is required to support the full capacity of large
|
|
(2TB+) block devices, including RAID, disk, Network Block Device,
|
|
Logical Volume Manager (LVM) and loopback.
|
|
|
|
This option also enables support for single files larger than
|
|
2TB.
|
|
|
|
The ext4 filesystem requires that this feature be enabled in
|
|
order to support filesystems that have the huge_file feature
|
|
enabled. Otherwise, it will refuse to mount in the read-write
|
|
mode any filesystems that use the huge_file feature, which is
|
|
enabled by default by mke2fs.ext4.
|
|
|
|
The GFS2 filesystem also requires this feature.
|
|
|
|
If unsure, say Y.
|
|
|
|
config BLK_SCSI_REQUEST
|
|
bool
|
|
|
|
config BLK_DEV_BSG
|
|
bool "Block layer SG support v4"
|
|
default y
|
|
select BLK_SCSI_REQUEST
|
|
help
|
|
Saying Y here will enable generic SG (SCSI generic) v4 support
|
|
for any block device.
|
|
|
|
Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
|
|
can handle complicated SCSI commands: tagged variable length cdbs
|
|
with bidirectional data transfers and generic request/response
|
|
protocols (e.g. Task Management Functions and SMP in Serial
|
|
Attached SCSI).
|
|
|
|
This option is required by recent UDEV versions to properly
|
|
access device serial numbers, etc.
|
|
|
|
If unsure, say Y.
|
|
|
|
config BLK_DEV_BSGLIB
|
|
bool "Block layer SG support v4 helper lib"
|
|
default n
|
|
select BLK_DEV_BSG
|
|
select BLK_SCSI_REQUEST
|
|
help
|
|
Subsystems will normally enable this if needed. Users will not
|
|
normally need to manually enable this.
|
|
|
|
If unsure, say N.
|
|
|
|
config BLK_DEV_INTEGRITY
|
|
bool "Block layer data integrity support"
|
|
select CRC_T10DIF if BLK_DEV_INTEGRITY
|
|
---help---
|
|
Some storage devices allow extra information to be
|
|
stored/retrieved to help protect the data. The block layer
|
|
data integrity option provides hooks which can be used by
|
|
filesystems to ensure better data integrity.
|
|
|
|
Say yes here if you have a storage device that provides the
|
|
T10/SCSI Data Integrity Field or the T13/ATA External Path
|
|
Protection. If in doubt, say N.
|
|
|
|
config BLK_DEV_ZONED
|
|
bool "Zoned block device support"
|
|
---help---
|
|
Block layer zoned block device support. This option enables
|
|
support for ZAC/ZBC host-managed and host-aware zoned block devices.
|
|
|
|
Say yes here if you have a ZAC or ZBC storage device.
|
|
|
|
config BLK_DEV_THROTTLING
|
|
bool "Block layer bio throttling support"
|
|
depends on BLK_CGROUP=y
|
|
default n
|
|
---help---
|
|
Block layer bio throttling support. It can be used to limit
|
|
the IO rate to a device. IO rate policies are per cgroup and
|
|
one needs to mount and use blkio cgroup controller for creating
|
|
cgroups and specifying per device IO rate policies.
|
|
|
|
See Documentation/cgroups/blkio-controller.txt for more information.
|
|
|
|
config BLK_DEV_THROTTLING_LOW
|
|
bool "Block throttling .low limit interface support (EXPERIMENTAL)"
|
|
depends on BLK_DEV_THROTTLING
|
|
default n
|
|
---help---
|
|
Add .low limit interface for block throttling. The low limit is a best
|
|
effort limit to prioritize cgroups. Depending on the setting, the limit
|
|
can be used to protect cgroups in terms of bandwidth/iops and better
|
|
utilize disk resource.
|
|
|
|
Note, this is an experimental interface and could be changed someday.
|
|
|
|
config BLK_CMDLINE_PARSER
|
|
bool "Block device command line partition parser"
|
|
default n
|
|
---help---
|
|
Enabling this option allows you to specify the partition layout from
|
|
the kernel boot args. This is typically of use for embedded devices
|
|
which don't otherwise have any standardized method for listing the
|
|
partitions on a block device.
|
|
|
|
See Documentation/block/cmdline-partition.txt for more information.
|
|
|
|
config BLK_WBT
|
|
bool "Enable support for block device writeback throttling"
|
|
default n
|
|
---help---
|
|
Enabling this option enables the block layer to throttle buffered
|
|
background writeback from the VM, making it more smooth and having
|
|
less impact on foreground operations. The throttling is done
|
|
dynamically on an algorithm loosely based on CoDel, factoring in
|
|
the realtime performance of the disk.
|
|
|
|
config BLK_WBT_SQ
|
|
bool "Single queue writeback throttling"
|
|
default n
|
|
depends on BLK_WBT
|
|
---help---
|
|
Enable writeback throttling by default on legacy single queue devices
|
|
|
|
config BLK_WBT_MQ
|
|
bool "Multiqueue writeback throttling"
|
|
default y
|
|
depends on BLK_WBT
|
|
---help---
|
|
Enable writeback throttling by default on multiqueue devices.
|
|
Multiqueue currently doesn't have support for IO scheduling,
|
|
enabling this option is recommended.
|
|
|
|
config BLK_DEBUG_FS
|
|
bool "Block layer debugging information in debugfs"
|
|
default y
|
|
depends on DEBUG_FS
|
|
---help---
|
|
Include block layer debugging information in debugfs. This information
|
|
is mostly useful for kernel developers, but it doesn't incur any cost
|
|
at runtime.
|
|
|
|
Unless you are building a kernel for a tiny system, you should
|
|
say Y here.
|
|
|
|
config BLK_SED_OPAL
|
|
bool "Logic for interfacing with Opal enabled SEDs"
|
|
---help---
|
|
Builds Logic for interfacing with Opal enabled controllers.
|
|
Enabling this option enables users to setup/unlock/lock
|
|
Locking ranges for SED devices using the Opal protocol.
|
|
|
|
config BLK_INLINE_ENCRYPTION
|
|
bool "Enable inline encryption support in block layer"
|
|
help
|
|
Build the blk-crypto subsystem. Enabling this lets the
|
|
block layer handle encryption, so users can take
|
|
advantage of inline encryption hardware if present.
|
|
|
|
config BLK_INLINE_ENCRYPTION_FALLBACK
|
|
bool "Enable crypto API fallback for blk-crypto"
|
|
depends on BLK_INLINE_ENCRYPTION
|
|
select CRYPTO
|
|
select CRYPTO_BLKCIPHER
|
|
help
|
|
Enabling this lets the block layer handle inline encryption
|
|
by falling back to the kernel crypto API when inline
|
|
encryption hardware is not present.
|
|
|
|
menu "Partition Types"
|
|
|
|
source "block/partitions/Kconfig"
|
|
|
|
endmenu
|
|
|
|
endif # BLOCK
|
|
|
|
config BLOCK_COMPAT
|
|
bool
|
|
depends on BLOCK && COMPAT
|
|
default y
|
|
|
|
config BLK_MQ_PCI
|
|
bool
|
|
depends on BLOCK && PCI
|
|
default y
|
|
|
|
config BLK_MQ_VIRTIO
|
|
bool
|
|
depends on BLOCK && VIRTIO
|
|
default y
|
|
|
|
config BLK_MQ_RDMA
|
|
bool
|
|
depends on BLOCK && INFINIBAND
|
|
default y
|
|
|
|
source block/Kconfig.iosched
|