[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1157439691.4133.12.camel@raven.themaw.net>
Date: Tue, 05 Sep 2006 15:01:31 +0800
From: Ian Kent <raven@...maw.net>
To: Trond Myklebust <trond.myklebust@....uio.no>
Cc: David Howells <dhowells@...hat.com>, Andrew Morton <akpm@...l.org>,
torvalds@...l.org, steved@...hat.com,
linux-fsdevel@...r.kernel.org, linux-cachefs@...hat.com,
nfsv4@...ux-nfs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] Permit filesystem local caching and NFS superblock
sharing [try #13]
On Tue, 2006-09-05 at 14:06 +0800, Ian Kent wrote:
> On Tue, 2006-09-05 at 00:53 -0400, Trond Myklebust wrote:
> > On Tue, 2006-09-05 at 12:03 +0800, Ian Kent wrote:
> > > Sure but this is an old version of autofs which is in use so changing
> > > the expected behavior of a system call is not acceptable and I expect
> > > other applications may well have a problem with this also.
> >
> > Applications that rely on mkdir() to never return EACCES are broken.
> > Particularly so in an selinux system (as was the case here).
>
> That's not quite right.
>
> autofs v4 doesn't rely on mkdir never returning EACCESS just that it
> return EEXIST if the directory exists. Never the less if the behavior of
> stat will work in this case I'll change v4 to do it the way you suggest
> (as v5 does already).
Aaah. Wrong again!
Although v5 doesn't attempt to mount an NFS export if the directory
doesn't exist it does end up doing a mkdir later as the most common case
is mounting an NFS export within an autofs filesystem or other, usually
local filesystem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists