The comment inaccurately describes what pipefs is - that is, a file
system.
Signed-off-by: Kienan Stewart <kstewart@xxxxxxxxxxxx>
---
Hi,
while reading through `pipe.c`, I noticed that the comment explaining
why pipefs should not be mounted in user space inaccurately describes
what pipefs is - that is, a file system.
While I understand the original language used in context, I believe
this change increases the legibility of the comment.
thanks,
kienan
---
fs/pipe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/pipe.c b/fs/pipe.c
index 7dff2aa50a6d..9a6dfe39f012 100644
--- a/fs/pipe.c
+++ b/fs/pipe.c
@@ -1427,7 +1427,7 @@ static const struct super_operations pipefs_ops = {
/*
* pipefs should _never_ be mounted by userland - too much of security hassle,
- * no real gain from having the whole whorehouse mounted. So we don't need
+ * no real gain from having the whole file system mounted. So we don't need
* any operations on the root directory. However, we need a non-trivial
* d_name - pipe: will go nicely and kill the special-casing in procfs.
*/
---
base-commit: d5d547aa7b51467b15d9caa86b116f8c2507c72a
change-id: 20240829-pipe-correct_imprecise_wording-d20e370edbc0
Best regards,
--
Kienan Stewart <kstewart@xxxxxxxxxxxx>
