linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Sven Geggus <lists@fuchsschwanzdomain.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Kerberized NFS-Server Problem still present in 3.10.0-rc2
Date: Wed, 19 Jun 2013 17:34:12 -0400	[thread overview]
Message-ID: <20130619213412.GA2547@fieldses.org> (raw)
In-Reply-To: <kpscp8$fo3$1@ultimate100.geggus.net>

On Wed, Jun 19, 2013 at 01:47:20PM +0000, Sven Geggus wrote:
> Hello,
> 
> I just tried using Kernel 3.10.0-rc2 an my NFS-server test VM and I'm still
> unable to run a working kerberized NFS-Server with this kernel.
> 
> To make it work I would have to go back to Kernel 3.8.x (which i can't
> because I want to use drbd 8.4).
> 
> Any hints on how to furter debug this?
> 
> As I already said, I failed in "git bisecting" the Problem because the
> behaviour changed from broken behaviour (infinite hang) to another broken
> behaviour (permission denied) while doing so.

Apologies, I don't remember the previous discussion, so, could you
summarize for me?:

	- you're able to reproduce/not reproduce the problem by changing
	  *only* the kernel on the nfs server between 3.8.x and
	  3.10.0-rc2 ?
	- have you figured out exactly where the failure happens?:
	- which version of NFS are you using?

Also if you haven't already it would be useful to know at exactly which
step of the process it's failing.  As a first step running wireshark on
the traffic between client and server and looking for a NULL
init_sec_context rpc call and seeing whether it succeeds or not, would
be useful.

--b.

  reply	other threads:[~2013-06-19 21:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 13:47 Kerberized NFS-Server Problem still present in 3.10.0-rc2 Sven Geggus
2013-06-19 21:34 ` J. Bruce Fields [this message]
2013-06-20  8:03   ` Sven Geggus
2013-06-20 12:09     ` Sven Geggus
2013-06-20 14:49     ` J. Bruce Fields
2013-06-20 14:52       ` J. Bruce Fields
2013-06-21  8:32         ` Sven Geggus
2013-06-24 21:54           ` J. Bruce Fields
2013-06-25  9:46             ` Sven Geggus
2013-07-01 12:09               ` Sven Geggus
     [not found]               ` <20130701205234.GF19945@fieldses.org>
2013-07-02  8:05                 ` Sven Geggus
     [not found]                   ` <20130705181859.GA8288@fieldses.org>
     [not found]                     ` <20130705203435.GE8288@fieldses.org>
2013-07-08  8:08                       ` Sven Geggus
2013-07-08 13:35                         ` J. Bruce Fields
2013-07-08 15:54                           ` Sven Geggus
2013-07-08 19:41                             ` J. Bruce Fields
2013-07-09 16:03                               ` Sven Geggus
2013-07-09 16:57                         ` J. Bruce Fields
2013-07-09 17:23                           ` Chuck Lever
2013-07-10  7:55                           ` Sven Geggus

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=20130619213412.GA2547@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lists@fuchsschwanzdomain.de \
    /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).