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>

diff --git a/fs/zonefs/file.c b/fs/zonefs/file.c
index fd3a5922f6c34c23c90ccacea1945bf8efcf84be..90e2ad8ee5f4bf0c4d88200a1b7d836dd68b23cc 100644 (file)
--- 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 4dc7f967c861b37d51b936cee0772e043c0bc891..70be0b3dda496625fa879b368dc453824d57d664 100644 (file)
--- 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: