From: Steven Rostedt <rostedt@goodmis.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Jeff Layton <jlayton@poochiereds.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Network Devel Mailing List <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Bruce James Fields <bfields@fieldses.org>
Subject: Re: [REGRESSION] NFS is creating a hidden port (left over from xs_bind() )
Date: Fri, 19 Jun 2015 20:50:24 -0400 [thread overview]
Message-ID: <20150619205024.0ad093f8@gandalf.local.home> (raw)
In-Reply-To: <20150619203745.16545a22@gandalf.local.home>
On Fri, 19 Jun 2015 20:37:45 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> > Is it causing any other damage than the rkhunter warning you reported?
>
> Well, not that I know of. Are you sure that this port will be
> reconnected, and is not just a leak. Not sure if you could waste more
> ports this way with connections to other machines. I only have my
> wife's box connect to this server. This server is actually a client to
> my other boxes.
>
> Although the rkhunter warning is the only thing that triggers, I still
> would think this is a stable fix, especially if the port is leaked and
> not taken again.
I did some experiments. If I unmount the directories from my wife's
machine and remount them, the port that was hidden is fully closed.
Maybe it's not that big of a deal after all.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Jeff Layton <jlayton@poochiereds.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Network Devel Mailing List <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Bruce James Fields <bfields@fieldses.org>
Subject: Re: [REGRESSION] NFS is creating a hidden port (left over from xs_bind() )
Date: Fri, 19 Jun 2015 20:50:24 -0400 [thread overview]
Message-ID: <20150619205024.0ad093f8@gandalf.local.home> (raw)
In-Reply-To: <20150619203745.16545a22@gandalf.local.home>
On Fri, 19 Jun 2015 20:37:45 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> > Is it causing any other damage than the rkhunter warning you reported?
>
> Well, not that I know of. Are you sure that this port will be
> reconnected, and is not just a leak. Not sure if you could waste more
> ports this way with connections to other machines. I only have my
> wife's box connect to this server. This server is actually a client to
> my other boxes.
>
> Although the rkhunter warning is the only thing that triggers, I still
> would think this is a stable fix, especially if the port is leaked and
> not taken again.
I did some experiments. If I unmount the directories from my wife's
machine and remount them, the port that was hidden is fully closed.
Maybe it's not that big of a deal after all.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Jeff Layton <jlayton@poochiereds.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Network Devel Mailing List <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Bruce James Fields <bfields@fieldses.org>
Subject: Re: [REGRESSION] NFS is creating a hidden port (left over from xs_bind() )
Date: Fri, 19 Jun 2015 20:50:24 -0400 [thread overview]
Message-ID: <20150619205024.0ad093f8@gandalf.local.home> (raw)
In-Reply-To: <20150619203745.16545a22@gandalf.local.home>
On Fri, 19 Jun 2015 20:37:45 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> > Is it causing any other damage than the rkhunter warning you reported?
>
> Well, not that I know of. Are you sure that this port will be
> reconnected, and is not just a leak. Not sure if you could waste more
> ports this way with connections to other machines. I only have my
> wife's box connect to this server. This server is actually a client to
> my other boxes.
>
> Although the rkhunter warning is the only thing that triggers, I still
> would think this is a stable fix, especially if the port is leaked and
> not taken again.
I did some experiments. If I unmount the directories from my wife's
machine and remount them, the port that was hidden is fully closed.
Maybe it's not that big of a deal after all.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
next prev parent reply other threads:[~2015-06-20 0:50 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 3:49 [REGRESSION] NFS is creating a hidden port (left over from xs_bind() ) Steven Rostedt
2015-06-12 14:10 ` Trond Myklebust
2015-06-12 14:40 ` Eric Dumazet
2015-06-12 14:40 ` Eric Dumazet
2015-06-12 14:57 ` Trond Myklebust
2015-06-12 15:43 ` Eric Dumazet
2015-06-12 15:43 ` Eric Dumazet
2015-06-12 15:34 ` Steven Rostedt
2015-06-12 15:34 ` Steven Rostedt
2015-06-12 15:50 ` Steven Rostedt
2015-06-12 15:50 ` Steven Rostedt
2015-06-12 15:53 ` Steven Rostedt
2015-06-18 3:08 ` Steven Rostedt
2015-06-18 3:08 ` Steven Rostedt
2015-06-18 19:24 ` Trond Myklebust
2015-06-18 19:24 ` Trond Myklebust
2015-06-18 19:49 ` Steven Rostedt
2015-06-18 19:49 ` Steven Rostedt
2015-06-18 22:50 ` Jeff Layton
2015-06-18 22:50 ` Jeff Layton
2015-06-19 1:08 ` Steven Rostedt
2015-06-19 1:08 ` Steven Rostedt
2015-06-19 1:37 ` Jeff Layton
2015-06-19 3:21 ` Steven Rostedt
2015-06-19 3:21 ` Steven Rostedt
2015-06-19 16:25 ` Steven Rostedt
2015-06-19 17:17 ` Steven Rostedt
2015-06-19 17:17 ` Steven Rostedt
2015-06-19 17:17 ` Steven Rostedt
2015-06-19 17:39 ` Trond Myklebust
2015-06-19 17:39 ` Trond Myklebust
2015-06-19 17:39 ` Trond Myklebust
2015-06-19 19:52 ` Jeff Layton
2015-06-19 19:52 ` Jeff Layton
2015-06-19 19:52 ` Jeff Layton
2015-06-19 20:30 ` Trond Myklebust
2015-06-19 20:30 ` Trond Myklebust
2015-06-19 20:30 ` Trond Myklebust
2015-06-19 21:56 ` Steven Rostedt
2015-06-19 21:56 ` Steven Rostedt
2015-06-19 21:56 ` Steven Rostedt
2015-06-19 22:14 ` Steven Rostedt
2015-06-19 22:14 ` Steven Rostedt
2015-06-19 22:14 ` Steven Rostedt
2015-06-19 23:25 ` Trond Myklebust
2015-06-19 23:25 ` Trond Myklebust
2015-06-19 23:25 ` Trond Myklebust
2015-06-20 0:37 ` Steven Rostedt
2015-06-20 0:37 ` Steven Rostedt
2015-06-20 0:37 ` Steven Rostedt
2015-06-20 0:50 ` Steven Rostedt [this message]
2015-06-20 0:50 ` Steven Rostedt
2015-06-20 0:50 ` Steven Rostedt
2015-06-20 1:27 ` Steven Rostedt
2015-06-20 1:27 ` Steven Rostedt
2015-06-20 1:27 ` Steven Rostedt
2015-06-20 2:44 ` Trond Myklebust
2015-06-20 2:44 ` Trond Myklebust
2015-06-20 2:44 ` Trond Myklebust
2016-06-22 16:41 ` It's back! (Re: [REGRESSION] NFS is creating a hidden port (left over from xs_bind() )) Steven Rostedt
2015-06-19 21:50 ` [REGRESSION] NFS is creating a hidden port (left over from xs_bind() ) Steven Rostedt
2015-06-19 21:50 ` Steven Rostedt
2015-06-19 21:50 ` Steven Rostedt
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=20150619205024.0ad093f8@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=eric.dumazet@gmail.com \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@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.