From: Guo Chao <yan@linux.vnet.ibm.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] fs/namei: fix some typos
Date: Fri, 29 Jun 2012 11:29:18 +0800 [thread overview]
Message-ID: <1340940558-9893-3-git-send-email-yan@linux.vnet.ibm.com> (raw)
In-Reply-To: <1340940558-9893-1-git-send-email-yan@linux.vnet.ibm.com>
Signed-off-by: Guo Chao <yan@linux.vnet.ibm.com>
---
fs/namei.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index 05b9053..adf61b3 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -1080,7 +1080,7 @@ static struct dentry *lookup_dcache(struct qstr *name, struct dentry *dir,
/*
* Call i_op->lookup on the dentry. The dentry must be negative but may be
- * hashed if it was pouplated with DCACHE_NEED_LOOKUP.
+ * hashed if it was populated with DCACHE_NEED_LOOKUP.
*
* dir->d_inode->i_mutex must be held
*/
@@ -1737,7 +1737,7 @@ static inline int lookup_last(struct nameidata *nd, struct path *path)
nd->flags & LOOKUP_FOLLOW);
}
-/* Returns 0 and nd will be valid on success; Retuns error, otherwise. */
+/* Returns 0 and nd will be valid on success; Returns error, otherwise. */
static int path_lookupat(int dfd, const char *name,
unsigned int flags, struct nameidata *nd)
{
@@ -2002,7 +2002,7 @@ static inline int check_sticky(struct inode *dir, struct inode *inode)
* a. be owner of dir, or
* b. be owner of victim, or
* c. have CAP_FOWNER capability
- * 6. If the victim is append-only or immutable we can't do antyhing with
+ * 6. If the victim is append-only or immutable we can't do anything with
* links pointing to it.
* 7. If we were asked to remove a directory and victim isn't one - ENOTDIR.
* 8. If we were asked to remove a non-directory and victim isn't one - EISDIR.
@@ -3018,7 +3018,7 @@ SYSCALL_DEFINE2(mkdir, const char __user *, pathname, umode_t, mode)
* dentry, and if that is true (possibly after pruning the dcache),
* then we drop the dentry now.
*
- * A low-level filesystem can, if it choses, legally
+ * A low-level filesystem can, if it chooses, legally
* do a
*
* if (!d_unhashed(dentry))
@@ -3366,7 +3366,7 @@ SYSCALL_DEFINE5(linkat, int, olddfd, const char __user *, oldname,
/*
* To use null names we require CAP_DAC_READ_SEARCH
* This ensures that not everyone will be able to create
- * handlink using the passed filedescriptor.
+ * hardlink using the passed filedescriptor.
*/
if (flags & AT_EMPTY_PATH) {
if (!capable(CAP_DAC_READ_SEARCH))
--
1.7.9.5
prev parent reply other threads:[~2012-06-29 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 3:29 [PATCH 1/3] Use path_put instead of combination of two functions Guo Chao
2012-06-29 3:29 ` [PATCH 2/3] Check node type at the beginning of mknodat Guo Chao
2012-06-29 3:29 ` Guo Chao [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=1340940558-9893-3-git-send-email-yan@linux.vnet.ibm.com \
--to=yan@linux.vnet.ibm.com \
--cc=linux-fsdevel@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
Powered by JetHome