mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Mike Christie <michael.christie@oracle.com>
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: Mon, 27 Jun 2022 09:37:21 -0700	[thread overview]
Message-ID: <ed7e268e-94c5-38b1-286d-e2cb10412334@acm.org> (raw)
In-Reply-To: <17649b9c-7e42-1625-8bc9-8ad333ab771c@fujitsu.com>

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?

Thanks,

Bart.

  reply	other threads:[~2022-06-27 16:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  7:09 lizhijian
2022-06-27 16:37 ` Bart Van Assche [this message]
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
     [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=ed7e268e-94c5-38b1-286d-e2cb10412334@acm.org \
    --to=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=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
all inboxes | Powered by JetHome®