Lines Matching refs:it
58 informative error value to report). Call it foo_fill_super(). Now declare::
89 it by internal locking (most of filesystems couldn't care less) - you
98 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
109 individual fs sb_op functions. If you don't need it, remove it.
116 free to drop it...
130 an existing filesystem, set it according to ->fs_flags::
136 FS_LITTER is gone - just remove it from fs_flags.
143 went in - and hadn't been documented ;-/). Just remove it from fs_flags
163 Briefly it allows for the definition of decode_fh and encode_fh operations
195 When the inode has been created by iget5_locked(), it will be returned with the
197 the initialization. Once the inode is initialized it must be unlocked by
218 should be called on the inode to render it dead, and an appropriate error
231 ->revalidate() is gone. If your filesystem had it - provide ->getattr()
232 and let it call whatever you had as ->revlidate() + (for symlinks that
258 FS_NOMOUNT is gone. If you use it - just set SB_NOUSER in flags
267 As soon as it gets fixed is_read_only() will die.
273 ->permission() is called without BKL now. Grab it on entry, drop upon
284 shifted into individual fs sb_op functions where it's not clear that
285 it's safe to remove it. If you don't need it, remove it.
329 be used instead. It gets called whenever the inode is evicted, whether it has
335 ->drop_inode() returns int now; it's called on final iput() with
336 inode->i_lock held and it returns true if filesystems wants the inode to be
337 dropped. As before, generic_drop_inode() is still the default and it's been
338 updated appropriately. generic_delete_inode() is also alive and it consists
343 ->evict_inode() (as it used to be for each call of ->delete_inode()). Unlike
345 mark_buffer_dirty_inode()), it's your responsibility to call
349 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
352 to it.
360 0. Even on 0 refcount transition, it must be able to tolerate being called 0,
397 initialize the former in inode_init_always(), so just leave it alone in
398 the callback. It used to be necessary to clean it there, but not anymore
420 the filesystem provides it), which requires dropping out of rcu-walk mode. This
445 ->get_sb() is gone. Switch to use of ->mount(). Typically it's just
447 the function type. If you were doing it manually, just switch from setting
467 SEEK_DATA. You can hanle this by returning -EINVAL, but it would be nicer to
468 support it in some way. The generic handler assumes that the entire file is
479 anymore, so if you require i_mutex locking you must make sure to take it and
480 release it yourself.
487 misusing it. Replacement: d_make_root(inode). On success d_make_root(inode)
491 for the inode. If d_make_root(inode) is passed a NULL inode it returns NULL
505 The witch is dead! Well, 2/3 of it, anyway. ->d_revalidate() and
513 two, it gets "is it an O_EXCL or equivalent?" boolean argument. Note that
521 FS_REVAL_DOT is gone; if you used to have it, add ->d_weak_revalidate()
548 taken anymore, so verify that your callbacks do not rely on it (none
565 it entirely.
579 do _not_ use new_sync_{read,write} for ->read/->write; leave it NULL
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
610 is non-NULL. Note that link body isn't available anymore, so if you need it,
611 store it as cookie.
622 you've done inode_nohighmem() it's safe to use, but if you allocate and
640 set_delayed_call() where it used to set ``*cookie``.
661 it's a symlink. Checking ->i_mode is really needed now. In-tree we had
670 they used to - they just take it exclusive. However, ->lookup() may be
677 data structures needs exclusion for some reason, arrange it
692 ->iterate_shared() is added; it's a parallel variant of ->iterate().
694 between it and lseek on the same struct file), but if your directory
700 changes - it is a read-only operation, after all. If you have any
706 Old method is only used if the new one is absent; eventually it will
732 used it for finding the struct super_block involved, dentry->d_sb will
733 work just as well; if it's something more complicated, use dentry->d_parent.
734 Just be careful not to assume that fetching it more than once will yield
735 the same value - in RCU mode it could change under you.
757 dentry separately, and it now has request_mask and query_flags arguments
768 value for 'called finish_no_open(), open it yourself' case has become
782 so the caller needs to drop the inode reference it held.
817 just get rid of it. Synchronous work (e.g. the stuff that can't
821 done by ->alloc_inode(). IOW, if it's cleaning up the stuff that
827 * if ->destroy_inode() is non-NULL, it gets called
828 * if ->free_inode() is non-NULL, it gets scheduled by call_rcu()
832 Note that the callback (be it via ->free_inode() or explicit call_rcu()
836 there, but that's it. Freeing memory in the callback is fine; doing
892 whereas previously it could be paired with mnt_drop_write() as well.
900 you don't need iov_iter_advance() after it. However, if you decide to use
907 Calling conventions for file_open_root() changed; now it takes struct path *