linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Chris Perl <chris.perl@gmail.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Jeff Layton <jeff.layton@primarydata.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfs-utils - TCP ephemeral port exhaustion results in mount failures
Date: Fri, 5 Sep 2014 16:03:11 -0400	[thread overview]
Message-ID: <CAHQdGtRpD03KHJyu1MtxA=21pu4z_YAG4XA-8Bu+t4xeUefaNQ@mail.gmail.com> (raw)
In-Reply-To: <CA+Tkd6WYkkVbY2YsmRNHB4+9AFg5UjC1xoycLTZQOYrtFCT_2w@mail.gmail.com>

On Fri, Sep 5, 2014 at 3:40 PM, Chris Perl <chris.perl@gmail.com> wrote:
> I just submitted two patches, one for nfs-utils and one for linux-nfs.
>
> As I said in my previous email, the patch to nfs-utils was enough to
> get us farther along, but we failed inside mount(2) with EIO (with a
> decidedly more confusing error message).
>
> So, I've also submitted a patch for the rpc code in the kernel that
> also avoids bind when asking for a random ephemeral port.  I've tested
> the combination of these two patches with my system while in the
> situation I originally outlined.  I can continue to successfully mount
> NFS filesystems using both of these patches.
>
> I don't particularly love the kernel patch, as it makes `xs_bind' not
> actually bind in all circumstances, which seems confusing.  However, I
> thought trying to rework things in a larger way would cause more
> issues given that I'm not very familiar with this code.  If everyone
> hates it, I can try something else.

To whom did you submit these patches? I don't see anything in the
linux-nfs mailing list.

-- 
Trond Myklebust

Linux NFS client maintainer, PrimaryData

trond.myklebust@primarydata.com

  reply	other threads:[~2014-09-05 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 16:51 nfs-utils - TCP ephemeral port exhaustion results in mount failures Chris Perl
2014-09-03 11:00 ` Jeff Layton
2014-09-03 13:55   ` Chuck Lever
2014-09-03 20:01     ` Chris Perl
2014-09-05 19:40       ` Chris Perl
2014-09-05 20:03         ` Trond Myklebust [this message]
2014-09-05 20:04           ` Chris Perl
2014-09-05 20:20             ` Chris Perl
2014-09-05 21:23               ` Weston Andros Adamson
2014-09-05 22:34                 ` Chris Perl
2014-09-09 18:18               ` Steve Dickson
2014-09-09 21:01                 ` Chris Perl

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='CAHQdGtRpD03KHJyu1MtxA=21pu4z_YAG4XA-8Bu+t4xeUefaNQ@mail.gmail.com' \
    --to=trond.myklebust@primarydata.com \
    --cc=chris.perl@gmail.com \
    --cc=chuck.lever@oracle.com \
    --cc=jeff.layton@primarydata.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).