linux-kernel - [PATCH] fs: configfs: Fix sentence with a better word in the file symlink.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: <20210205123235.1365780-1-unixbhaskar@gmail.com>
Date:   Fri,  5 Feb 2021 18:02:35 +0530
From:   Bhaskar Chowdhury <unixbhaskar@...il.com>
To:     jlbec@...lplan.org, hch@....de, linux-kernel@...r.kernel.org
Cc:     rdunlap@...radead.org, Bhaskar Chowdhury <unixbhaskar@...il.com>
Subject: [PATCH] fs: configfs: Fix sentence with a better word in the file symlink.c


s/fucking/wonderful/

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
 fs/configfs/symlink.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/configfs/symlink.c b/fs/configfs/symlink.c
index cb61467478ca..26676e27346b 100644
--- a/fs/configfs/symlink.c
+++ b/fs/configfs/symlink.c
@@ -169,7 +169,7 @@ int configfs_symlink(struct inode *dir, struct dentry *dentry, const char *symna
 	 * link(2) and symlink(2) - they wanted the target resolved
 	 * at syscall time (as link(2) would've done), be a directory
 	 * (which link(2) would've refused to do) *AND* be a deep
-	 * fucking magic, making the target busy from rmdir POV.
+	 * wonderful magic, making the target busy from rmdir POV.
 	 * symlink(2) is nothing of that sort, and the locking it
 	 * gets matches the normal symlink(2) semantics.  Without
 	 * attempts to resolve the target (which might very well
--
2.30.0