From: "Steve Wise" <swise@opengridcomputing.com>
To: "'Anna Schumaker'" <Anna.Schumaker@netapp.com>,
"'Trond Myklebust'" <trond.myklebust@primarydata.com>
Cc: <linux-nfs@vger.kernel.org>, "'Chuck Lever'" <chuck.lever@oracle.com>
Subject: RE: [GIT PULL] Please pull an NFSoRDMA client bugfix
Date: Tue, 17 Nov 2015 14:14:43 -0600 [thread overview]
Message-ID: <004d01d12174$98e80340$cab809c0$@opengridcomputing.com> (raw)
In-Reply-To: <56439320.1040103@Netapp.com>
> -----Original Message-----
> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Anna Schumaker
> Sent: Wednesday, November 11, 2015 1:13 PM
> To: Steve Wise; 'Trond Myklebust'
> Cc: linux-nfs@vger.kernel.org; Chuck Lever
> Subject: Re: [GIT PULL] Please pull an NFSoRDMA client bugfix
>
> Hi Steve,
>
> On 11/05/2015 12:20 PM, Steve Wise wrote:
> > Anna and Trond,
> >
> > Does it make sense for this to be pushed into stable as well? It can cause a touch-after-free crash on iWARP transports.
>
> Do you know if any users are hitting this? I can push it to stable, but only if it's being hit in the wild.
>
Don't think it is being hit in the wild...
> Anna
>
> >
> > Steve.
> >
> >> -----Original Message-----
> >> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Anna Schumaker
> >> Sent: Tuesday, September 29, 2015 3:57 PM
> >> To: Trond Myklebust
> >> Cc: linux-nfs@vger.kernel.org; Steve Wise
> >> Subject: [GIT PULL] Please pull an NFSoRDMA client bugfix
> >>
> >> Hi Trond,
> >>
> >> The following changes since commit d0f36c46deea97bd16b9277be2f1acac74d76037:
> >>
> >> xprtrdma: take HCA driver refcount at client (2015-08-05 16:22:56 -0400)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.linux-nfs.org/projects/anna/nfs-rdma.git tags/nfs-rdma-for-4.3-2
> >>
> >> for you to fetch changes up to 72c021738252dde5849d575a650239d6404930ee:
> >>
> >> xprtrdma: disconnect and flush cqs before freeing buffers (2015-09-28 10:42:35 -0400)
> >>
> >> Thanks,
> >> Anna
> >>
> >> ----------------------------------------------------------------
> >> Steve Wise (1):
> >> xprtrdma: disconnect and flush cqs before freeing buffers
> >>
> >> net/sunrpc/xprtrdma/transport.c | 2 +-
> >> net/sunrpc/xprtrdma/verbs.c | 9 ++++++---
> >> 2 files changed, 7 insertions(+), 4 deletions(-)
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-11-17 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 20:57 [GIT PULL] Please pull an NFSoRDMA client bugfix Anna Schumaker
2015-11-05 17:20 ` Steve Wise
2015-11-11 19:12 ` Anna Schumaker
2015-11-17 20:14 ` Steve Wise [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-17 22:12 [GIT PULL] Please pull an NFSoRDMA Client Bugfix Anna Schumaker
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='004d01d12174$98e80340$cab809c0$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=Anna.Schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 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.