Lines Matching refs:called

24 on are called from a process context. Filesystem locking is described
75 called so the specific filesystem implementation can do its work. You
235 All methods are called without any locks being held, unless otherwise
237 only called from a process context (i.e. not from an interrupt handler
240 alloc_inode: this method is called by alloc_inode() to allocate memory
246 destroy_inode: this method is called by destroy_inode() to release
251 dirty_inode: this method is called by the VFS to mark an inode dirty.
253 write_inode: this method is called when the VFS needs to write an
257 drop_inode: called when the last access to the inode is dropped,
263 called regardless of the value of i_nlink)
270 delete_inode: called when the VFS wants to delete an inode
272 put_super: called when the VFS wishes to free the superblock
273 (i.e. unmount). This is called with the superblock lock held
275 sync_fs: called when VFS is writing out all dirty data associated with
279 freeze_fs: called when VFS is locking a filesystem and
283 unfreeze_fs: called when VFS is unlocking a filesystem and making it writable
286 statfs: called when the VFS needs to get filesystem statistics.
288 remount_fs: called when the filesystem is remounted. This is called
291 clear_inode: called then the VFS clears the inode. Optional
293 umount_begin: called when the VFS is unmounting a filesystem.
295 show_options: called by the VFS to show mount options for
298 quota_read: called by the VFS to read from filesystem quota file.
300 quota_write: called by the VFS to write to filesystem quota file.
302 nr_cached_objects: called by the sb cache shrinking function for the
306 free_cache_objects: called by the sb cache shrinking function for the
309 implement ->nr_cached_objects for it to be called correctly.
312 encountered, hence the void return type. This will never be called if
370 Again, all methods are called without any locks being held, unless
373 create: called by the open(2) and creat(2) system calls. Only
379 lookup: called when the VFS needs to look up an inode in a parent
384 should be inserted into the dentry (this is called a negative
391 This method is called with the directory inode semaphore held
393 link: called by the link(2) system call. Only required if you want
397 unlink: called by the unlink(2) system call. Only required if you
400 symlink: called by the symlink(2) system call. Only required if you
404 mkdir: called by the mkdir(2) system call. Only required if you want
408 rmdir: called by the rmdir(2) system call. Only required if you want
411 mknod: called by the mknod(2) system call to create a device (char,
417 rename: called by the rename(2) system call to rename the object to
434 readlink: called by the readlink(2) system call. Only required if
437 follow_link: called by the VFS to follow a symbolic link to the
447 put_link: called by the VFS to release resources allocated by
449 to this method as the last parameter; only called when
452 permission: called by the VFS to check for access rights on a POSIX-like
455 May be called in rcu-walk mode (mask & MAY_NOT_BLOCK). If in rcu-walk
460 -ECHILD and it will be called again in ref-walk mode.
462 setattr: called by the VFS to set attributes for a file. This method
463 is called by chmod(2) and related system calls.
465 getattr: called by the VFS to get attributes of a file. This method
466 is called by stat(2) and related system calls.
468 setxattr: called by the VFS to set an extended attribute for a file.
470 inode. This method is called by setxattr(2) system call.
472 getxattr: called by the VFS to retrieve the value of an extended
473 attribute name. This method is called by getxattr(2) function
476 listxattr: called by the VFS to list all extended attributes for a
477 given file. This method is called by listxattr(2) system call.
479 removexattr: called by the VFS to remove an extended attribute from
480 a file. This method is called by removexattr(2) system call.
482 update_time: called by the VFS to update a specific time or the i_version of
486 atomic_open: called on the last component of an open. Using this optional
490 usual 0 or -ve . This method is only called if the last component is
496 tmpfile: called in the end of O_TMPFILE open(). Optional, equivalent to
521 lru_cache_add and mark_page_active needs to be called whenever the
539 complete. While waiting ->sync_page (if defined) will be called on
607 writepage: called by the VM to write a dirty page to backing store.
625 readpage: called by the VM to read a page from backing store.
626 The page will be Locked when readpage is called, and should be
631 that all succeeds, ->readpage will be called again.
633 writepages: called by the VM to write out pages associated with the
642 set_page_dirty: called by the VM to set a page dirty.
645 a page is dirtied. This is called, for example, when a memory
650 readpages: called by the VM to read pages associated with the address_space
679 which case write_end is not called.
682 be called. len is the original len passed to write_begin, and copied
684 if write_begin was called with the AOP_FLAG_UNINTERRUPTIBLE flag).
692 bmap: called by the VFS to map a logical block offset within object to
703 i_op->open() was called on. It may be useful for stacking filesystems
708 will be called when part or all of the page is to be removed
719 releasepage: releasepage is called on PagePrivate pages to indicate
740 freepage: freepage is called once the page is no longer visible in
742 data. Since it may be called by the memory reclaimer, it
746 direct_IO: called by the generic read/write routines to perform
839 Again, all methods are called without any locks being held, unless
842 llseek: called when the VFS needs to move the file position index
844 read: called by read(2) and related system calls
848 write: called by write(2) and related system calls
852 iterate: called when the VFS needs to read the directory contents
854 poll: called by the VFS when a process wants to check if there is
858 unlocked_ioctl: called by the ioctl(2) system call.
860 compat_ioctl: called by the ioctl(2) system call when 32 bit system calls
863 mmap: called by the mmap(2) system call
865 open: called by the VFS when an inode should be opened. When the VFS
875 flush: called by the close(2) system call to flush a file
877 release: called when the last reference to an open file is closed
879 fsync: called by the fsync(2) system call
881 fasync: called by the fcntl(2) system call when asynchronous
884 lock: called by the fcntl(2) system call for F_GETLK, F_SETLK, and F_SETLKW
887 get_unmapped_area: called by the mmap(2) system call
889 check_flags: called by the fcntl(2) system call for F_SETFL command
891 flock: called by the flock(2) system call
893 splice_write: called by the VFS to splice data from a pipe to a file. This
896 splice_read: called by the VFS to splice data from file to a pipe. This
899 setlease: called by the VFS to set or release a file lock lease. setlease
903 fallocate: called by the VFS to preallocate blocks or punch a hole.
944 d_revalidate: called when the VFS needs to revalidate a dentry. This
945 is called whenever a name look-up finds a dentry in the
954 d_revalidate may be called in rcu-walk mode (flags & LOOKUP_RCU).
961 -ECHILD and it will be called again in ref-walk mode.
963 d_weak_revalidate: called when the VFS needs to revalidate a "jumped" dentry.
964 This is called when a path-walk ends at dentry that was not acquired by
975 d_weak_revalidate is only called after leaving rcu-walk mode.
977 d_hash: called when the VFS adds a dentry to the hash table. The first
984 d_compare: called to compare a dentry name with a given name. The first
998 It is a tricky calling convention because it needs to be called under
1001 d_delete: called when the last reference to a dentry is dropped and the
1007 d_release: called when a dentry is really deallocated
1009 d_iput: called when a dentry loses its inode (just prior to its
1014 d_dname: called when the pathname of a dentry should be generated.
1026 d_automount: called when an automount dentry is to be traversed (optional).
1046 d_manage: called to allow the filesystem to manage the transition from a
1088 parent's hash, the "d_delete" method is called to check whether
1099 (the d_iput() method is called). If there are other
1100 references, then d_drop() is called instead
1108 pointer is NULL, the dentry is called a "negative
1109 dentry". This function is commonly called when an inode is