From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: Bart Van Assche <bvanassche@acm.org>, Hillf Danton <hdanton@sina.com>
Cc: Mike Christie <michael.christie@oracle.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: Wed, 27 Jul 2022 03:24:36 +0000 [thread overview]
Message-ID: <63b37fec-3b32-dbd0-175f-ab7f6aa3dbdf@fujitsu.com> (raw)
In-Reply-To: <a671867f-153c-75a4-0f58-8dcb0d4f9c19@acm.org>
Bart,
On 05/07/2022 12:34, Bart Van Assche wrote:
>
> A potential solution could be to decouple the lifetimes of the data structures used for configfs (struct se_wwn and struct srpt_tpg) and the data structures associated with RDMA objects (struct srpt_port). If nobody else beats me to this I will try to find the time to implement this approach.
I saw your approach this morning, i will have a look and tests later.
Thanks
Zhijian
next prev parent reply other threads:[~2022-07-27 3:24 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
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 [this message]
[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=63b37fec-3b32-dbd0-175f-ab7f6aa3dbdf@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=bvanassche@acm.org \
--cc=hdanton@sina.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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).