linux-kernel - [PATCH] Fix incorrect use of loose in fs.c

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081205030806.32225.66382.stgit@marcab.local.tull.net>
Date:	Fri, 05 Dec 2008 14:08:06 +1100
From:	Nick Andrew <nick@...k-andrew.net>
To:	David Howells <dhowells@...hat.com>,
	David Woodhouse <David.Woodhouse@...el.com>,
	David Woodhouse <dwmw2@...radead.org>,
	James Morris <jmorris@...ei.org>,
	Nick Andrew <nick@...k-andrew.net>,
	linux-mtd@...ts.infradead.org
Cc:	<linux-kernel@...r.kernel.org>, Nick Andrew <nick@...k-andrew.net>
Subject: [PATCH] Fix incorrect use of loose in fs.c

Fix incorrect use of loose in fs.c

It should be 'lose', not 'loose'. Also fix a spelling error.

Signed-off-by: Nick Andrew <nick@...k-andrew.net>
---

 fs/jffs2/fs.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


diff --git a/fs/jffs2/fs.c b/fs/jffs2/fs.c
index 249305d..a598de9 100644
--- a/fs/jffs2/fs.c
+++ b/fs/jffs2/fs.c
@@ -386,7 +386,7 @@ int jffs2_remount_fs (struct super_block *sb, int *flags, char *data)
 	/* We stop if it was running, then restart if it needs to.
 	   This also catches the case where it was stopped and this
 	   is just a remount to restart it.
-	   Flush the writebuffer, if neccecary, else we loose it */
+	   Flush the writebuffer, if necessary, else we lose it */
 	if (!(sb->s_flags & MS_RDONLY)) {
 		jffs2_stop_garbage_collect_thread(c);
 		mutex_lock(&c->alloc_sem);


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/