LKML Archive on
help / color / mirror / Atom feed
From: "J. Bruce Fields" <>
To: Lukas Hejtmanek <>
	Neil Brown <>
Subject: Re: Oops in NFSv4 server in
Date: Fri, 14 Mar 2008 14:14:13 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Mar 13, 2008 at 03:36:31PM +0100, Lukas Hejtmanek wrote:
> Hello,
> On Wed, Mar 12, 2008 at 12:00:07PM -0400, J. Bruce Fields wrote:
> > In this case it looks like something in the gss context cache is bad.
> > 
> > I'm not sure what's going on.
> I discovered what triggers this bug. If I have default export with secure
> option and I try to connect from insecure port, it produces the oops.
> If I add insecure option to the export, no oops at all and mount succeeds.
> Also, the bug is not triggered by the first attempt but by the second one.
> So I guess that from the first attempt there is something inserted into gss
> context cache - error occurs (insecure attempt with the secure option), gss
> context is removed from the cache as invalid but not completely. And the
> second attempt does oops. Sounds reasonable for me. 
> Hope this helps to find the bug.

That's an excellent clue, thanks.  I wonder it would be explainable by a
reference count imbalance of some kind in fh_verify?  I don't quite see
it yet, and unfortunately can't yet reproduce the bug here.


  reply	other threads:[~2008-03-14 18:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 12:25 Lukas Hejtmanek
2008-03-12 16:00 ` J. Bruce Fields
2008-03-13 14:36   ` Lukas Hejtmanek
2008-03-14 18:14     ` J. Bruce Fields [this message]
2008-03-14 19:33       ` J. Bruce Fields
2008-03-14 19:53         ` Lukas Hejtmanek
2008-03-14 20:05           ` J. Bruce Fields
2008-03-14 23:37             ` [PATCH] nfsd: fix oops on access from high-numbered ports J. Bruce Fields
2008-03-14 23:42             ` Oops in NFSv4 server in J. Bruce Fields
2008-03-16 23:19               ` Neil Brown
2008-03-19 22:32                 ` J. Bruce Fields
2008-03-20  2:31                   ` NeilBrown
2008-03-17  8:12             ` Lukas Hejtmanek
2008-03-17 13:15               ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: Oops in NFSv4 server in' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).