fanotify: Fix spelling mistake "enforecement" -> "enforcement"

There is a spelling mistake in a comment. Fix it.

Signed-off-by: Ethan Carter Edwards <ethan@ethancedwards.com>
Link: https://patch.msgid.link/20260418-fanotify-typo-v1-1-03ea48cb44ba@ethancedwards.com
Signed-off-by: Jan Kara <jack@suse.cz>

diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c
index bfe884d624e7b2cfd4825adb35e26af437128c06..38290b9c07f7b465ea65f481a83a8d2246519e33 100644 (file)
--- a/fs/notify/fanotify/fanotify.c
+++ b/fs/notify/fanotify/fanotify.c
@@ -457,7 +457,7 @@ static int fanotify_encode_fh(struct fanotify_fh *fh, struct inode *inode,
        /*
         * Unlike file_handle, type and len of struct fanotify_fh are u8.
         * Traditionally, filesystem return handle_type < 0xff, but there
-        * is no enforecement for that in vfs.
+        * is no enforcement for that in vfs.
         */
        BUILD_BUG_ON(MAX_HANDLE_SZ > 0xff || FILEID_INVALID > 0xff);
        if (type <= 0 || type >= FILEID_INVALID || fh_len != dwords << 2)