linux-kernel - [PATCH 1/1 linux-next] vfs: fix comment typos

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Thu, 24 Nov 2016 19:50:39 +0100
From:   Fabian Frederick <fabf@...net.be>
To:     Alexander Viro <viro@...iv.linux.org.uk>
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        fabf@...net.be
Subject: [PATCH 1/1 linux-next] vfs: fix comment typos

Signed-off-by: Fabian Frederick <fabf@...net.be>
---
 fs/namei.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/namei.c b/fs/namei.c
index 1669c93d..ca829b4 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -3119,12 +3119,12 @@ static int lookup_open(struct nameidata *nd, struct path *path,
 	}
 
 	/*
-	 * Checking write permission is tricky, bacuse we don't know if we are
+	 * Checking write permission is tricky, because we don't know if we are
 	 * going to actually need it: O_CREAT opens should work as long as the
 	 * file exists.  But checking existence breaks atomicity.  The trick is
 	 * to check access and if not granted clear O_CREAT from the flags.
 	 *
-	 * Another problem is returing the "right" error value (e.g. for an
+	 * Another problem is returning the "right" error value (e.g. for an
 	 * O_EXCL open we want to return EEXIST not EROFS).
 	 */
 	if (open_flag & O_CREAT) {
-- 
2.7.4