From: "Yan, Zheng" <zyan@redhat.com>
To: Luis Henriques <lhenriques@suse.com>
Cc: Sage Weil <sage@redhat.com>, Ilya Dryomov <idryomov@gmail.com>,
ceph-devel <ceph-devel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ceph: check i_nlink while converting a file handle to dentry
Date: Fri, 19 May 2017 08:41:45 +0800 [thread overview]
Message-ID: <A5330653-F609-4CE7-BE15-AD80C671FAD2@redhat.com> (raw)
In-Reply-To: <20170518164805.jgvxvvvseurrur7e@hermes.olymp>
> On 19 May 2017, at 00:48, Luis Henriques <lhenriques@suse.com> wrote:
>
> On Thu, May 18, 2017 at 09:36:44PM +0800, Yan, Zheng wrote:
>>
>>> On 17 May 2017, at 19:21, Luis Henriques <lhenriques@suse.com> wrote:
>>>
>>> Converting a file handle to a dentry can be done call after the inode
>>> unlink. This means that __fh_to_dentry() requires an extra check to
>>> verify the number of links is not 0.
>>>
>>> The issue can be easily reproduced using xfstest generic/426, which does
>>> something like:
>>>
>>> name_to_handle_at(&fh)
>>> echo 3 > /proc/sys/vm/drop_caches
>>> unlink()
>>> open_by_handle_at(&fh)
>>>
>>> The call to open_by_handle_at() should fail, as the file doesn't exist
>>> anymore.
>>>
>>> Cc: stable@vger.kernel.org
>>> Link: http://tracker.ceph.com/issues/19958
>>> Signed-off-by: Luis Henriques <lhenriques@suse.com>
>>> ---
>>> fs/ceph/export.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/fs/ceph/export.c b/fs/ceph/export.c
>>> index e8f11fa565c5..7df550c13d7f 100644
>>> --- a/fs/ceph/export.c
>>> +++ b/fs/ceph/export.c
>>> @@ -91,6 +91,10 @@ static struct dentry *__fh_to_dentry(struct super_block *sb, u64 ino)
>>> ceph_mdsc_put_request(req);
>>> if (!inode)
>>> return ERR_PTR(-ESTALE);
>>> + if (inode->i_nlink == 0) {
>>> + iput(inode);
>>> + return ERR_PTR(-ESTALE);
>>> + }
>>> }
>>
>> maybe we should do this check in MDS
>
> Thank you for your review. Are you suggesting to do this check *only* in
> the MDS? I guess that's probably a good thing to do too, but don't you
> think it's a good idea to keep it on the client side as well?
Applied. Thanks
Yan, Zheng
>
> Cheers,
> --
> Luís
prev parent reply other threads:[~2017-05-19 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 11:21 Luis Henriques
2017-05-18 13:36 ` Yan, Zheng
2017-05-18 16:48 ` Luis Henriques
2017-05-19 0:41 ` Yan, Zheng [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=A5330653-F609-4CE7-BE15-AD80C671FAD2@redhat.com \
--to=zyan@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=lhenriques@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@redhat.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
all inboxes | Powered by JetHome®