Lines Matching refs:it
51 informative error value to report). Call it foo_fill_super(). Now declare
80 it by internal locking (most of filesystems couldn't care less) - you
88 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
98 individual fs sb_op functions. If you don't need it, remove it.
104 free to drop it...
116 an existing filesystem, set it according to ->fs_flags:
120 FS_LITTER is gone - just remove it from fs_flags.
126 went in - and hadn't been documented ;-/). Just remove it from fs_flags
144 Briefly it allows for the definition of decode_fh and encode_fh operations
175 When the inode has been created by iget5_locked(), it will be returned with the
177 the initialization. Once the inode is initialized it must be unlocked by
197 should be called on the inode to render it dead, and an appropriate error
208 ->revalidate() is gone. If your filesystem had it - provide ->getattr()
209 and let it call whatever you had as ->revlidate() + (for symlinks that
231 FS_NOMOUNT is gone. If you use it - just set SB_NOUSER in flags
239 As soon as it gets fixed is_read_only() will die.
244 ->permission() is called without BKL now. Grab it on entry, drop upon
254 shifted into individual fs sb_op functions where it's not clear that
255 it's safe to remove it. If you don't need it, remove it.
296 be used instead. It gets called whenever the inode is evicted, whether it has
302 ->drop_inode() returns int now; it's called on final iput() with
303 inode->i_lock held and it returns true if filesystems wants the inode to be
304 dropped. As before, generic_drop_inode() is still the default and it's been
305 updated appropriately. generic_delete_inode() is also alive and it consists
310 ->evict_inode() (as it used to be for each call of ->delete_inode()). Unlike
312 mark_buffer_dirty_inode()), it's your responsibility to call
316 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
319 to it.
326 0. Even on 0 refcount transition, it must be able to tolerate being called 0,
358 initialize the former in inode_init_always(), so just leave it alone in
359 the callback. It used to be necessary to clean it there, but not anymore
377 the filesystem provides it), which requires dropping out of rcu-walk mode. This
398 ->get_sb() is gone. Switch to use of ->mount(). Typically it's just
400 function type. If you were doing it manually, just switch from setting ->mnt_root
414 SEEK_DATA. You can hanle this by returning -EINVAL, but it would be nicer to
415 support it in some way. The generic handler assumes that the entire file is
425 anymore, so if you require i_mutex locking you must make sure to take it and
426 release it yourself.
431 misusing it. Replacement: d_make_root(inode). The difference is,
436 The witch is dead! Well, 2/3 of it, anyway. ->d_revalidate() and
441 two, it gets "is it an O_EXCL or equivalent?" boolean argument. Note that
446 FS_REVAL_DOT is gone; if you used to have it, add ->d_weak_revalidate()
462 taken anymore, so verify that your callbacks do not rely on it (none
473 it entirely.
481 do _not_ use new_sync_{read,write} for ->read/->write; leave it NULL
495 nameidata isn't passed at all - nd_jump_link() doesn't need it and
500 dentry, it does not get nameidata at all and it gets called only when cookie
501 is non-NULL. Note that link body isn't available anymore, so if you need it,
502 store it as cookie.
510 you've done inode_nohighmem() it's safe to use, but if you allocate and
521 set_delayed_call() where it used to set *cookie.
535 it's a symlink. Checking ->i_mode is really needed now. In-tree we had
541 they used to - they just take it exclusive. However, ->lookup() may be
547 data structures needs exclusion for some reason, arrange it
558 ->iterate_shared() is added; it's a parallel variant of ->iterate().
560 between it and lseek on the same struct file), but if your directory
566 changes - it is a read-only operation, after all. If you have any
572 Old method is only used if the new one is absent; eventually it will
587 used it for finding the struct super_block involved, dentry->d_sb will
588 work just as well; if it's something more complicated, use dentry->d_parent.
589 Just be careful not to assume that fetching it more than once will yield
590 the same value - in RCU mode it could change under you.
602 dentry separately, and it now has request_mask and query_flags arguments
610 value for 'called finish_no_open(), open it yourself' case has become
621 so the caller needs to drop the inode reference it held.