linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFSv4 and Kerberos problem in svcgssd
Date: Tue, 19 Jun 2012 11:04:13 +0200	[thread overview]
Message-ID: <20120619090413.GO30157@ics.muni.cz> (raw)
In-Reply-To: <20120618221437.GA13534@fieldses.org>

On Mon, Jun 18, 2012 at 06:14:37PM -0400, J. Bruce Fields wrote:
> > it seems that -n option for rpc.svcgssd produces file descriptor leaks. It
> > looks like this:
> > 
> > ls -l /proc/25920/fd/
> > total 0
> > lrwx------ 1 root root 64 Jun 16 00:13 29 -> /var/tmp/nfs_0
> > lr-x------ 1 root root 64 Jun 16 00:13 3 -> pipe:[24457591]
> > lrwx------ 1 root root 64 Jun 16 00:13 30 -> /var/tmp/nfs_0
> > l-wx------ 1 root root 64 Jun 16 00:13 4 -> pipe:[24457591]
> > lr-x------ 1 root root 64 Jun 16 00:13 5 -> pipe:[24457592]
> > l-wx------ 1 root root 64 Jun 16 00:13 6 -> pipe:[24457592]
> > lr-x------ 1 root root 64 Jun 16 00:13 7 -> /etc/gssapi_mech.conf
> > lr-x------ 1 root root 64 Jun 16 00:13 8 ->
> > /proc/25920/net/rpc/auth.rpcsec.init/channel
> > lrwx------ 1 root root 64 Jun 16 00:13 9 -> /var/tmp/nfs_0
> > 
> > Is there any known fix for this? It runs quickly from max open files..
> 
> It doesn't look familiar to me.--b.

seems to be KRB problem, however, I thought that it may be a problem in
svcgssd as well.

https://bugzilla.redhat.com/show_bug.cgi?id=761006

-- 
Lukáš Hejtmánek

      reply	other threads:[~2012-06-19  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 22:30 NFSv4 and Kerberos problem in svcgssd Lukas Hejtmanek
2012-06-18 22:14 ` J. Bruce Fields
2012-06-19  9:04   ` Lukas Hejtmanek [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=20120619090413.GO30157@ics.muni.cz \
    --to=xhejtman@ics.muni.cz \
    --cc=bfields@fieldses.org \
    --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).