From: Kienan Stewart <kstewart@efficios.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-janitors@vger.kernel.org,
Kienan Stewart <kstewart@efficios.com>
Subject: [PATCH] fs/pipe: Correct imprecise wording in comment
Date: Wed, 04 Sep 2024 10:13:29 -0400 [thread overview]
Message-ID: <20240904-pipe-correct_imprecise_wording-v1-1-2b07843472c2@efficios.com> (raw)
The comment inaccurately describes what pipefs is - that is, a file
system.
Signed-off-by: Kienan Stewart <kstewart@efficios.com>
---
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@efficios.com>
next reply other threads:[~2024-09-04 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 14:13 Kienan Stewart [this message]
2024-09-04 14:54 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240904-pipe-correct_imprecise_wording-v1-1-2b07843472c2@efficios.com \
--to=kstewart@efficios.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®