From: Charles Mirabile <cmirabil@redhat.com>
To: brauner@kernel.org
Cc: hpa@zytor.com, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, luto@kernel.org,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk,
Charles Mirabile <cmirabil@redhat.com>
Subject: [PATCH] Re: [PATCH] vfs: relax linkat() AT_EMPTY_PATH - aka flink() - requirements
Date: Fri, 12 Apr 2024 15:22:17 -0400 [thread overview]
Message-ID: <20240412192217.4172554-1-cmirabil@redhat.com> (raw)
In-Reply-To: <20240412-vegetarisch-installieren-1152433bd1a7@brauner>
this is a nitpic, but if you are going to touch the comment on
line 4654 I think you should fix the spelling mistake :^)
handlink -> hard link
Signed-off-by: Charles Mirabile <cmirabil@redhat.com>
---
fs/namei.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/namei.c b/fs/namei.c
index 6d5b3f0d6ad3..9b806b108ed0 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -4651,7 +4651,7 @@ int do_linkat(int olddfd, struct filename *old, int newdfd,
* To use null names we require CAP_DAC_READ_SEARCH or
* that the open-time creds of the dfd matches current.
* This ensures that not everyone will be able to create
- * handlink using the passed file descriptor.
+ * hard links using the passed file descriptor.
*/
if (flags & AT_EMPTY_PATH)
how |= LOOKUP_LINKAT_EMPTY;
--
2.44.0
prev parent reply other threads:[~2024-04-12 19:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 0:10 [PATCH] vfs: relax linkat() AT_EMPTY_PATH - aka flink() - requirements Linus Torvalds
2024-04-11 0:20 ` Linus Torvalds
2024-04-11 2:39 ` Linus Torvalds
2024-04-11 9:04 ` Christian Brauner
2024-04-11 12:25 ` Christian Brauner
2024-04-11 16:21 ` Linus Torvalds
2024-04-12 8:56 ` Christian Brauner
2024-04-11 16:15 ` Linus Torvalds
2024-04-11 16:44 ` Charles Mirabile
2024-04-11 17:29 ` Charles Mirabile
2024-04-11 17:35 ` Charles Mirabile
2024-04-11 18:13 ` Linus Torvalds
2024-04-11 19:34 ` Linus Torvalds
2024-04-12 7:45 ` Christian Brauner
2024-04-12 15:36 ` Linus Torvalds
2024-04-11 20:08 ` Charles Mirabile
2024-04-11 20:22 ` Linus Torvalds
2024-04-12 6:44 ` Christian Brauner
2024-04-12 6:41 ` Christian Brauner
2024-04-12 9:07 ` Christian Brauner
2024-04-12 17:43 ` Linus Torvalds
2024-04-13 9:41 ` Christian Brauner
2024-04-13 15:16 ` Christian Brauner
2024-04-13 17:07 ` Linus Torvalds
2024-04-12 19:22 ` Charles Mirabile [this message]
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=20240412192217.4172554-1-cmirabil@redhat.com \
--to=cmirabil@redhat.com \
--cc=brauner@kernel.org \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=torvalds@linux-foundation.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