[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1N6Mhx-0004s8-UU@pomaz-ex.szeredi.hu>
Date: Fri, 06 Nov 2009 12:10:21 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: miklos@...redi.hu, miklos@...redi.hu, akpm@...ux-foundation.org,
viro@...IV.linux.org.uk, dhowells@...hat.com, hch@...radead.org,
adilger@....com, mtk.manpages@...il.com,
torvalds@...ux-foundation.org, drepper@...il.com,
jamie@...reable.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 resend] vfs: new O_NODE open flag
On Thu, 5 Nov 2009, Alan Cox wrote:
> > open O_RDONLY
> > remote file moves
> > new one appears
> > fstat
> >
> > What's the difference?
>
> CIFS in the second case gets a handle to the remote object I believe. NFS
> certainly gets it right.
There's no f_op->fgetattr(), just i_op->getattr().
NFS gets it right, but NFSD is in the kernel and it can juggle with
looking up the inode by its number (for certain filesystems),
something CIFS is unlikely to be able to do.
Thanks,
Miklos
--
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