Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Parav Pandit <pandit.parav@gmail.com>
Cc: Dag Moxnes <dag.moxnes@oracle.com>,
	Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Parav Pandit <parav@mellanox.com>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] RDMA/core: Fix race when resolving IP address
Date: Fri, 5 Jul 2019 07:09:50 +0300	[thread overview]
Message-ID: <20190705040950.GO7212@mtr-leonro.mtl.com> (raw)
In-Reply-To: <CAG53R5VQqqr0S6OU+13tcuxcvz922iuqoP-mWbaQERPc48964A@mail.gmail.com>

On Fri, Jul 05, 2019 at 07:49:06AM +0530, Parav Pandit wrote:
> On Fri, Jun 28, 2019 at 2:20 PM Dag Moxnes <dag.moxnes@oracle.com> 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.
> >
> > Signed-off-by: Dag Moxnes <dag.moxnes@oracle.com>
> > Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
> >
> > ---
> > v1 -> v2:
> >    * Modified implementation to improve readability
> > ---
> >  drivers/infiniband/core/addr.c | 9 ++++++---
> >  1 file changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/infiniband/core/addr.c b/drivers/infiniband/core/addr.c
> > index 2f7d141598..51323ffbc5 100644
> > --- a/drivers/infiniband/core/addr.c
> > +++ b/drivers/infiniband/core/addr.c
> > @@ -333,11 +333,14 @@ static int dst_fetch_ha(const struct dst_entry *dst,
> >         if (!n)
> >                 return -ENODATA;
> >
> > -       if (!(n->nud_state & NUD_VALID)) {
> > +       read_lock_bh(&n->lock);
> > +       if (n->nud_state & NUD_VALID) {
> > +               memcpy(dev_addr->dst_dev_addr, n->ha, MAX_ADDR_LEN);
> > +               read_unlock_bh(&n->lock);
> > +       } else {
> > +               read_unlock_bh(&n->lock);
> >                 neigh_event_send(n, NULL);
> >                 ret = -ENODATA;
> > -       } else {
> > -               memcpy(dev_addr->dst_dev_addr, n->ha, MAX_ADDR_LEN);
> >         }
> >
> >         neigh_release(n);
> > --
> > 2.20.1
> >
> Reviewed-by: Parav Pandit <parav@mellanox.com>
>
> A sample trace such as below in commit message would be good to have.
> Or the similar one that you noticed with ARP delete sequence.
>
> neigh_changeaddr()
>   neigh_flush_dev()
>    n->nud_state = NUD_NOARP;
>
> Having some issues with office outlook, so replying via gmail.

Your replies from gmail looks much better when you used Outlook - proper
spacing between quoted text and your reply.

Thanks

  reply	other threads:[~2019-07-05  4:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  8:49 [PATCH v2] RDMA/core: Fix race when resolving IP address Dag Moxnes
2019-07-05  2:19 ` Parav Pandit
2019-07-05  4:09   ` Leon Romanovsky [this message]
2019-07-09 12:26     ` Jason Gunthorpe
2019-07-05  9:03   ` Dag Moxnes

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=20190705040950.GO7212@mtr-leonro.mtl.com \
    --to=leon@kernel.org \
    --cc=dag.moxnes@oracle.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=pandit.parav@gmail.com \
    --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