From: Mike Marciniszyn <mike.marciniszyn-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
To: roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
Subject: [PATCH 0/2] ipath/qib deadlock
Date: Fri, 04 Oct 2013 09:29:01 -0400 [thread overview]
Message-ID: <20131004132821.29162.46169.stgit@phlsvslse11.ph.intel.com> (raw)
These two patches fix flaws that have been
observed in the wild with qib.
The issue has also been code inspected by
Jan Kara in his get_user_pages_unlocked()
patch series.
By using get_user_pages_fast() the dependency
on Jan's patch set has been removed. I can't
find any issue with losing the force in these
use cases.
Jan Kara (2):
IB/ipath: Convert ipath_user_sdma_pin_pages() to use get_user_pages_fast()
IB/qib: Convert qib_user_sdma_pin_pages() to use get_user_pages_fast()
drivers/infiniband/hw/ipath/ipath_user_sdma.c | 7 +------
drivers/infiniband/hw/qib/qib_user_sdma.c | 6 +-----
2 files changed, 2 insertions(+), 11 deletions(-)
--
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-10-04 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 13:29 Mike Marciniszyn [this message]
[not found] ` <20131004132821.29162.46169.stgit-K+u1se/DcYrLESAwzcoQNrvm/XP+8Wra@public.gmane.org>
2013-10-04 13:29 ` [PATCH 1/2] IB/ipath: Convert ipath_user_sdma_pin_pages() to use get_user_pages_fast() Mike Marciniszyn
[not found] ` <20131004132906.29162.1038.stgit-K+u1se/DcYrLESAwzcoQNrvm/XP+8Wra@public.gmane.org>
2013-10-04 13:45 ` Marciniszyn, Mike
2013-10-04 13:29 ` [PATCH 2/2] IB/qib: Convert qib_user_sdma_pin_pages() " Mike Marciniszyn
-- strict thread matches above, loose matches on Subject: below --
2013-10-04 13:28 [PATCH 0/2] ipath/qib deadlock Mike Marciniszyn
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=20131004132821.29162.46169.stgit@phlsvslse11.ph.intel.com \
--to=mike.marciniszyn-h88zbnxc6kdqt0dzr+alfa@public.gmane.org \
--cc=jack-AlSwsSmVLrQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
/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