Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Fix spelling and gramatical errors

Fixed 3 typos in design.rst

Signed-off-by: Xiaxi Shen <shenxiaxi26@gmail.com>
Link: https://lore.kernel.org/r/20240807070536.14536-1-shenxiaxi26@gmail.com
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Christian Brauner <brauner@kernel.org>

authored by

Xiaxi Shen and committed by
Christian Brauner
28c7658b 087adb4f

+3 -3
+3 -3
Documentation/filesystems/iomap/design.rst
··· 142 142 * **pure overwrite**: A write operation that does not require any 143 143 metadata or zeroing operations to perform during either submission 144 144 or completion. 145 - This implies that the fileystem must have already allocated space 145 + This implies that the filesystem must have already allocated space 146 146 on disk as ``IOMAP_MAPPED`` and the filesystem must not place any 147 - constaints on IO alignment or size. 147 + constraints on IO alignment or size. 148 148 The only constraints on I/O alignment are device level (minimum I/O 149 149 size and alignment, typically sector size). 150 150 ··· 394 394 395 395 * The **upper** level primitive is provided by the filesystem to 396 396 coordinate access to different iomap operations. 397 - The exact primitive is specifc to the filesystem and operation, 397 + The exact primitive is specific to the filesystem and operation, 398 398 but is often a VFS inode, pagecache invalidation, or folio lock. 399 399 For example, a filesystem might take ``i_rwsem`` before calling 400 400 ``iomap_file_buffered_write`` and ``iomap_file_unshare`` to prevent