public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	roland@purestorage.com, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH] IB/mthca: Fix how mthca_map_user_db() calls gup
Date: Thu, 25 Jan 2018 13:06:24 -0500	[thread overview]
Message-ID: <1516903584.27592.183.camel@redhat.com> (raw)
In-Reply-To: <20180125175048.GG10706@ziepe.ca>

[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]

On Thu, 2018-01-25 at 10:50 -0700, Jason Gunthorpe wrote:
> On Thu, Jan 25, 2018 at 11:34:23AM -0500, Doug Ledford wrote:
> > > - Should I be wrong about no callers already holding mmap_sem,
> > >   I still think calling gup without the mutex makes sense for
> > >   improved paralellism. Now, if callers can hold the mmap_sem,
> > >   it's wrong to do copy_from_user right before calling mthca_map_user_db.
> > 
> > So, if I understand you correctly, we (well, you and Al would be more
> > correct, we haven't looked into the situation yet, so Mellanox people
> > that worked on this in the day might now, or someone taking the time to
> > research it could find out) don't have a clear understanding of all the
> > conditions this function is called under, and so we actually don't know
> > what the best way forward is to fix it?
> 
> I looked at it enough to be confident that mthca_map_user_db is never
> called with mmap_sem held.
> 
> Also pretty confident that mthca_unmap_user_db is never called with
> mmap_sem.
> 
> So how about just grabbing mmap_sem around the call to get_user_pages
> and no other changes?

Since the original post was referred to an ABBA deadlock, wouldn't we
have to drop db_tab->mutex, then grab both in the proper order?

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-01-25 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 20:54 [PATCH] IB/mthca: Fix how mthca_map_user_db() calls gup Davidlohr Bueso
     [not found] ` <20180123205459.432-1-dave-h16yJtLeMjHk1uMJSBkQmQ@public.gmane.org>
2018-01-25 16:34   ` Doug Ledford
2018-01-25 17:50     ` Jason Gunthorpe
2018-01-25 18:06       ` Doug Ledford [this message]
     [not found]         ` <1516903584.27592.183.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-25 18:53           ` Jason Gunthorpe
     [not found]             ` <20180125185330.GH10706-uk2M96/98Pc@public.gmane.org>
2018-01-25 19:27               ` Davidlohr Bueso
2018-01-26 15:44                 ` Doug Ledford

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=1516903584.27592.183.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=dave@stgolabs.net \
    --cc=dbueso@suse.de \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=roland@purestorage.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