All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: " J.A. Magallón " <jamagallon-sh/6fXdz2Rs@public.gmane.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: Problems with default ACLs over NFS
Date: Thu, 26 Mar 2009 17:05:13 -0700	[thread overview]
Message-ID: <20090326170513.4e7d377a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090323222427.00bb24e7-BIo4oXGMtDgJmsy6czSMtA@public.gmane.org>

(cc linux-nfs)

On Mon, 23 Mar 2009 22:24:27 +0100 "J.A. Magall__n" <jamagallon-sh/6fXdz2Rs@public.gmane.org> wrote:

> Hi all...
> 
> I have a strange problem with 2.6.29-rc8-git3.
> It looks like a kernel bug... ?
> 
> I have a box with NFS autofs-mounted home directories. Server is a
> Solaris 10 system. This worked in previous kernel versions, so I
> don't blame Solaris, at this moment.
> 
> With this acls set in my home:
> 
> 
> prometeo:~> getfacl .  
> 
> # file: .
> # owner: magallon
> # group: giga
> user::rwx
> user:webservd:r-x       #effective:r-x
> group::--x      #effective:--x
> mask:r-x
> other:--x
> default:user::rwx
> default:group::--x
> default:other:--x
> 
> I get this strange message in the linux client:
> 
> cicely:~> mkdir kk  
> mkdir: cannot create directory `kk': Invalid argument
> 
> But the directory is created, and its ACLs are correct:
> 
> prometeo:~> getfacl kk  
> 
> # file: kk
> # owner: magallon
> # group: giga
> user::rwx
> group::--x      #effective:--x
> other:--x
> default:user::rwx
> default:group::--x
> default:other:--x
> 
> If I remove the 'default' entries, the error message goes away.
> 
> With strace, I get this:
> 
> mkdir("kk", 0777)                       = -1 EINVAL (Invalid argument)
> 
> Mount info from /proc/mounts:
> 
> ldap:danae-nfs:automountMapName=auto_home,o=diis /home autofs rw,fd=7,pgrp=3165,timeout=600,minproto=5,maxproto=5,indirect 0 0
> 
> danae-nfs:/export/home/usuarios/giga/magallon /home/magallon nfs rw,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=155.210.152.202,mountvers=3,mountproto=tcp,addr=155.210.152.202 0 0
> 
> It happens the same If I try to create a file with "> kk", or try to cp -r one
> other dir, but "touch kk" works.
> 
> Any idea ?
> 


WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: " J.A. Magallón " <jamagallon@ono.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: Problems with default ACLs over NFS
Date: Thu, 26 Mar 2009 17:05:13 -0700	[thread overview]
Message-ID: <20090326170513.4e7d377a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090323222427.00bb24e7@werewolf.home>

(cc linux-nfs)

On Mon, 23 Mar 2009 22:24:27 +0100 "J.A. Magall__n" <jamagallon@ono.com> wrote:

> Hi all...
> 
> I have a strange problem with 2.6.29-rc8-git3.
> It looks like a kernel bug... ?
> 
> I have a box with NFS autofs-mounted home directories. Server is a
> Solaris 10 system. This worked in previous kernel versions, so I
> don't blame Solaris, at this moment.
> 
> With this acls set in my home:
> 
> 
> prometeo:~> getfacl .  
> 
> # file: .
> # owner: magallon
> # group: giga
> user::rwx
> user:webservd:r-x       #effective:r-x
> group::--x      #effective:--x
> mask:r-x
> other:--x
> default:user::rwx
> default:group::--x
> default:other:--x
> 
> I get this strange message in the linux client:
> 
> cicely:~> mkdir kk  
> mkdir: cannot create directory `kk': Invalid argument
> 
> But the directory is created, and its ACLs are correct:
> 
> prometeo:~> getfacl kk  
> 
> # file: kk
> # owner: magallon
> # group: giga
> user::rwx
> group::--x      #effective:--x
> other:--x
> default:user::rwx
> default:group::--x
> default:other:--x
> 
> If I remove the 'default' entries, the error message goes away.
> 
> With strace, I get this:
> 
> mkdir("kk", 0777)                       = -1 EINVAL (Invalid argument)
> 
> Mount info from /proc/mounts:
> 
> ldap:danae-nfs:automountMapName=auto_home,o=diis /home autofs rw,fd=7,pgrp=3165,timeout=600,minproto=5,maxproto=5,indirect 0 0
> 
> danae-nfs:/export/home/usuarios/giga/magallon /home/magallon nfs rw,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=155.210.152.202,mountvers=3,mountproto=tcp,addr=155.210.152.202 0 0
> 
> It happens the same If I try to create a file with "> kk", or try to cp -r one
> other dir, but "touch kk" works.
> 
> Any idea ?
> 


  parent reply	other threads:[~2009-03-27  0:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 21:24 Problems with default ACLs over NFS J.A. Magallón
     [not found] ` <20090323222427.00bb24e7-BIo4oXGMtDgJmsy6czSMtA@public.gmane.org>
2009-03-27  0:05   ` Andrew Morton [this message]
2009-03-27  0:05     ` Andrew Morton
2009-03-27 22:50     ` hooanon05
2009-04-20  4:42       ` Suresh Jayaraman
2009-04-20  4:42         ` Suresh Jayaraman
2009-04-20  5:17         ` hooanon05
2009-04-20  5:35           ` Suresh Jayaraman
2009-04-20  5:35             ` Suresh Jayaraman
2009-04-20 14:18             ` Sven Geggus
2009-04-21  5:00               ` Suresh Jayaraman
  -- strict thread matches above, loose matches on Subject: below --
2009-04-19 15:03 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=20090326170513.4e7d377a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jamagallon-sh/6fXdz2Rs@public.gmane.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.