All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Kudyba <rkudyba@fordham.edu>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: "greg@kroah.com" <greg@kroah.com>,
	"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: Thu, 6 Jul 2017 10:24:54 -0400	[thread overview]
Message-ID: <CAFHi+KTpg8MKWH60-R9NqdjFhYyVeFKY5JrU1Ezw-kgDXNcEYg@mail.gmail.com> (raw)
In-Reply-To: <1499288361.63624.2.camel@primarydata.com>

>> > > 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.

Ahh indeed it was firewalld. Not sure why this just cropped up,
perhaps some update? Anyways once I ran:

firewall-cmd --permanent --add-service=nfs
firewall-cmd --permanent --add-service=mountd
firewall-cmd --permanent --add-service=rpc-bind
firewall-cmd --reload

We were back in business with NFS sharing. Thanks so much for the
reply & hint as I couldn't find what error 113 meant.

      reply	other threads:[~2017-07-06 14:25 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
2017-07-05 20:59       ` Trond Myklebust
2017-07-06 14:24       ` Robert Kudyba [this message]

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=CAFHi+KTpg8MKWH60-R9NqdjFhYyVeFKY5JrU1Ezw-kgDXNcEYg@mail.gmail.com \
    --to=rkudyba@fordham.edu \
    --cc=Anna.Schumaker@netapp.com \
    --cc=greg@kroah.com \
    --cc=kinglongmee@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trondmy@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.