linux-kernel - [PATCH] fs: jffs2: Remove utf8 from printk string

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]

Date:	Fri,  6 Feb 2015 15:19:03 +0100
From:	Rasmus Villemoes <linux@...musvillemoes.dk>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Rasmus Villemoes <linux@...musvillemoes.dk>,
	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: [PATCH] fs: jffs2: Remove utf8 from printk string

Any non-ascii characters are escaped before being show to user-space,
so this shows up as

jffs2: version 2.2. (NAND) \xffffffc2\xffffffa9\xffffffa9 2001-2006 Red Hat, Inc.

(I have no idea why the second byte is repeated.) Replace with a
widely used ascii replacement.

Signed-off-by: Rasmus Villemoes <linux@...musvillemoes.dk>
---
Actually, I don't see the value in printing a copyright notice to the
kernel log, especially since it's out-of-sync with the one at the top
of the file.

 fs/jffs2/super.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/jffs2/super.c b/fs/jffs2/super.c
index 0918f0e2e266..471b674b6f8a 100644
--- a/fs/jffs2/super.c
+++ b/fs/jffs2/super.c
@@ -382,7 +382,7 @@ static int __init init_jffs2_fs(void)
 #ifdef CONFIG_JFFS2_SUMMARY
 	       " (SUMMARY) "
 #endif
-	       " © 2001-2006 Red Hat, Inc.\n");
+	       " (c) 2001-2006 Red Hat, Inc.\n");
 
 	jffs2_inode_cachep = kmem_cache_create("jffs2_i",
 					     sizeof(struct jffs2_inode_info),
-- 
2.1.3

--
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/