From: Mike Christie <michael.christie@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: use-after-free in srpt_enable_tpg()
Date: Thu, 30 Jun 2022 11:40:30 -0500 [thread overview]
Message-ID: <fbaca135-891c-7ff3-d7ac-bd79609849f5@oracle.com> (raw)
In-Reply-To: <ed7e268e-94c5-38b1-286d-e2cb10412334@acm.org>
On 6/27/22 11:37 AM, Bart Van Assche wrote:
> On 6/27/22 00:09, lizhijian@fujitsu.com wrote:
>> So far, I doubt if the previous defect of configfs mentioned in
>> 9b64f7d0b: "(RDMA/srpt: Postpone HCA removal until after configfs
>> directory removal)" has got a better solution. if not, i have no a
>> clear mechanism to avoid it yet.
>>
>> feedbacks are very welcome.
> Mike, are you perhaps aware of any plans to add functions to the LIO core for removing tpg and wwn objects?
>
I don't know any work being done in this area. I was only working
on the refcounting/configfs parts for sessions in those configfs/sysfs
patchsets. However, I think I hit similar issues with the session.
I went around the world with solutions but didn't really like them
so I never pushed the patches for inclusion.
What was the hang caused by 9b64f7d0bb0a?
next prev parent reply other threads:[~2022-06-30 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 7:09 use-after-free in srpt_enable_tpg() lizhijian
2022-06-27 16:37 ` Bart Van Assche
2022-06-30 16:40 ` Mike Christie [this message]
2022-06-30 18:42 ` Bart Van Assche
[not found] ` <20220701015934.1105-1-hdanton@sina.com>
2022-07-02 22:26 ` Bart Van Assche
[not found] ` <20220703021119.1109-1-hdanton@sina.com>
2022-07-03 14:55 ` Bart Van Assche
[not found] ` <20220704001157.1644-1-hdanton@sina.com>
2022-07-05 4:34 ` Bart Van Assche
2022-07-05 12:39 ` Jason Gunthorpe
2022-07-27 3:24 ` lizhijian
[not found] ` <20220705114050.1979-1-hdanton@sina.com>
2022-07-05 16:10 ` Bart Van Assche
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=fbaca135-891c-7ff3-d7ac-bd79609849f5@oracle.com \
--to=michael.christie@oracle.com \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.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).