[PATCH] fs: fix typos in comments

[PATCH] fs: fix typos in comments

[Hemanth Selam]

Fix typos in comments, reported by scripts/checkpatch.pl using the
misspelling list in scripts/spelling.txt.  Only touches comments, no code
changes.

Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
 fs/aio.c                | 4 ++--
 fs/coredump.c           | 2 +-
 fs/fs-writeback.c       | 6 +++---
 fs/inode.c              | 2 +-
 fs/namespace.c          | 2 +-
 include/linux/fs.h      | 2 +-
 include/uapi/linux/fs.h | 2 +-
 7 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/fs/aio.c b/fs/aio.c
index d78acc69f487..685525aef7a3 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -936,7 +936,7 @@ static int kill_ioctx(struct mm_struct *mm, struct kioctx *ctx,
 
 /*
  * exit_aio: called when the last user of mm goes away.  At this point, there is
- * no way for any new requests to be submited or any of the io_* syscalls to be
+ * no way for any new requests to be submitted or any of the io_* syscalls to be
  * called on the context.
  *
  * There may be outstanding kiocbs, but free_ioctx() will explicitly wait on
@@ -1280,7 +1280,7 @@ static long aio_read_events_ring(struct kioctx *ctx,
 	 * The mutex can block and wake us up and that will cause
 	 * wait_event_interruptible_hrtimeout() to schedule without sleeping
 	 * and repeat. This should be rare enough that it doesn't cause
-	 * peformance issues. See the comment in read_events() for more detail.
+	 * performance issues. See the comment in read_events() for more detail.
 	 */
 	sched_annotate_sleep();
 	mutex_lock(&ctx->ring_lock);
diff --git a/fs/coredump.c b/fs/coredump.c
index ac3cd74808c6..2e8f247efd65 100644
--- a/fs/coredump.c
+++ b/fs/coredump.c
@@ -1047,7 +1047,7 @@ static bool coredump_write(struct core_name *cn,
 	cn->core_dumped = binfmt->core_dump(cprm);
 	/*
 	 * Ensures that file size is big enough to contain the current
-	 * file postion. This prevents gdb from complaining about
+	 * file position. This prevents gdb from complaining about
 	 * a truncated file if the last "write" to the file was
 	 * dump_skip.
 	 */
diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index e744f9f9d43f..f303936446da 100644
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -233,7 +233,7 @@ void wb_wait_for_completion(struct wb_completion *done)
  * Parameters for foreign inode detection, see wbc_detach_inode() to see
  * how they're used.
  *
- * These paramters are inherently heuristical as the detection target
+ * These parameters are inherently heuristical as the detection target
  * itself is fuzzy.  All we want to do is detaching an inode from the
  * current owner if it's being written to by some other cgroups too much.
  *
@@ -248,7 +248,7 @@ void wb_wait_for_completion(struct wb_completion *done)
  * to 16 slots.  To avoid tiny writes from swinging the decision too much,
  * writes smaller than 1/8 of avg size are ignored.
  */
-#define WB_FRN_TIME_SHIFT	13	/* 1s = 2^13, upto 8 secs w/ 16bit */
+#define WB_FRN_TIME_SHIFT	13	/* 1s = 2^13, up to 8 secs w/ 16bit */
 #define WB_FRN_TIME_AVG_SHIFT	3	/* avg = avg * 7/8 + new * 1/8 */
 #define WB_FRN_TIME_CUT_DIV	8	/* ignore rounds < avg / 8 */
 #define WB_FRN_TIME_PERIOD	(2 * (1 << WB_FRN_TIME_SHIFT))	/* 2s */
@@ -259,7 +259,7 @@ void wb_wait_for_completion(struct wb_completion *done)
 #define WB_FRN_HIST_THR_SLOTS	(WB_FRN_HIST_SLOTS / 2)
 					/* if foreign slots >= 8, switch */
 #define WB_FRN_HIST_MAX_SLOTS	(WB_FRN_HIST_THR_SLOTS / 2 + 1)
-					/* one round can affect upto 5 slots */
+					/* one round can affect up to 5 slots */
 #define WB_FRN_MAX_IN_FLIGHT	1024	/* don't queue too many concurrently */
 
 /*
diff --git a/fs/inode.c b/fs/inode.c
index ba7da39be4a3..817fd5254495 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -1771,7 +1771,7 @@ EXPORT_SYMBOL(ilookup);
  * function must never block --- find_inode() can block in
  * __wait_on_freeing_inode() --- or when the caller can not increment
  * the reference count because the resulting iput() might cause an
- * inode eviction.  The tradeoff is that the @match funtion must be
+ * inode eviction.  The tradeoff is that the @match function must be
  * very carefully implemented.
  */
 struct inode *find_inode_nowait(struct super_block *sb,
diff --git a/fs/namespace.c b/fs/namespace.c
index 1ecd96c918b3..f45233f425f7 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -4115,7 +4115,7 @@ int path_mount(const char *dev_name, const struct path *path,
 	if (flags & SB_MANDLOCK)
 		warn_mandlock();
 
-	/* Default to relatime unless overriden */
+	/* Default to relatime unless overridden */
 	if (!(flags & MS_NOATIME))
 		mnt_flags |= MNT_RELATIME;
 
diff --git a/include/linux/fs.h b/include/linux/fs.h
index f9d1e05e8ae6..05d05bb9c951 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1436,7 +1436,7 @@ static inline void i_gid_write(struct inode *inode, gid_t gid)
  * @idmap: idmap of the mount the inode was found from
  * @inode: inode to map
  *
- * Return: whe inode's i_uid mapped down according to @idmap.
+ * Return: the inode's i_uid mapped down according to @idmap.
  * If the inode's i_uid has no mapping INVALID_VFSUID is returned.
  */
 static inline vfsuid_t i_uid_into_vfsuid(struct mnt_idmap *idmap,
diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h
index 34c6f219462a..a46c33692aa2 100644
--- a/include/uapi/linux/fs.h
+++ b/include/uapi/linux/fs.h
@@ -88,7 +88,7 @@ struct fstrim_range {
  * We include a length field because some filesystems (vfat) have an identifier
  * that we do want to expose as a UUID, but doesn't have the standard length.
  *
- * We use a fixed size buffer beacuse this interface will, by fiat, never
+ * We use a fixed size buffer because this interface will, by fiat, never
  * support "UUIDs" longer than 16 bytes; we don't want to force all downstream
  * users to have to deal with that.
  */
-- 
2.48.1

Re: [PATCH] fs: fix typos in comments

[Jan Kara]

On Mon 07-09-26 12:02:52, Hemanth Selam wrote:
> Fix typos in comments, reported by scripts/checkpatch.pl using the
> misspelling list in scripts/spelling.txt.  Only touches comments, no code
> changes.
> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>

Looks good. Feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  fs/aio.c                | 4 ++--
>  fs/coredump.c           | 2 +-
>  fs/fs-writeback.c       | 6 +++---
>  fs/inode.c              | 2 +-
>  fs/namespace.c          | 2 +-
>  include/linux/fs.h      | 2 +-
>  include/uapi/linux/fs.h | 2 +-
>  7 files changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/fs/aio.c b/fs/aio.c
> index d78acc69f487..685525aef7a3 100644
> --- a/fs/aio.c
> +++ b/fs/aio.c
> @@ -936,7 +936,7 @@ static int kill_ioctx(struct mm_struct *mm, struct kioctx *ctx,
>  
>  /*
>   * exit_aio: called when the last user of mm goes away.  At this point, there is
> - * no way for any new requests to be submited or any of the io_* syscalls to be
> + * no way for any new requests to be submitted or any of the io_* syscalls to be
>   * called on the context.
>   *
>   * There may be outstanding kiocbs, but free_ioctx() will explicitly wait on
> @@ -1280,7 +1280,7 @@ static long aio_read_events_ring(struct kioctx *ctx,
>  	 * The mutex can block and wake us up and that will cause
>  	 * wait_event_interruptible_hrtimeout() to schedule without sleeping
>  	 * and repeat. This should be rare enough that it doesn't cause
> -	 * peformance issues. See the comment in read_events() for more detail.
> +	 * performance issues. See the comment in read_events() for more detail.
>  	 */
>  	sched_annotate_sleep();
>  	mutex_lock(&ctx->ring_lock);
> diff --git a/fs/coredump.c b/fs/coredump.c
> index ac3cd74808c6..2e8f247efd65 100644
> --- a/fs/coredump.c
> +++ b/fs/coredump.c
> @@ -1047,7 +1047,7 @@ static bool coredump_write(struct core_name *cn,
>  	cn->core_dumped = binfmt->core_dump(cprm);
>  	/*
>  	 * Ensures that file size is big enough to contain the current
> -	 * file postion. This prevents gdb from complaining about
> +	 * file position. This prevents gdb from complaining about
>  	 * a truncated file if the last "write" to the file was
>  	 * dump_skip.
>  	 */
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index e744f9f9d43f..f303936446da 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -233,7 +233,7 @@ void wb_wait_for_completion(struct wb_completion *done)
>   * Parameters for foreign inode detection, see wbc_detach_inode() to see
>   * how they're used.
>   *
> - * These paramters are inherently heuristical as the detection target
> + * These parameters are inherently heuristical as the detection target
>   * itself is fuzzy.  All we want to do is detaching an inode from the
>   * current owner if it's being written to by some other cgroups too much.
>   *
> @@ -248,7 +248,7 @@ void wb_wait_for_completion(struct wb_completion *done)
>   * to 16 slots.  To avoid tiny writes from swinging the decision too much,
>   * writes smaller than 1/8 of avg size are ignored.
>   */
> -#define WB_FRN_TIME_SHIFT	13	/* 1s = 2^13, upto 8 secs w/ 16bit */
> +#define WB_FRN_TIME_SHIFT	13	/* 1s = 2^13, up to 8 secs w/ 16bit */
>  #define WB_FRN_TIME_AVG_SHIFT	3	/* avg = avg * 7/8 + new * 1/8 */
>  #define WB_FRN_TIME_CUT_DIV	8	/* ignore rounds < avg / 8 */
>  #define WB_FRN_TIME_PERIOD	(2 * (1 << WB_FRN_TIME_SHIFT))	/* 2s */
> @@ -259,7 +259,7 @@ void wb_wait_for_completion(struct wb_completion *done)
>  #define WB_FRN_HIST_THR_SLOTS	(WB_FRN_HIST_SLOTS / 2)
>  					/* if foreign slots >= 8, switch */
>  #define WB_FRN_HIST_MAX_SLOTS	(WB_FRN_HIST_THR_SLOTS / 2 + 1)
> -					/* one round can affect upto 5 slots */
> +					/* one round can affect up to 5 slots */
>  #define WB_FRN_MAX_IN_FLIGHT	1024	/* don't queue too many concurrently */
>  
>  /*
> diff --git a/fs/inode.c b/fs/inode.c
> index ba7da39be4a3..817fd5254495 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -1771,7 +1771,7 @@ EXPORT_SYMBOL(ilookup);
>   * function must never block --- find_inode() can block in
>   * __wait_on_freeing_inode() --- or when the caller can not increment
>   * the reference count because the resulting iput() might cause an
> - * inode eviction.  The tradeoff is that the @match funtion must be
> + * inode eviction.  The tradeoff is that the @match function must be
>   * very carefully implemented.
>   */
>  struct inode *find_inode_nowait(struct super_block *sb,
> diff --git a/fs/namespace.c b/fs/namespace.c
> index 1ecd96c918b3..f45233f425f7 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -4115,7 +4115,7 @@ int path_mount(const char *dev_name, const struct path *path,
>  	if (flags & SB_MANDLOCK)
>  		warn_mandlock();
>  
> -	/* Default to relatime unless overriden */
> +	/* Default to relatime unless overridden */
>  	if (!(flags & MS_NOATIME))
>  		mnt_flags |= MNT_RELATIME;
>  
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index f9d1e05e8ae6..05d05bb9c951 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -1436,7 +1436,7 @@ static inline void i_gid_write(struct inode *inode, gid_t gid)
>   * @idmap: idmap of the mount the inode was found from
>   * @inode: inode to map
>   *
> - * Return: whe inode's i_uid mapped down according to @idmap.
> + * Return: the inode's i_uid mapped down according to @idmap.
>   * If the inode's i_uid has no mapping INVALID_VFSUID is returned.
>   */
>  static inline vfsuid_t i_uid_into_vfsuid(struct mnt_idmap *idmap,
> diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h
> index 34c6f219462a..a46c33692aa2 100644
> --- a/include/uapi/linux/fs.h
> +++ b/include/uapi/linux/fs.h
> @@ -88,7 +88,7 @@ struct fstrim_range {
>   * We include a length field because some filesystems (vfat) have an identifier
>   * that we do want to expose as a UUID, but doesn't have the standard length.
>   *
> - * We use a fixed size buffer beacuse this interface will, by fiat, never
> + * We use a fixed size buffer because this interface will, by fiat, never
>   * support "UUIDs" longer than 16 bytes; we don't want to force all downstream
>   * users to have to deal with that.
>   */
> -- 
> 2.48.1
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

Re: [PATCH] fs: fix typos in comments

[Christian Brauner]

On Mon, 07 Sep 2026 12:02:52 +0530, Hemanth Selam wrote:
> fs: fix typos in comments

Applied to the vfs-7.4.misc branch of the vfs/vfs.git tree.
Patches in the vfs-7.4.misc branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-7.4.misc

[1/1] fs: fix typos in comments
      https://git.kernel.org/vfs/vfs/c/21a62663d473