linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: "Torvalds, Linus" <torvalds@linux-foundation.org>
Cc: linux-rdma <linux-rdma@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Gunthorpe, Jason" <jgg@ziepe.ca>
Subject: [PULL REQUEST] Please pull rdma.git
Date: Fri, 30 Aug 2019 11:42:36 -0400	[thread overview]
Message-ID: <cef8e627336f4a85b2860fd9bde25c71aef7e194.camel@redhat.com> (raw)

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

Hi Linus,

*Much* calmer week this week.  Just one -rc patch queued up.  The way
the siw driver was locking around the traversal of the list of ipv6
addresses on a device was causing a scheduling while atomic issue. 
Bernard straightened it out by using the rtnl_lock.

Here's the boiler plate:

The following changes since commit c536277e0db1ad2e9fbb9dfd940c3565a14d9c52:

  RDMA/siw: Fix 64/32bit pointer inconsistency (2019-08-23 12:08:27 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-linus

for you to fetch changes up to 531a64e4c35bb9844b0cf813a6c9a87e00be05ff:

  RDMA/siw: Fix IPv6 addr_list locking (2019-08-28 10:29:19 -0400)

----------------------------------------------------------------
Pull request for 5.3-rc6

- Fix locking on list traversal (siw)

Signed-off-by: Doug Ledford <dledford@redhat.com>

----------------------------------------------------------------
Bernard Metzler (1):
      RDMA/siw: Fix IPv6 addr_list locking

 drivers/infiniband/sw/siw/siw_cm.c | 31 ++++++++++++++++++++-----------
 1 file changed, 20 insertions(+), 11 deletions(-)

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    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:[~2019-08-30 15:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 15:42 Doug Ledford [this message]
2019-08-30 16:40 ` [PULL REQUEST] Please pull rdma.git pr-tracker-bot
     [not found] <5b0aa103f6007e1887f9b2cacaec8015834589b8.camel@xsintricity.com>
2019-08-23 19:14 ` Doug Ledford
  -- strict thread matches above, loose matches on Subject: below --
2019-08-14 14:59 Doug Ledford
2019-08-14 18:25 ` pr-tracker-bot
2019-08-19 10:08 ` Geert Uytterhoeven
2019-08-19 12:14   ` Jason Gunthorpe
2019-08-19 12:29     ` Geert Uytterhoeven
2019-08-19 12:48       ` Jason Gunthorpe
2019-08-02 14:39 Doug Ledford
2019-08-02 22:10 ` pr-tracker-bot
2019-06-21 19:42 Doug Ledford
2019-06-21 22:35 ` pr-tracker-bot
2018-12-13 16:56 Doug Ledford
2018-12-13 21:15 ` pr-tracker-bot
     [not found] <58466423-c87e-3921-101e-bffab8989fd8@redhat.com>
     [not found] ` <20161117184950.GP4240@leon.nu>
     [not found]   ` <582E089A.3040106@redhat.com>
     [not found]     ` <20161117200203.GQ4240@leon.nu>
2016-11-17 22:24       ` Or Gerlitz
2016-11-18  2:01         ` Doug Ledford
2016-11-19 19:46           ` Or Gerlitz
2016-11-19 23:11             ` Doug Ledford
2016-11-20 12:53               ` Leon Romanovsky

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=cef8e627336f4a85b2860fd9bde25c71aef7e194.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).