From: Bart Van Assche <bvanassche@acm.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Leon Romanovsky <leonro@mellanox.com>,
linux-rdma@vger.kernel.org, Li Zhijian <lizhijian@fujitsu.com>,
Hillf Danton <hdanton@sina.com>,
Mike Christie <michael.christie@oracle.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v2 0/3] Fix a use-after-free in the SRP target driver
Date: Wed, 27 Jul 2022 12:34:12 -0700 [thread overview]
Message-ID: <20220727193415.1583860-1-bvanassche@acm.org> (raw)
Hi Jason,
A known issue in the SRP target driver is that a use-after-free is triggered
if an RDMA port is removed while a LIO target port is still associated with
that RDMA port. This patch series fixes that use-after-free.
Thanks,
Bart.
See also:
* Commit 9b64f7d0bb0a ("RDMA/srpt: Postpone HCA removal until after configfs directory removal").
* https://lore.kernel.org/all/17649b9c-7e42-1625-8bc9-8ad333ab771c@fujitsu.com/
Changes compared to v1:
- Left out three BUG_ON() statements.
- Added three WARN_ON_ONCE() statements.
- Removed an unnecessary if (!sport_id) statement block.
Bart Van Assche (3):
RDMA/srpt: Duplicate port name members
RDMA/srpt: Introduce a reference count in struct srpt_device
RDMA/srpt: Fix a use-after-free
drivers/infiniband/ulp/srpt/ib_srpt.c | 148 ++++++++++++++++++--------
drivers/infiniband/ulp/srpt/ib_srpt.h | 18 ++--
2 files changed, 118 insertions(+), 48 deletions(-)
next reply other threads:[~2022-07-27 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 19:34 Bart Van Assche [this message]
2022-07-27 19:34 ` [PATCH v2 1/3] RDMA/srpt: Duplicate port name members Bart Van Assche
2022-07-27 19:34 ` [PATCH v2 2/3] RDMA/srpt: Introduce a reference count in struct srpt_device Bart Van Assche
2022-07-27 19:34 ` [PATCH v2 3/3] RDMA/srpt: Fix a use-after-free Bart Van Assche
2022-07-29 19:46 ` [PATCH v2 0/3] Fix a use-after-free in the SRP target driver Jason Gunthorpe
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=20220727193415.1583860-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=hdanton@sina.com \
--cc=jgg@ziepe.ca \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=michael.christie@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.