All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@primarydata.com>
To: "rkudyba@fordham.edu" <rkudyba@fordham.edu>,
	"greg@kroah.com" <greg@kroah.com>
Cc: "kinglongmee@gmail.com" <kinglongmee@gmail.com>,
	"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Stable request to fix a reference leak and list corruption
Date: Wed, 5 Jul 2017 20:59:25 +0000	[thread overview]
Message-ID: <1499288361.63624.2.camel@primarydata.com> (raw)
In-Reply-To: <CAFHi+KQShB-m6GT87uKO=KN0AF-1t0+uXbW7UE2NFyi_wOSLDg@mail.gmail.com>

On Wed, 2017-07-05 at 16:29 -0400, Robert Kudyba wrote:
> > > Could we please queue up the following patch as a stable fix for
> > > commit a974deee47? It needs to be applied to v4.10 and older.
> > 
> > Now applied, thanks.
> 
> Until kernel 4.11.9 is into Fedora's updates, I downgraded our server
> acting as the NIS master to 4.10.16-200. But all NIS users time out
> with "ypserv: #011-> Error #-3. Could this be a different issue with
> rpcbind or nfs-utils? Here are some debug enabled logs for RPC with a
> different error "xs_error_report client ffff8d8223caa000, error=113"
> 

Error 113 is EHOSTUNREACH. It means that either your server is down, or
there is some other networking issue that is preventing the client from
connecting to it (e.g. a firewall setting, route configuration, arp
cache pollution?). Either way, it is unrelated to this particular
patch.

-- 
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com

WARNING: multiple messages have this Message-ID (diff)
From: Trond Myklebust <trondmy@primarydata.com>
To: "rkudyba@fordham.edu" <rkudyba@fordham.edu>,
	"greg@kroah.com" <greg@kroah.com>
Cc: "kinglongmee@gmail.com" <kinglongmee@gmail.com>,
	"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Stable request to fix a reference leak and list corruption
Date: Wed, 5 Jul 2017 20:59:25 +0000	[thread overview]
Message-ID: <1499288361.63624.2.camel@primarydata.com> (raw)
In-Reply-To: <CAFHi+KQShB-m6GT87uKO=KN0AF-1t0+uXbW7UE2NFyi_wOSLDg@mail.gmail.com>

T24gV2VkLCAyMDE3LTA3LTA1IGF0IDE2OjI5IC0wNDAwLCBSb2JlcnQgS3VkeWJhIHdyb3RlOg0K
PiA+ID4gQ291bGQgd2UgcGxlYXNlIHF1ZXVlIHVwIHRoZSBmb2xsb3dpbmcgcGF0Y2ggYXMgYSBz
dGFibGUgZml4IGZvcg0KPiA+ID4gY29tbWl0IGE5NzRkZWVlNDc/IEl0IG5lZWRzIHRvIGJlIGFw
cGxpZWQgdG8gdjQuMTAgYW5kIG9sZGVyLg0KPiA+IA0KPiA+IE5vdyBhcHBsaWVkLCB0aGFua3Mu
DQo+IA0KPiBVbnRpbCBrZXJuZWwgNC4xMS45IGlzIGludG8gRmVkb3JhJ3MgdXBkYXRlcywgSSBk
b3duZ3JhZGVkIG91ciBzZXJ2ZXINCj4gYWN0aW5nIGFzIHRoZSBOSVMgbWFzdGVyIHRvIDQuMTAu
MTYtMjAwLiBCdXQgYWxsIE5JUyB1c2VycyB0aW1lIG91dA0KPiB3aXRoICJ5cHNlcnY6ICMwMTEt
PiBFcnJvciAjLTMuIENvdWxkIHRoaXMgYmUgYSBkaWZmZXJlbnQgaXNzdWUgd2l0aA0KPiBycGNi
aW5kIG9yIG5mcy11dGlscz8gSGVyZSBhcmUgc29tZSBkZWJ1ZyBlbmFibGVkIGxvZ3MgZm9yIFJQ
QyB3aXRoIGENCj4gZGlmZmVyZW50IGVycm9yICJ4c19lcnJvcl9yZXBvcnQgY2xpZW50IGZmZmY4
ZDgyMjNjYWEwMDAsIGVycm9yPTExMyINCj4gDQoNCkVycm9yIDExMyBpcyBFSE9TVFVOUkVBQ0gu
IEl0IG1lYW5zIHRoYXQgZWl0aGVyIHlvdXIgc2VydmVyIGlzIGRvd24sIG9yDQp0aGVyZSBpcyBz
b21lIG90aGVyIG5ldHdvcmtpbmcgaXNzdWUgdGhhdCBpcyBwcmV2ZW50aW5nIHRoZSBjbGllbnQg
ZnJvbQ0KY29ubmVjdGluZyB0byBpdCAoZS5nLiBhIGZpcmV3YWxsIHNldHRpbmcsIHJvdXRlIGNv
bmZpZ3VyYXRpb24sIGFycA0KY2FjaGUgcG9sbHV0aW9uPykuIEVpdGhlciB3YXksIGl0IGlzIHVu
cmVsYXRlZCB0byB0aGlzIHBhcnRpY3VsYXINCnBhdGNoLg0KDQotLSANClRyb25kIE15a2xlYnVz
dA0KTGludXggTkZTIGNsaWVudCBtYWludGFpbmVyLCBQcmltYXJ5RGF0YQ0KdHJvbmQubXlrbGVi
dXN0QHByaW1hcnlkYXRhLmNvbQ0K


  reply	other threads:[~2017-07-05 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 14:47 [PATCH] Stable request to fix a reference leak and list corruption Trond Myklebust
2017-06-28 14:47 ` [PATCH] NFSv4: fix a reference leak caused WARNING messages Trond Myklebust
2017-07-02  8:53 ` [PATCH] Stable request to fix a reference leak and list corruption Greg KH
2017-07-05 20:29   ` Robert Kudyba
2017-07-05 20:59     ` Trond Myklebust [this message]
2017-07-05 20:59       ` Trond Myklebust
2017-07-06 14:24       ` Robert Kudyba

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=1499288361.63624.2.camel@primarydata.com \
    --to=trondmy@primarydata.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=greg@kroah.com \
    --cc=kinglongmee@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rkudyba@fordham.edu \
    --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.