linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: WARN_ON added to rpc_create()
Date: Fri, 19 Aug 2016 10:51:43 -0400	[thread overview]
Message-ID: <20160819145143.GB2956@parsley.fieldses.org> (raw)
In-Reply-To: <E884FAC0-09C6-467D-8A90-AC1AEC72ED81@oracle.com>

On Thu, Aug 18, 2016 at 05:59:12PM -0400, Chuck Lever wrote:
> Thanks for checking.
> 
> I've tracked the misbehavior down to a DMA mapping mismatch. It's
> not related to the backchannel at all. I'm putting together a fix
> right now.
> 
> But I would like to use NFSv4.1/RDMA without that warning firing.
> Any reason to keep it (in either place) ?

I thought you said the BC_TCP->BC change fixed it?  If so, we should
just do that.

--b.

  reply	other threads:[~2016-08-19 14:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 15:27 WARN_ON added to rpc_create() Chuck Lever
2016-08-03 17:47 ` J. Bruce Fields
2016-08-03 19:40   ` Chuck Lever
2016-08-10 18:01     ` Chuck Lever
2016-08-18 21:56       ` J. Bruce Fields
2016-08-18 21:59         ` Chuck Lever
2016-08-19 14:51           ` J. Bruce Fields [this message]
2016-08-18 21:56     ` J. Bruce Fields
2016-08-18 22:11       ` Chuck Lever
2016-08-19 14:50         ` J. Bruce Fields
2016-08-19 15:06           ` Chuck Lever
2016-08-19 15:19             ` Chuck Lever
2016-08-19 15:47             ` J. Bruce Fields
2016-08-19 15:51               ` Chuck Lever
2016-08-19 15:55                 ` J. Bruce Fields

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=20160819145143.GB2956@parsley.fieldses.org \
    --to=bfields@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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 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).