From: Wu Bo <wubo40@huawei.com>
To: Jeff Layton <jlayton@kernel.org>, <sage@redhat.com>,
<idryomov@gmail.com>
Cc: <ceph-devel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<liuzhiqiang26@huawei.com>, <linfeilong@huawei.com>
Subject: Re: [PATCH V2] fs/ceph:fix double unlock in handle_cap_export()
Date: Wed, 29 Apr 2020 08:46:33 +0800 [thread overview]
Message-ID: <6c99072a-f92b-b7e8-9aef-509d1a9ee985@huawei.com> (raw)
In-Reply-To: <e89bd817c69422c85f1945041dd83fbe8d534805.camel@kernel.org>
On 2020/4/28 22:48, Jeff Layton wrote:
> On Tue, 2020-04-28 at 21:13 +0800, Wu Bo wrote:
>> if the ceph_mdsc_open_export_target_session() return fails,
>> should add a lock to avoid twice unlocking.
>> Because the lock will be released at the retry or out_unlock tag.
>>
>
> The problem looks real, but...
>
>> --
>> v1 -> v2:
>> add spin_lock(&ci->i_ceph_lock) before goto out_unlock tag.
>>
>> Signed-off-by: Wu Bo <wubo40@huawei.com>
>> ---
>> fs/ceph/caps.c | 27 +++++++++++++++------------
>> 1 file changed, 15 insertions(+), 12 deletions(-)
>>
>> diff --git a/fs/ceph/caps.c b/fs/ceph/caps.c
>> index 185db76..414c0e2 100644
>> --- a/fs/ceph/caps.c
>> +++ b/fs/ceph/caps.c
>> @@ -3731,22 +3731,25 @@ static void handle_cap_export(struct inode *inode, struct ceph_mds_caps *ex,
>>
>> /* open target session */
>> tsession = ceph_mdsc_open_export_target_session(mdsc, target);
>> - if (!IS_ERR(tsession)) {
>> - if (mds > target) {
>> - mutex_lock(&session->s_mutex);
>> - mutex_lock_nested(&tsession->s_mutex,
>> - SINGLE_DEPTH_NESTING);
>> - } else {
>> - mutex_lock(&tsession->s_mutex);
>> - mutex_lock_nested(&session->s_mutex,
>> - SINGLE_DEPTH_NESTING);
>> - }
>> - new_cap = ceph_get_cap(mdsc, NULL);
>> - } else {
>> + if (IS_ERR(tsession)) {
>> WARN_ON(1);
>> tsession = NULL;
>> target = -1;
>> + mutex_lock(&session->s_mutex);
>> + spin_lock(&ci->i_ceph_lock);
>> + goto out_unlock;
>
> Why did you make this case goto out_unlock instead of retrying as it did
> before?
>
If the problem occurs, target = -1, and goto retry lable, you need to
call __get_cap_for_mds() or even call __ceph_remove_cap(), and then jump
to out_unlock lable. All I think is unnecessary, goto out_unlock instead
of retrying directly.
Thanks.
Wu Bo
>> + }
>> +
>> + if (mds > target) {
>> + mutex_lock(&session->s_mutex);
>> + mutex_lock_nested(&tsession->s_mutex,
>> + SINGLE_DEPTH_NESTING);
>> + } else {
>> + mutex_lock(&tsession->s_mutex);
>> + mutex_lock_nested(&session->s_mutex,
>> + SINGLE_DEPTH_NESTING);
>> }
>> + new_cap = ceph_get_cap(mdsc, NULL);
>> goto retry;
>>
>> out_unlock:
>
next prev parent reply other threads:[~2020-04-29 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 13:13 Wu Bo
2020-04-28 14:48 ` Jeff Layton
2020-04-29 0:46 ` Wu Bo [this message]
2020-04-29 15:31 ` Jeff Layton
2020-04-30 2:50 ` Yan, Zheng
2020-04-30 4:31 ` Wu Bo
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=6c99072a-f92b-b7e8-9aef-509d1a9ee985@huawei.com \
--to=wubo40@huawei.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--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®