All of lore.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Olga Kornievskaia <aglo@umich.edu>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: SETCLIENTID acceptor
Date: Mon, 14 May 2018 17:07:40 -0400	[thread overview]
Message-ID: <20180514210740.GC29264@fieldses.org> (raw)
In-Reply-To: <D9D58278-855E-414E-A340-E47B5BEA7FD9@oracle.com>

On Mon, May 14, 2018 at 02:02:19PM -0400, Chuck Lever wrote:
> I erased the gssproxy cache, and that appears to have fixed
> the client misbehavior. I'm still using gssproxy, and I was
> able to use NFSv4.0 with Kerberos on my TCP-only i/f, then
> on my IB i/f, then on my RoCE i/f without notable problems.
> 
> Since gssproxy is the default configuration on RHEL 7-based
> systems, I think we want to make gssproxy work rather than
> disabling it -- unless there is some serious structural 
> problem that will prevent it from ever working right.

Yeah.  Maybe discuss it with Simo or someone if we've figured out what's
actually going on.

--g.

  reply	other threads:[~2018-05-14 21:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 21:19 SETCLIENTID acceptor Chuck Lever
2018-05-10 17:40 ` Olga Kornievskaia
2018-05-10 18:09   ` Chuck Lever
2018-05-10 19:07     ` Olga Kornievskaia
2018-05-10 19:23       ` Chuck Lever
2018-05-10 20:58         ` Olga Kornievskaia
2018-05-10 21:11           ` Chuck Lever
2018-05-10 21:34             ` Olga Kornievskaia
2018-05-11 14:34               ` Chuck Lever
2018-05-11 19:43                 ` Chuck Lever
2018-05-11 20:04                   ` Olga Kornievskaia
2018-05-11 20:57           ` Chuck Lever
2018-05-14 17:26             ` Olga Kornievskaia
2018-05-14 18:02               ` Chuck Lever
2018-05-14 21:07                 ` J. Bruce Fields [this message]
2018-05-14 21:00 ` J. Bruce Fields

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=20180514210740.GC29264@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=aglo@umich.edu \
    --cc=chuck.lever@oracle.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 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.