All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: stable@vger.kernel.org
Cc: Anna Schumaker <anna.schumaker@netapp.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: [stable 4.7] xprtrdma: Create common scatterlist fields in rpcrdma_mw
Date: Wed, 7 Sep 2016 15:28:00 -0400	[thread overview]
Message-ID: <EC53244E-DABF-48B9-BD5E-73D04E64C14C@oracle.com> (raw)

Sending again. I have not received ACK/NAK after 1 week.

Please cherry-pick this commit for v4.7 stable:

commit 564471d2f2f1ddaf02119b8759813666db93abba
Author:     Chuck Lever <chuck.lever@oracle.com>
AuthorDate: Wed Jun 29 13:52:21 2016 -0400
Commit:     Anna Schumaker <Anna.Schumaker@Netapp.com>
CommitDate: Mon Jul 11 15:50:43 2016 -0400

   xprtrdma: Create common scatterlist fields in rpcrdma_mw


It addresses a bug in:

commit d7a21c1bed54adcf96e1713019a6ad87e90fbbc3
Author:     Chuck Lever <chuck.lever@oracle.com>
AuthorDate: Mon May 2 14:42:12 2016 -0400
Commit:     Anna Schumaker <Anna.Schumaker@Netapp.com>
CommitDate: Tue May 17 15:48:02 2016 -0400

   xprtrdma: Reset MRs in frwr_op_unmap_sync()

Which causes DMAR errors and an oops when using NFS/RDMA on
x86_64 systems where the iommu is enabled.

This was reported via IRC, I don't have the reporter's e-mail
address. I was able to reproduce the issue, and confirm that
564471d2f2f1 fixes the problem on v4.7.2.

(The actual fix is just two lines in that commit).

--
Chuck Lever




             reply	other threads:[~2016-09-07 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 19:28 Chuck Lever [this message]
2016-09-08  6:49 ` [stable 4.7] xprtrdma: Create common scatterlist fields in rpcrdma_mw Greg KH
2016-09-08 13:49   ` Chuck Lever
  -- strict thread matches above, loose matches on Subject: below --
2016-08-31 14:51 Chuck Lever

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=EC53244E-DABF-48B9-BD5E-73D04E64C14C@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.