From: Al Viro <viro@zeniv.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [RFC] dget_parent() misuse in xfs_filestream_get_parent()
Date: Fri, 28 Jun 2019 07:00:27 +0100 [thread overview]
Message-ID: <20190628060026.GR17978@ZenIV.linux.org.uk> (raw)
dget_parent() never returns NULL. So this
parent = dget_parent(dentry);
if (!parent)
goto out_dput;
dir = igrab(d_inode(parent));
dput(parent);
out_dput:
is obviously fishy. What is that code trying to do? Is that
"dentry might be a root of disconnected tree, in which case
we want xfs_filestream_get_parent() to return NULL"? If so,
that should be
parent = dget_parent(dentry);
if (parent != dentry)
dir = igrab(d_inode(parent));
dput(parent);
If we want dentry itself, that dir = igrab(...) should be
unconditional. I'm not familiar enough with that code,
and I'd rather not go into YAMassiveSideRTFS, so...
next reply other threads:[~2019-06-28 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 6:00 Al Viro [this message]
2019-07-07 23:22 ` [RFC] dget_parent() misuse in xfs_filestream_get_parent() Dave Chinner
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=20190628060026.GR17978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).