Messages in this thread Patch in this message | | | From | Fabian Frederick <> | Subject | [PATCH V2 linux-next] ext4: fix block_validity definition | Date | Mon, 7 Nov 2016 08:25:40 +0100 |
| |
Fix ext4 documentation according to commit 45f1a9c3f63d ("ext4: enable block_validity by default")
Also fix some typos.
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Fabian Frederick <fabf@skynet.be> --- V2: Replace beginning of the definition (suggested by Darrick).
Documentation/filesystems/ext4.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/Documentation/filesystems/ext4.txt b/Documentation/filesystems/ext4.txt index 6c0108e..1d92713 100644 --- a/Documentation/filesystems/ext4.txt +++ b/Documentation/filesystems/ext4.txt @@ -351,14 +351,13 @@ nouid32 Disables 32-bit UIDs and GIDs. This is for interoperability with older kernels which only store and expect 16-bit values. -block_validity This options allows to enables/disables the in-kernel +block_validity(*) These options enable or disable the in-kernel noblock_validity facility for tracking filesystem metadata blocks within internal data structures. This allows multi- block allocator and other routines to quickly locate extents which might overlap with filesystem metadata - blocks. This option is intended for debugging - purposes and since it negatively affects the - performance, it is off by default. + blocks. Initially intended for debugging, it's now + enabled by default. dioread_lock Controls whether or not ext4 should use the DIO read dioread_nolock locking. If the dioread_nolock option is specified -- 2.7.4
| |