On Wed, 2018-03-14 at 07:02 -0400, Jeff Layton wrote:
> On Wed, 2018-03-14 at 16:42 +0800, Eddie Horng wrote:
> > Hi Amir,
> > Since the flock issue is clarified, I would like to start this new
> > thread to discuss if we can find the cause of d_type=DT_UNKNOWN.
> > First
>
> This sounds like NOTABUG to me. As readdir(3) states:
>
> Currently, only some filesystems (among them: Btrfs, ext2, ext3,
> and ext4) have full support for returning the file type in
> d_type. All applications must properly handle a return of
> DT_UNKNOWN.
>
> Applications that rely solely on d_type are effectively broken. You
> always need to be able to follow up with a stat or equivalent.
>
Yes, but one of the main such applications is the "find" utility, which
uses it to avoid calling stat() in order to discover the directories.
For that reason, NFS does try to set the d_type flag when it is using
readdirplus, and the server returns attributes for the entry in
question. Otherwise, it is forced to default to DT_UNKNOWN.
Note that in the cases where the readdir entry has a matching dentry,
we probably could try to do better by doing a d_lookup() and then
filling the d_type. Is that worth doing?
> > of all I tried rdirplus and nordirplus mount option but got no
> > difference. Then I roughly trace call flow of nfs3_decode_dirent( )
> > as
> > below:
> >
> > decode_fattr3()
> > fattr->mode = (be32_to_cpup(p++) & ~S_IFMT) | fmode;
> > fattr->valid |= NFS_ATTR_FATTR_V3;
> >
> > decode_post_op_attr()
> > p = xdr_inline_decode(xdr, 4);
> > if (*p != xdr_zero)
> > return decode_fattr3(xdr, fattr);
> >
> > nfs3_decode_dirent()
> > entry->d_type = DT_UNKNOWN;
> > if (entry->fattr->valid & NFS_ATTR_FATTR_V3)
> > entry->d_type = nfs_umode_to_dtype(entry->fattr->mode);
> >
> > In overlay exported case, decode_post_op_attr hits *p==xdr_zero, so
> > decode_fattr3 is not called, then d_type reamins DT_UNKNOWN in
> > nfs3_decode_dirent. It seems nfs4_decode_dirent has very different
> > way
> > to decode file attr and maybe the xdr layout is quite different as
> > well.I have not idea about how the xdr to be filled from overlay
> > and
> > nfsd's output. Could some of you master give a hint?
>
> Very different.
>
> The v3 client will sometimes issue a READDIR (just names and fileids
> of
> dirents) and sometimes a READDIRPLUS (same as READDIR + attributes)
> depending on the expected size of the result and what sort of access
> pattern the application has. If you get back DT_UNKNOWN, it's quite
> possible that it chose to use a READDIR and therefore doesn't have
> enough info to fill out the d_type.
>
> Cheers,
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@xxxxxxxxxxxxxxx
��.n��������+%������w��{.n�����{���w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
