diff mbox series

fs: aio: Fix a typo

Message ID 20210607062049.189901-1-lijian_8010a29@163.com (mailing list archive)
State New, archived
Headers show
Series fs: aio: Fix a typo | expand

Commit Message

lijian_8010a29@163.com June 7, 2021, 6:20 a.m. UTC
From: lijian <lijian@yulong.com>

Change 'submited' to 'submitted', and
change 'peformance' to 'performance'.

Signed-off-by: lijian <lijian@yulong.com>
---
 fs/aio.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff mbox series

Patch

diff --git a/fs/aio.c b/fs/aio.c
index e499cbcef117..2ddcabcaa370 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -850,7 +850,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
@@ -1181,7 +1181,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);