All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weston Andros Adamson <dros@primarydata.com>
To: Chris Perl <chris.perl@gmail.com>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Jeffrey Layton <jeff.layton@primarydata.com>,
	linux-nfs list <linux-nfs@vger.kernel.org>
Subject: Re: nfs-utils - TCP ephemeral port exhaustion results in mount failures
Date: Fri, 5 Sep 2014 17:23:49 -0400	[thread overview]
Message-ID: <44C76FD6-5333-402B-9DA4-D38065AAA15F@primarydata.com> (raw)
In-Reply-To: <CA+Tkd6UjfJmjG0WE1F2bsB068rXkEUHhOq6S+F5e=OVA_wxeMw@mail.gmail.com>

Do these patches require one another?

What happens if I have a patched nfs-utils, but not a patched kernel or the other way around?

-dros


On Sep 5, 2014, at 4:20 PM, Chris Perl <chris.perl@gmail.com> wrote:

> It looks like they may have come through after all, unfortunately I
> already sent them again.  Apologies for the spam.
> 
> On Fri, Sep 5, 2014 at 4:04 PM, Chris Perl <chris.perl@gmail.com> wrote:
>> I tried to send them to the list, but I guess they didn't come through
>> because my sender was set to chris.perl@gmail.com, but I ran `git
>> send-email' from work, so the smtp sender ip wouldn't authorized.
>> 
>> I'll figure out a way to send them now.
>> 
>> On Fri, Sep 5, 2014 at 4:03 PM, Trond Myklebust
>> <trond.myklebust@primarydata.com> wrote:
>>> 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
> --
> 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


  reply	other threads:[~2014-09-05 21:23 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
2014-09-05 20:04           ` Chris Perl
2014-09-05 20:20             ` Chris Perl
2014-09-05 21:23               ` Weston Andros Adamson [this message]
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=44C76FD6-5333-402B-9DA4-D38065AAA15F@primarydata.com \
    --to=dros@primarydata.com \
    --cc=chris.perl@gmail.com \
    --cc=chuck.lever@oracle.com \
    --cc=jeff.layton@primarydata.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.