Home
last modified time | relevance | path

Searched refs:atomic_open (Results 1 – 14 of 14) sorted by relevance

/Linux-v5.10/fs/
Dbad_inode.c175 .atomic_open = bad_inode_atomic_open,
Dnamei.c2957 static struct dentry *atomic_open(struct nameidata *nd, struct dentry *dentry, in atomic_open() function
2970 error = dir->i_op->atomic_open(dir, dentry, file, in atomic_open()
3075 if (dir_inode->i_op->atomic_open) { in lookup_open()
3076 dentry = atomic_open(nd, dentry, file, open_flag, mode); in lookup_open()
/Linux-v5.10/fs/9p/
Dvfs_inode.c1382 .atomic_open = v9fs_vfs_atomic_open,
1397 .atomic_open = v9fs_vfs_atomic_open,
Dvfs_inode_dotl.c953 .atomic_open = v9fs_vfs_atomic_open_dotl,
/Linux-v5.10/Documentation/filesystems/
Dporting.rst713 ->atomic_open() calls without O_CREAT may happen in parallel.
763 ->atomic_open() calling conventions have changed. Gone is ``int *opened``,
768 does not need any changes in ->atomic_open() instances.
859 failure exits in ->atomic_open() instances should *NOT* fput() the file,
Dlocking.rst79 int (*atomic_open)(struct inode *, struct dentry *,
108 atomic_open: shared (exclusive if O_CREAT is set in open flags)
Dvfs.rst437 int (*atomic_open)(struct inode *, struct dentry *, struct file *,
568 ``atomic_open``
Dpath-lookup.rst1224 this. If not, then ``lookup_open()`` will either call ``atomic_open()`` (if
1403 introduction of ``->atomic_open()`` they are less relevant there.
/Linux-v5.10/fs/cifs/
Dcifsfs.c1047 .atomic_open = cifs_atomic_open,
/Linux-v5.10/fs/ceph/
Ddir.c1958 .atomic_open = ceph_atomic_open,
/Linux-v5.10/fs/fuse/
Ddir.c1814 .atomic_open = fuse_atomic_open,
/Linux-v5.10/fs/gfs2/
Dinode.c2168 .atomic_open = gfs2_atomic_open,
/Linux-v5.10/include/linux/
Dfs.h1887 int (*atomic_open)(struct inode *, struct dentry *, member
/Linux-v5.10/fs/nfs/
Dnfs4proc.c10322 .atomic_open = nfs_atomic_open,