From: Divya Indi <divya.indi@oracle.com>
To: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Jason Gunthorpe <jgg@ziepe.ca>, Kaike Wan <kaike.wan@intel.com>
Cc: "Gerd Rausch" <gerd.rausch@oracle.com>,
"Håkon Bugge" <haakon.bugge@oracle.com>,
"Srinivas Eeda" <srinivas.eeda@oracle.com>,
"Rama Nichanamatlu" <rama.nichanamatlu@oracle.com>,
"Doug Ledford" <dledford@redhat.com>
Subject: Resolving use-after-free in ib_nl_send_msg
Date: Thu, 7 May 2020 11:34:46 -0700 [thread overview]
Message-ID: <1588876487-5781-1-git-send-email-divya.indi@oracle.com> (raw)
[PATCH] IB/sa: Resolving use-after-free in ib_nl_send_msg.
Hi,
This patch is in reply to -
https://lkml.org/lkml/2020/4/24/1076
We have a use-after-free possibility in the ibacm code path -
when the timer(ib_nl_request_timeout) kicks in before ib_nl_snd_msg
has completed sending the query out to ibacm via netlink. The timeout
handler ie ib_nl_request_timeout may result in releasing the query while
ib_nl_snd_msg is still accessing query.
Since the issue appears to be specific to the ibacm code path, we are
trying to resolve it for the life cycle of sa_query in the ibacm code path.
Please review the proposed fix ie the patch that follows.
Would appreciate your thoughts and feedback on the same.
Let me know if you have any questions!
Thanks,
Divya
next reply other threads:[~2020-05-07 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 18:34 Divya Indi [this message]
2020-05-07 18:34 ` [PATCH 1/2] IB/sa: " Divya Indi
2020-05-07 19:06 ` Wan, Kaike
2020-05-07 19:36 ` Mark Bloch
2020-05-07 20:16 ` Wan, Kaike
2020-05-07 21:40 ` Mark Bloch
2020-05-11 21:10 ` Divya Indi
2020-05-11 21:06 ` Divya Indi
2020-05-12 11:15 ` Wan, Kaike
2020-05-08 0:08 ` Jason Gunthorpe
2020-05-11 21:26 ` Divya Indi
2020-05-13 15:00 ` Jason Gunthorpe
2020-05-13 21:02 ` Divya Indi
2020-05-19 23:30 ` Divya Indi
2020-05-20 0:10 ` Jason Gunthorpe
[not found] ` <20200508110302.17872-1-hdanton@sina.com>
2020-05-11 21:30 ` Divya Indi
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=1588876487-5781-1-git-send-email-divya.indi@oracle.com \
--to=divya.indi@oracle.com \
--cc=dledford@redhat.com \
--cc=gerd.rausch@oracle.com \
--cc=haakon.bugge@oracle.com \
--cc=jgg@ziepe.ca \
--cc=kaike.wan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rama.nichanamatlu@oracle.com \
--cc=srinivas.eeda@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 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®