Lines Matching refs:nameidata

376 Bringing it together with ``struct nameidata``
382 in a ``struct nameidata``, "namei" being the traditional name - dating
384 converts a "name" to an "inode".  ``struct nameidata`` contains (among
416 is requested.  Keeping a reference in the ``nameidata`` ensures that
438    Given a path (``name``) and a nameidata structure (``nd``), check that the
460 otherwise it installs the new ``struct path`` in the ``struct nameidata``, and
492 path_lookupat() will unset LOOKUP_JUMPED in nameidata so that in the
740 ``struct nameidata`` in the ``m_seq`` field.  This one lock and one
764 ``seq`` field of the nameidata structure, so ``nd->seq`` should always be
788 access and it is stored in the ``inode`` field of ``nameidata`` from where
903 ``seq`` number from the ``nameidata``, so it needs to be extra careful
1000 The ``nameidata`` structure that we met in an earlier article contains a
1139 up in the ``nameidata``, and result in pick_link() returning ``NULL``.
1142 with "``/``" are detected in pick_link() which resets the ``nameidata``
1161 ``nameidata`` in place to point to that target.  ``->get_link()`` then
1170 component.  This is just returned in the ``last`` field of ``nameidata``.
1279 the various flags that can be stored in the ``nameidata`` to guide the
1300 ``ND_ROOT_PRESET`` indicates that the ``root`` field in the ``nameidata`` was