| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20250928062832.3465356-1-cuitao@kylinos.cn> Date: Sun, 28 Sep 2025 14:28:32 +0800 From: cuitao <cuitao@...inos.cn> To: axboe@...nel.dk, linux-block@...r.kernel.org Cc: linux-kernel@...r.kernel.org, cuitao <cuitao@...inos.cn> Subject: [PATCH] block: Kconfig: Fix indentation. The convention for indentation seems to be a single tab. Help text is further indented by an additional two whitespaces. Fix the lines that violate these rules. Signed-off-by: cuitao <cuitao@...inos.cn> --- block/Kconfig | 116 +++++++++++++++++++++++++------------------------- 1 file changed, 58 insertions(+), 58 deletions(-) diff --git a/block/Kconfig b/block/Kconfig index 15027963472d..ce19774969f4 100644 --- a/block/Kconfig +++ b/block/Kconfig @@ -65,82 +65,82 @@ config BLK_DEV_INTEGRITY select CRC_T10DIF select CRC64 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. + 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. + 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_WRITE_MOUNTED bool "Allow writing to mounted block devices" default y help - When a block device is mounted, writing to its buffer cache is very - likely going to cause filesystem corruption. It is also rather easy to - crash the kernel in this way since the filesystem has no practical way - of detecting these writes to buffer cache and verifying its metadata - integrity. However there are some setups that need this capability - like running fsck on read-only mounted root device, modifying some - features on mounted ext4 filesystem, and similar. If you say N, the - kernel will prevent processes from writing to block devices that are - mounted by filesystems which provides some more protection from runaway - privileged processes and generally makes it much harder to crash - filesystem drivers. Note however that this does not prevent - underlying device(s) from being modified by other means, e.g. by - directly submitting SCSI commands or through access to lower layers of - storage stack. If in doubt, say Y. The configuration can be overridden - with the bdev_allow_write_mounted boot option. + When a block device is mounted, writing to its buffer cache is very + likely going to cause filesystem corruption. It is also rather easy to + crash the kernel in this way since the filesystem has no practical way + of detecting these writes to buffer cache and verifying its metadata + integrity. However there are some setups that need this capability + like running fsck on read-only mounted root device, modifying some + features on mounted ext4 filesystem, and similar. If you say N, the + kernel will prevent processes from writing to block devices that are + mounted by filesystems which provides some more protection from runaway + privileged processes and generally makes it much harder to crash + filesystem drivers. Note however that this does not prevent + underlying device(s) from being modified by other means, e.g. by + directly submitting SCSI commands or through access to lower layers of + storage stack. If in doubt, say Y. The configuration can be overridden + with the bdev_allow_write_mounted boot option. config BLK_DEV_ZONED bool "Zoned block device support" help - Block layer zoned block device support. This option enables - support for ZAC/ZBC/ZNS host-managed and host-aware zoned block - devices. + Block layer zoned block device support. This option enables + support for ZAC/ZBC/ZNS host-managed and host-aware zoned block + devices. - Say yes here if you have a ZAC, ZBC, or ZNS storage device. + Say yes here if you have a ZAC, ZBC, or ZNS storage device. config BLK_DEV_THROTTLING bool "Block layer bio throttling support" depends on BLK_CGROUP select BLK_CGROUP_RWSTAT 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. + 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/admin-guide/cgroup-v1/blkio-controller.rst for more information. + See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information. config BLK_WBT bool "Enable support for block device writeback throttling" 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. + 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_MQ bool "Enable writeback throttling by default" default y depends on BLK_WBT help - Enable writeback throttling by default for request-based block devices. + Enable writeback throttling by default for request-based block devices. config BLK_CGROUP_IOLATENCY bool "Enable support for latency based cgroup IO protection" depends on BLK_CGROUP help - Enabling this option enables the .latency interface for IO throttling. - The IO controller will attempt to maintain average IO latencies below - the configured latency target, throttling anybody with a higher latency - target than the victimized group. + Enabling this option enables the .latency interface for IO throttling. + The IO controller will attempt to maintain average IO latencies below + the configured latency target, throttling anybody with a higher latency + target than the victimized group. - Note, this is an experimental interface and could be changed someday. + Note, this is an experimental interface and could be changed someday. config BLK_CGROUP_FC_APPID bool "Enable support to track FC I/O Traffic across cgroup applications" @@ -156,31 +156,31 @@ config BLK_CGROUP_IOCOST depends on BLK_CGROUP select BLK_RQ_ALLOC_TIME help - Enabling this option enables the .weight interface for cost - model based proportional IO control. The IO controller - distributes IO capacity between different groups based on - their share of the overall weight distribution. + Enabling this option enables the .weight interface for cost + model based proportional IO control. The IO controller + distributes IO capacity between different groups based on + their share of the overall weight distribution. config BLK_CGROUP_IOPRIO bool "Cgroup I/O controller for assigning an I/O priority class" depends on BLK_CGROUP help - Enable the .prio interface for assigning an I/O priority class to - requests. The I/O priority class affects the order in which an I/O - scheduler and block devices process requests. Only some I/O schedulers - and some block devices support I/O priorities. + Enable the .prio interface for assigning an I/O priority class to + requests. The I/O priority class affects the order in which an I/O + scheduler and block devices process requests. Only some I/O schedulers + and some block devices support I/O priorities. 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. + 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. + 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" @@ -188,9 +188,9 @@ config BLK_SED_OPAL select PSERIES_PLPKS if PPC_PSERIES select PSERIES_PLPKS_SED if PPC_PSERIES 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. + 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" -- 2.48.1
Powered by blists - more mailing lists