From: Davidlohr Bueso <dave@stgolabs.net>
To: dledford@redhat.com, roland@purestorage.com, linux-rdma@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, dave@stgolabs.net,
Davidlohr Bueso <dbueso@suse.de>
Subject: [PATCH] IB/mthca: Fix how mthca_map_user_db() calls gup
Date: Tue, 23 Jan 2018 12:54:59 -0800 [thread overview]
Message-ID: <20180123205459.432-1-dave@stgolabs.net> (raw)
mthca_map_user_db() has two problems regarding the call to
get_user_pages():
(i) It is not done under mmap_sem.
(ii) It is done under the db_table mutex, which protects all
database related operations. Should any of these be called
under mmap_sem, we get an ABBA deadlock. In addition, gup can
be performance intensive, which could contend other mapping/
unmapping ops.
To fix this, we can drop the mutex while doing a gup_fast(),
once done, recheck to see the page was mapped while we didn't
hold the mutex, and exit out with the corresponding housekeeping.
Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
---
- Compile tested only.
- 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.
drivers/infiniband/hw/mthca/mthca_memfree.c | 20 +++++++++++++++++++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/mthca/mthca_memfree.c b/drivers/infiniband/hw/mthca/mthca_memfree.c
index c6fe89d79248..046871878a02 100644
--- a/drivers/infiniband/hw/mthca/mthca_memfree.c
+++ b/drivers/infiniband/hw/mthca/mthca_memfree.c
@@ -472,9 +472,27 @@ int mthca_map_user_db(struct mthca_dev *dev, struct mthca_uar *uar,
goto out;
}
- ret = get_user_pages(uaddr & PAGE_MASK, 1, FOLL_WRITE, pages, NULL);
+ mutex_unlock(&db_tab->mutex);
+
+ ret = get_user_pages_fast(uaddr & PAGE_MASK, 1, FOLL_WRITE, pages);
if (ret < 0)
+ return ret;
+
+ mutex_lock(&db_tab->mutex);
+
+ if (db_tab->page[i].refcount >= MTHCA_DB_REC_PER_PAGE ||
+ (db_tab->page[i].uvirt && db_tab->page[i].uvirt != uaddr)) {
+ put_page(pages[0]);
+ ret = -EINVAL;
goto out;
+ }
+
+ /* page was already mapped by another task while we were doing gup */
+ if (db_tab->page[i].refcount) {
+ put_page(pages[0]);
+ ++db_tab->page[i].refcount;
+ goto out;
+ }
sg_set_page(&db_tab->page[i].mem, pages[0], MTHCA_ICM_PAGE_SIZE,
uaddr & ~PAGE_MASK);
--
2.13.6
next reply other threads:[~2018-01-23 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 20:54 Davidlohr Bueso [this message]
[not found] ` <20180123205459.432-1-dave-h16yJtLeMjHk1uMJSBkQmQ@public.gmane.org>
2018-01-25 16:34 ` [PATCH] IB/mthca: Fix how mthca_map_user_db() calls gup Doug Ledford
2018-01-25 17:50 ` Jason Gunthorpe
2018-01-25 18:06 ` Doug Ledford
[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=20180123205459.432-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=dledford@redhat.com \
--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