Lines Matching refs:t

95 it by internal locking (most of filesystems couldn't care less) - you
115 individual fs sb_op functions.  If you don't need it, remove it.
149 went in - and hadn't been documented ;-/).  Just remove it from fs_flags
291 it's safe to remove it.  If you don't need it, remove it.
518 ->create() doesn't take ``struct nameidata *``; unlike the previous
521 object doesn't exist.  It's remote/distributed ones that might care...
607 nameidata isn't passed at all - nd_jump_link() doesn't need it and
616 is non-NULL.  Note that link body isn't available anymore, so if you need it,
665 i_pipe/i_link union zeroed out at inode eviction.  As the result, you can't
732 ->d_compare() doesn't get parent as a separate argument anymore.  If you
750 ->readlink is optional for symlinks.  Don't set, unless filesystem needs
806 don't need to bother with the check - d_splice_alias() will do the
810 also doesn't need a separate treatment.
818 just get rid of it.  Synchronous work (e.g. the stuff that can't
854 very suspect (and won't work in modules).  Such uses are very likely to
883 For bvec based itererators bio_iov_iter_get_pages() now doesn't copy bvecs but
901 you don't need iov_iter_advance() after it.  However, if you decide to use
917 no_llseek is gone; don't set .llseek to that - just leave it NULL instead.
985 The holder of a block device used to be the file_system_type which wasn't
986 particularly useful. It wasn't possible to go from block device to owning
988 This mechanism would only work for a single device so the block layer couldn't
1041     ->kill_sb(). In other words, if the superblock isn't on the list of
1063 by any locks; just don't do it if the old parent is the same as the new one.
1064 We really can't lock two subdirectories in same-directory rename - not without