Home
last modified time | relevance | path

Searched refs:nameidata (Results 1 – 4 of 4) sorted by relevance

/Linux-v5.4/fs/
Dnamei.c488 struct nameidata { struct
505 struct nameidata *saved; argument
511 static void set_nameidata(struct nameidata *p, int dfd, struct filename *name) in set_nameidata() argument
513 struct nameidata *old = current->nameidata; in set_nameidata()
519 current->nameidata = p; in set_nameidata()
524 struct nameidata *now = current->nameidata, *old = now->saved; in restore_nameidata()
526 current->nameidata = old; in restore_nameidata()
533 static int __nd_alloc_stack(struct nameidata *nd) in __nd_alloc_stack()
572 static inline int nd_alloc_stack(struct nameidata *nd) in nd_alloc_stack()
581 static void drop_links(struct nameidata *nd) in drop_links()
[all …]
/Linux-v5.4/Documentation/filesystems/
Dpath-lookup.rst361 Bringing it together with ``struct nameidata``
367 in a ``struct nameidata``, "namei" being the traditional name - dating
369 converts a "name" to an "inode". ``struct nameidata`` contains (among
404 is requested. Keeping a reference in the ``nameidata`` ensures that
422 Given a path (``name``) and a nameidata structure (``nd``), check that the
443 ``struct nameidata`` and drop the unneeded references.
725 ``struct nameidata`` in the ``m_seq`` field. This one lock and one
749 ``seq`` field of the nameidata structure, so ``nd->seq`` should always be
773 access and it is stored in the ``inode`` field of ``nameidata`` from where
888 ``seq`` number from the ``nameidata``, so it needs to be extra careful
[all …]
Dporting.rst506 ->lookup() do *not* take struct nameidata anymore; just the flags.
512 ->create() doesn't take ``struct nameidata *``; unlike the previous
601 nameidata isn't passed at all - nd_jump_link() doesn't need it and
609 dentry, it does not get nameidata at all and it gets called only when cookie
/Linux-v5.4/include/linux/
Dsched.h46 struct nameidata;
894 struct nameidata *nameidata; member