linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: lyl2019@mail.ustc.edu.cn
To: michael.christie@oracle.com
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] target: Fix a double put in transport_free_session
Date: Thu, 25 Mar 2021 15:48:11 +0800 (GMT+08:00)	[thread overview]
Message-ID: <7378433a.12fee.178685ae745.Coremail.lyl2019@mail.ustc.edu.cn> (raw)
In-Reply-To: <9d02b016-c924-79e3-9593-c073da0c769d@oracle.com>




> -----原始邮件-----
> 发件人: michael.christie@oracle.com
> 发送时间: 2021-03-24 00:28:35 (星期三)
> 收件人: "Lv Yunlong" <lyl2019@mail.ustc.edu.cn>, martin.petersen@oracle.com
> 抄送: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org, linux-kernel@vger.kernel.org
> 主题: Re: [PATCH] target: Fix a double put in transport_free_session
> 
> On 3/22/21 9:58 PM, Lv Yunlong wrote:
> > In transport_free_session, se_nacl is got from se_sess
> > with the initial reference. If se_nacl->acl_sess_list is
> > empty, se_nacl->dynamic_stop is set to true. Then the first
> > target_put_nacl(se_nacl) will drop the initial reference
> > and free se_nacl. Later there is a second target_put_nacl()
> > to put se_nacl. It may cause error in race.
> >> My patch sets se_nacl->dynamic_stop to false to avoid the
> > double put.
> > 
> > Signed-off-by: Lv Yunlong <lyl2019@mail.ustc.edu.cn>
> > ---
> >  drivers/target/target_core_transport.c | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/target/target_core_transport.c b/drivers/target/target_core_transport.c
> > index 5ecb9f18a53d..c266defe694f 100644
> > --- a/drivers/target/target_core_transport.c
> > +++ b/drivers/target/target_core_transport.c
> > @@ -584,8 +584,10 @@ void transport_free_session(struct se_session *se_sess)
> >  		}
> >  		mutex_unlock(&se_tpg->acl_node_mutex);
> >  
> > -		if (se_nacl->dynamic_stop)
> > +		if (se_nacl->dynamic_stop) {
> >  			target_put_nacl(se_nacl);
> > +			se_nacl->dynamic_stop = false;
> > +		}
> >  
> >  		target_put_nacl(se_nacl);
> Could you describe the race a little more?
> 
> Is the race:
> 
> 1. thread1 called core_tpg_check_initiator_node_acl and found the acl.
> sess->se_node_acl is set to the found acl.
> 2. thread2 is running transport_free_session. It now grabs the acl_node_mutex
> and sees se_nacl->acl_sess_list is empty.
> 3. thread2 does the dynamic_stop=true operations in transport_free_session.
> 4. thread1 now calls transport_register_session now adds the sess to acl's
> acl_sess_list.
> 
> Later when the session that thread 1 created is deleted dynamic_stop is still
> set, so we do an extra target_put_nacl?
> 
> I'm not sure your patch will handle this race. When we delete the session thread1
> created dynamic_node_acl is still set, so this:
> 
>                 mutex_lock(&se_tpg->acl_node_mutex);
>                 if (se_nacl->dynamic_node_acl &&
>                     !se_tfo->tpg_check_demo_mode_cache(se_tpg)) {
>                         spin_lock_irqsave(&se_nacl->nacl_sess_lock, flags);
>                         if (list_empty(&se_nacl->acl_sess_list))
>                                 se_nacl->dynamic_stop = true;
> 
> can set dynamic_stop to true again and we can end up doing the extra put still.
> 
> On top of the extra put we also do
> 
> list_del(&se_nacl->acl_list);
> 
> twice so we have to handle that as well.
> 
> Is there also another bug in this code. If someone adds an acl while there is a
> dynamic acl in place core_tpg_add_initiator_node_acl will clear dynamic_node_acl
> but we leave the extra reference, so later when transport_free_session is called
> we will not do the extra put.
> 

Ok, thanks for your answer. According the description above, i think it is a false
positive now.

Thanks.

  reply	other threads:[~2021-03-25  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  2:58 [PATCH] target: Fix a double put in transport_free_session Lv Yunlong
2021-03-23 16:28 ` michael.christie
2021-03-25  7:48   ` lyl2019 [this message]
2021-03-25 17:24     ` Mike Christie
2021-03-26 11:11       ` lyl2019
2021-03-26 12:31 ` Maurizio Lombardi
2021-03-26 16:24   ` Mike Christie

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=7378433a.12fee.178685ae745.Coremail.lyl2019@mail.ustc.edu.cn \
    --to=lyl2019@mail.ustc.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michael.christie@oracle.com \
    --cc=target-devel@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).