diff options
| author | Xichao Zhao <zhao.xichao@vivo.com> | 2025-08-08 16:37:01 +0800 |
|---|---|---|
| committer | Damien Le Moal <dlemoal@kernel.org> | 2025-08-12 11:59:27 +0900 |
| commit | a42938e80357a13f8b8592111e63f2e33a919863 (patch) | |
| tree | fb8b39c32473f975a83054c1c4f9c77b60eb25b0 | |
| parent | 8f5ae30d69d7543eee0d70083daf4de8fe15d585 (diff) | |
zonefs: correct some spelling mistakes
Trivial fix to spelling mistake in comment text.
(1) fix "unwriten"->"unwritten"
(2) fix "writen"->"written"
Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
| -rw-r--r-- | fs/zonefs/file.c | 2 | ||||
| -rw-r--r-- | fs/zonefs/super.c | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/fs/zonefs/file.c b/fs/zonefs/file.c index fd3a5922f6c3..90e2ad8ee5f4 100644 --- a/fs/zonefs/file.c +++ b/fs/zonefs/file.c @@ -85,7 +85,7 @@ static int zonefs_write_iomap_begin(struct inode *inode, loff_t offset, /* * For conventional zones, all blocks are always mapped. For sequential * zones, all blocks after always mapped below the inode size (zone - * write pointer) and unwriten beyond. + * write pointer) and unwritten beyond. */ mutex_lock(&zi->i_truncate_mutex); iomap->bdev = inode->i_sb->s_bdev; diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c index 4dc7f967c861..70be0b3dda49 100644 --- a/fs/zonefs/super.c +++ b/fs/zonefs/super.c @@ -268,7 +268,7 @@ static void zonefs_handle_io_error(struct inode *inode, struct blk_zone *zone, * Check the zone condition: if the zone is not "bad" (offline or * read-only), read errors are simply signaled to the IO issuer as long * as there is no inconsistency between the inode size and the amount of - * data writen in the zone (data_size). + * data written in the zone (data_size). */ data_size = zonefs_check_zone_condition(sb, z, zone); isize = i_size_read(inode); @@ -282,7 +282,7 @@ static void zonefs_handle_io_error(struct inode *inode, struct blk_zone *zone, * For the latter case, the cause may be a write IO error or an external * action on the device. Two error patterns exist: * 1) The inode size is lower than the amount of data in the zone: - * a write operation partially failed and data was writen at the end + * a write operation partially failed and data was written at the end * of the file. This can happen in the case of a large direct IO * needing several BIOs and/or write requests to be processed. * 2) The inode size is larger than the amount of data in the zone: |