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
459 ``struct nameidata`` and drop the unneeded references.
741 ``struct nameidata`` in the ``m_seq`` field.  This one lock and one
765 ``seq`` field of the nameidata structure, so ``nd->seq`` should always be
789 access and it is stored in the ``inode`` field of ``nameidata`` from where
904 ``seq`` number from the ``nameidata``, so it needs to be extra careful
1001 The ``nameidata`` structure that we met in an earlier article contains a
1158 up in the ``nameidata``, and result in ``get_link()`` returning ``NULL``.
1161 with "``/``" are detected in ``get_link()`` which resets the ``nameidata``
1180 ``nameidata`` in place to point to that target.  ``->follow_link()`` then
1182 reports this by leaving the ``last_type`` field of ``nameidata`` as
1190 component.  This is just returned in the ``last`` field of ``nameidata``.
1303 the various flags that can be stored in the ``nameidata`` to guide the
1324 ``LOOKUP_ROOT`` indicates that the ``root`` field in the ``nameidata`` was