From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dag Moxnes <dag.moxnes@oracle.com>
Cc: dledford@redhat.com, leon@kernel.org, parav@mellanox.com,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] RDMA/core: Fix race when resolving IP address
Date: Mon, 8 Jul 2019 14:50:25 -0300 [thread overview]
Message-ID: <20190708175025.GA6976@ziepe.ca> (raw)
In-Reply-To: <1562584584-13132-1-git-send-email-dag.moxnes@oracle.com>
On Mon, Jul 08, 2019 at 01:16:24PM +0200, Dag Moxnes wrote:
> Use neighbour lock when copying MAC address from neighbour data struct
> in dst_fetch_ha.
>
> When not using the lock, it is possible for the function to race with
> neigh_update, causing it to copy an invalid MAC address.
>
> It is possible to provoke this error by calling rdma_resolve_addr in a
> tight loop, while deleting the corresponding ARP entry in another tight
> loop.
>
> This will cause the race shown it the following sample trace:
>
> rdma_resolve_addr()
> rdma_resolve_ip()
> addr_resolve()
> addr_resolve_neigh()
> fetch_ha()
> dst_fetch_ha()
> n->nud_state == NUD_VALID
It isn't nud_state that is the problem here, it is the parallel
memcpy's onto ha. I fixed the commit message
This could also have been solved by using the ha_lock, but I don't
think we have a reason to particularly over-optimize this.
> drivers/infiniband/core/addr.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Applied to for-next, thanks
Jason
next prev parent reply other threads:[~2019-07-08 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 11:16 [PATCH v3] RDMA/core: Fix race when resolving IP address Dag Moxnes
2019-07-08 17:50 ` Jason Gunthorpe [this message]
2019-07-08 18:47 ` Dag Moxnes
2019-07-08 19:22 ` Mark Bloch
2019-07-08 19:38 ` Jason Gunthorpe
2019-07-08 20:11 ` Dag Moxnes
2019-07-08 23:05 ` 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=20190708175025.GA6976@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dag.moxnes@oracle.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@mellanox.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