mirror of
https://github.com/torvalds/linux.git
synced 2026-10-22 23:01:49 +02:00
fs/aio: fix comment typos
Fix two spelling mistakes in code comments. This is a comment only change with no functional impact. Signed-off-by: Mark Sercombe <sercombe.joel.mark@gmail.com> Link: https://patch.msgid.link/20260813231455.558829-1-sercombe.joel.mark@gmail.com Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
This commit is contained in:
parent
270b35c987
commit
8f0aec91bb
4
fs/aio.c
4
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);
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user