From: Al Viro <viro@ZenIV.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Vineeth Remanan Pillai <vineethp@amazon.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kamatam@amazon.com, aliguori@amazon.com
Subject: Re: [PATCH] namei: revert old behaviour for filename_lookup with LOOKUP_PARENT flag
Date: Thu, 13 Oct 2016 21:26:22 +0100 [thread overview]
Message-ID: <20161013202622.GS19539@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20161013200904.GA23139@infradead.org>
On Thu, Oct 13, 2016 at 01:09:04PM -0700, Christoph Hellwig wrote:
> On Thu, Oct 13, 2016 at 07:58:51PM +0000, Vineeth Remanan Pillai wrote:
> > filename_lookup used to return success for non-existing file when called
> > with LOOKUP_PARENT flag. This behaviour was changed with
> > commit 8bcb77fabd7c ("namei: split off filename_lookupat()
> > with LOOKUP_PARENT")
> >
> > The above patch split parent lookup functionality to a different function
> > filename_parentat and changed all calls to filename_lookup(LOOKUP_PARENT)
> > to the new function filename_parentat. But functions like kern_path which
> > passed the flags directly to filename_lookup regressed due to this.
> >
> > This patch aims to fix the regressed behaviour by calling
> > filename_parentat from filename_lookup if the flags contain LOOKUP_PARENT.
>
> What callers shows te problems? That's probaby were the fix need to got
> in, and even if not that's still part of a good bug report.
Out-of-tree, at a guess... Incidentally, since filename_lookup() is not
exported, it's probably kern_path() that gets used wherever it is.
Depending on the details of what's being attempted, kern_path_locked()
might or might not be the right primitive to use, but I would probably
start with checking if that's what the code in question really wants.
Use:
// kernel_string is an kernel pointer to NUL-terminated array of char
struct path path;
struct dentry *dentry;
dentry = kern_path_locked(kernel_string, &path);
if (IS_ERR(dentry))
// failed while getting the parent, or not a regular last
// component (/, ., .., <something>/., <something>/..)
sod off // no cleanup needed
// now path contains the resolved parent and dentry points to the
// dentry of child, possibly negative; the last component of the
// name can be determined from dentry->d_name. Parent directory
// is locked, making sure that directory entry won't be changed
// until you are done.
if (d_is_really_negative(dentry)) {
// parent exists, but child doesn't
} else {
// child exists
}
// clean up: drop dentry, unlock parent, drop dentry/vfsmount of parent
dput(dentry);
inode_unlock(path.dentry->d_inode);
path_put(&path);
next prev parent reply other threads:[~2016-10-13 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 19:58 [PATCH] namei: revert old behaviour for filename_lookup with LOOKUP_PARENT flag Vineeth Remanan Pillai
2016-10-13 20:06 ` Al Viro
2016-10-13 20:09 ` Christoph Hellwig
2016-10-13 20:26 ` Al Viro [this message]
2016-10-13 20:41 ` Vineeth Remanan Pillai
2016-10-13 20:44 ` Christoph Hellwig
2016-10-13 21:24 ` Al Viro
2016-10-13 22:14 ` Vineeth Remanan Pillai
2016-10-13 23:31 ` Al Viro
2016-10-14 0:02 ` Remanan Pillai, Vineeth
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=20161013202622.GS19539@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=aliguori@amazon.com \
--cc=hch@infradead.org \
--cc=kamatam@amazon.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vineethp@amazon.com \
/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;
as well as URLs for NNTP newsgroup(s).