From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org
Subject: [PATCH v2 2/3] vfs: add helper lookup_one_len_noperm()
Date: Fri, 19 May 2017 18:27:20 +0300 [thread overview]
Message-ID: <1495207641-11213-3-git-send-email-amir73il@gmail.com> (raw)
In-Reply-To: <1495207641-11213-1-git-send-email-amir73il@gmail.com>
This is a variant of lookup_one_len() that does not check task
permissions.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
fs/namei.c | 29 +++++++++++++++++++++++++++++
include/linux/namei.h | 1 +
2 files changed, 30 insertions(+)
diff --git a/fs/namei.c b/fs/namei.c
index 263caf0..837da8b 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -2511,6 +2511,35 @@ struct dentry *lookup_one_len(const char *name, struct dentry *base, int len)
EXPORT_SYMBOL(lookup_one_len);
/**
+ * lookup_one_len_noperm - filesystem helper to lookup single pathname component
+ * @name: pathname component to lookup
+ * @base: base directory to lookup from
+ * @len: maximum length @len should be interpreted to
+ *
+ * Note that this routine is purely a helper for filesystem usage and should
+ * not be called by generic code.
+ *
+ * Unlike lookup_one_len, it does not check the task permissions.
+ *
+ * The caller must hold base->i_mutex.
+ */
+struct dentry *lookup_one_len_noperm(const char *name, struct dentry *base,
+ int len)
+{
+ struct qstr this;
+ int err;
+
+ WARN_ON_ONCE(!inode_is_locked(base->d_inode));
+
+ err = lookup_one_len_init(&this, base, name, len);
+ if (err)
+ return ERR_PTR(err);
+
+ return __lookup_hash(&this, base, 0);
+}
+EXPORT_SYMBOL(lookup_one_len);
+
+/**
* lookup_one_len_unlocked - filesystem helper to lookup single pathname component
* @name: pathname component to lookup
* @base: base directory to lookup from
diff --git a/include/linux/namei.h b/include/linux/namei.h
index 8b4794e..afafd38 100644
--- a/include/linux/namei.h
+++ b/include/linux/namei.h
@@ -81,6 +81,7 @@ extern struct dentry *kern_path_locked(const char *, struct path *);
extern int kern_path_mountpoint(int, const char *, struct path *, unsigned int);
extern struct dentry *lookup_one_len(const char *, struct dentry *, int);
+extern struct dentry *lookup_one_len_noperm(const char *, struct dentry *, int);
extern struct dentry *lookup_one_len_unlocked(const char *, struct dentry *, int);
extern int follow_down_one(struct path *);
--
2.7.4
next prev parent reply other threads:[~2017-05-19 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 15:27 [PATCH v2 0/3] ovl: consistent st_ino/d_ino Amir Goldstein
2017-05-19 15:27 ` [PATCH v2 1/3] vfs: factor out lookup_one_len_init() Amir Goldstein
2017-05-19 15:27 ` Amir Goldstein [this message]
2017-05-19 15:27 ` [PATCH v2 3/3] ovl: constant d_ino across copy up Amir Goldstein
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=1495207641-11213-3-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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