ovl: trivial typo fixes in the file inode.c

s/peresistent/persistent/
s/xatts/xattrs/
s/annotaion/annotation/

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>

diff --git a/fs/overlayfs/inode.c b/fs/overlayfs/inode.c
index 8f3c79a..28c7197 100644 (file)
--- a/fs/overlayfs/inode.c
+++ b/fs/overlayfs/inode.c
@@ -115,7 +115,7 @@ static void ovl_map_dev_ino(struct dentry *dentry, struct kstat *stat, int fsid)
                 * high xinobits, so we use high xinobits to partition the
                 * overlay st_ino address space. The high bits holds the fsid
                 * (upper fsid is 0). The lowest xinobit is reserved for mapping
-                * the non-peresistent inode numbers range in case of overflow.
+                * the non-persistent inode numbers range in case of overflow.
                 * This way all overlay inode numbers are unique and use the
                 * overlay st_dev.
                 */
@@ -404,7 +404,7 @@ static bool ovl_can_list(struct super_block *sb, const char *s)
        if (ovl_is_private_xattr(sb, s))
                return false;
 
-       /* List all non-trusted xatts */
+       /* List all non-trusted xattrs */
        if (strncmp(s, XATTR_TRUSTED_PREFIX, XATTR_TRUSTED_PREFIX_LEN) != 0)
                return true;
 
@@ -534,7 +534,7 @@ static const struct address_space_operations ovl_aops = {
  * stackable i_mutex locks according to stack level of the super
  * block instance. An overlayfs instance can never be in stack
  * depth 0 (there is always a real fs below it).  An overlayfs
- * inode lock will use the lockdep annotaion ovl_i_mutex_key[depth].
+ * inode lock will use the lockdep annotation ovl_i_mutex_key[depth].
  *
  * For example, here is a snip from /proc/lockdep_chains after
  * dir_iterate of nested overlayfs: