Searched refs:sillyrename (Results 1 – 11 of 11) sorted by relevance
/dports/misc/rump/buildrump.sh-b914579/src/sys/fs/nfs/client/ |
H A D | nfsnode.h | 46 struct sillyrename { struct 119 struct sillyrename *nf_silly; /* Ptr to silly rename struct */ 183 int ncl_removeit(struct sillyrename *, struct vnode *);
|
H A D | nfs_clnode.c | 196 struct sillyrename *sp; in nfs_freesillyrename() 207 struct sillyrename *sp; in ncl_inactive()
|
H A D | nfs_clvnops.c | 217 struct componentname *scnp, struct sillyrename *sp); 1728 ncl_removeit(struct sillyrename *sp, struct vnode *vp) in ncl_removeit() 1918 struct sillyrename *sp) in nfs_renameit() 2406 struct sillyrename *sp; in nfs_sillyrename() 2415 MALLOC(sp, struct sillyrename *, sizeof (struct sillyrename), in nfs_sillyrename()
|
/dports/misc/rump/buildrump.sh-b914579/src/sys/nfs/ |
H A D | nfs_node.c | 187 struct sillyrename *sp; in nfs_inactive() 193 np->n_sillyrename = (struct sillyrename *)0; in nfs_inactive() 297 struct sillyrename *sp; in nfs_sillyworker() 300 sp = (struct sillyrename *)work; in nfs_sillyworker()
|
H A D | nfsnode.h | 148 struct sillyrename *nf_silly; /* !VDIR: silly rename struct */ 210 struct sillyrename { struct
|
H A D | nfs_var.h | 58 struct sillyrename; 98 int nfs_removeit(struct sillyrename *); 101 int nfs_renameit(struct vnode *, struct componentname *, struct sillyrename *);
|
H A D | nfs_vnops.c | 1801 nfs_removeit(struct sillyrename *sp) in nfs_removeit() 1931 nfs_renameit(struct vnode *sdvp, struct componentname *scnp, struct sillyrename *sp) in nfs_renameit() 2867 struct sillyrename *sp; in nfs_sillyrename()
|
/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/filesystems/nfs/ |
H A D | exporting.rst | 209 the NFS client will do a "sillyrename" to ensure that the file 211 file is held by nfsd so we usually end up doing a sillyrename, and
|
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/filesystems/nfs/ |
H A D | exporting.rst | 209 the NFS client will do a "sillyrename" to ensure that the file 211 file is held by nfsd so we usually end up doing a sillyrename, and
|
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/filesystems/nfs/ |
H A D | exporting.rst | 209 the NFS client will do a "sillyrename" to ensure that the file 211 file is held by nfsd so we usually end up doing a sillyrename, and
|
/dports/misc/rump/buildrump.sh-b914579/src/sys/fs/nfs/common/ |
H A D | nfs_var.h | 57 struct sillyrename;
|