mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Richard A Nelson <cowboy@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	openafs-devel@openafs.org
Subject: Re: NFS/AFS/Selinux issues with 2.26.29
Date: Wed, 25 Mar 2009 18:33:44 -0400	[thread overview]
Message-ID: <1238020424.26487.81.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <49CAAB9B.5070104@linux.vnet.ibm.com>

On Wed, 2009-03-25 at 15:09 -0700, Richard A Nelson wrote:
> 1) 2.6.29 NFS clients can no longer lock files:
>    #strace -f lockfile fubar
>    ...
>    uname({sys="Linux", node="gothic-ave", ...}) = 0
>    lstat64("_V0H.jaqyJB.gothic-ave", 0xbfdac9ec) = -1 ENOENT (No such file or directory)
>    open("_V0H.jaqyJB.gothic-ave", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0444) = -1 EINVAL (Invalid argument)
>    write(2, "lockfile: ", 10lockfile: )              = 10
>    write(2, "Try praying", 11Try praying)             = 11
>    write(2, ", giving up on \"", 16, giving up on ")       = 16
>    write(2, "fubar", 5fubar)                    = 5
>    write(2, "\"\n", 2"
> 
>    clients still on 2.6.28 and lower work fine ... the server *is* 2.26.29

lockfile works fine for me, both on NFSv3 and NFSv4 against my NetApp
filers, and as far as I can remember, there have been no changes to the
exclusive create code in the 2.6.29 client.

Given that you are claiming to be seeing selinux problems on
2.6.29-based servers, could you therefore please check again after
downgrading the server kernel?

Trond


  reply	other threads:[~2009-03-25 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 22:09 Richard A Nelson
2009-03-25 22:33 ` Trond Myklebust [this message]
2009-03-26  0:42   ` Richard A Nelson
2009-03-26 19:40     ` Trond Myklebust
2009-03-25 23:24 ` Marc Dionne
2009-03-26 20:55 ` David Howells

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=1238020424.26487.81.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=cowboy@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=openafs-devel@openafs.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

all inboxes | Powered by JetHome®