public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: linux-kernel@vger.kernel.org
Subject: NFS ENOLCK problem with CONFIG_SECURITY=n
Date: 31 Mar 2004 08:01:29 -0800	[thread overview]
Message-ID: <527jx1atuu.fsf@topspin.com> (raw)

I'm having problems with lockf returning ENOLCK on an NFS directory.
I also see messages like

    nsm_mon_unmon: rpc failed, status=-13
    lockd: cannot monitor 10.0.0.5
    lockd: failed to monitor 10.0.0.5

The system is an IA64 system running Debian testing with kernel 2.6.4.
I found previous reports of a similar problem, but the solution was to
set CONFIG_SECURITY to n (or add CONFIG_SECURITY_CAPABILITIES).
However, I already have CONFIG_SECURITY off:

    $ zgrep CONFIG_SECURITY /proc/config.gz
    # CONFIG_SECURITY is not set

Am I missing something?

Thanks,
  Roland

             reply	other threads:[~2004-03-31 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31 16:01 Roland Dreier [this message]
2004-03-31 16:38 ` NFS ENOLCK problem with CONFIG_SECURITY=n Trond Myklebust
2004-03-31 17:11   ` Roland Dreier

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=527jx1atuu.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=linux-kernel@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