Lines Matching full:it
64 informative error value to report). Call it foo_fill_super(). Now declare::
95 it by internal locking (most of filesystems couldn't care less) - you
104 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
115 individual fs sb_op functions. If you don't need it, remove it.
122 free to drop it...
136 an existing filesystem, set it according to ->fs_flags::
142 FS_LITTER is gone - just remove it from fs_flags.
149 went in - and hadn't been documented ;-/). Just remove it from fs_flags
169 Briefly it allows for the definition of decode_fh and encode_fh operations
174 It is planned that this will be required for exporting once the code
201 When the inode has been created by iget5_locked(), it will be returned with the
203 the initialization. Once the inode is initialized it must be unlocked by
224 should be called on the inode to render it dead, and an appropriate error
237 ->revalidate() is gone. If your filesystem had it - provide ->getattr()
238 and let it call whatever you had as ->revlidate() + (for symlinks that
264 FS_NOMOUNT is gone. If you use it - just set SB_NOUSER in flags
273 As soon as it gets fixed is_read_only() will die.
279 ->permission() is called without BKL now. Grab it on entry, drop upon
290 shifted into individual fs sb_op functions where it's not clear that
291 it's safe to remove it. If you don't need it, remove it.
335 be used instead. It gets called whenever the inode is evicted, whether it has
341 ->drop_inode() returns int now; it's called on final iput() with
342 inode->i_lock held and it returns true if filesystems wants the inode to be
343 dropped. As before, generic_drop_inode() is still the default and it's been
344 updated appropriately. generic_delete_inode() is also alive and it consists
349 ->evict_inode() (as it used to be for each call of ->delete_inode()). Unlike
351 mark_buffer_dirty_inode()), it's your responsibility to call
355 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
358 to it.
366 0. Even on 0 refcount transition, it must be able to tolerate being called 0,
403 initialize the former in inode_init_always(), so just leave it alone in
404 the callback. It used to be necessary to clean it there, but not anymore
426 the filesystem provides it), which requires dropping out of rcu-walk mode. This
432 directory inodes on the way down a path walk (to check for exec permission). It
451 ->get_sb() is gone. Switch to use of ->mount(). Typically it's just
453 the function type. If you were doing it manually, just switch from setting
473 SEEK_DATA. You can handle this by returning -EINVAL, but it would be nicer to
474 support it in some way. The generic handler assumes that the entire file is
485 anymore, so if you require i_mutex locking you must make sure to take it and
486 release it yourself.
493 misusing it. Replacement: d_make_root(inode). On success d_make_root(inode)
497 for the inode. If d_make_root(inode) is passed a NULL inode it returns NULL
511 The witch is dead! Well, 2/3 of it, anyway. ->d_revalidate() and
519 two, it gets "is it an O_EXCL or equivalent?" boolean argument. Note that
521 object doesn't exist. It's remote/distributed ones that might care...
527 FS_REVAL_DOT is gone; if you used to have it, add ->d_weak_revalidate()
554 taken anymore, so verify that your callbacks do not rely on it (none
571 it entirely.
585 do _not_ use new_sync_{read,write} for ->read/->write; leave it NULL
607 nameidata isn't passed at all - nd_jump_link() doesn't need it and
614 calling conventions for ->put_link() have changed. It gets inode instead of
615 dentry, it does not get nameidata at all and it gets called only when cookie
616 is non-NULL. Note that link body isn't available anymore, so if you need it,
617 store it as cookie.
628 you've done inode_nohighmem() it's safe to use, but if you allocate and
646 set_delayed_call() where it used to set ``*cookie``.
667 it's a symlink. Checking ->i_mode is really needed now. In-tree we had
676 they used to - they just take it exclusive. However, ->lookup() may be
683 data structures needs exclusion for some reason, arrange it
700 between it and lseek on the same struct file), but if your directory
733 used it for finding the struct super_block involved, dentry->d_sb will
734 work just as well; if it's something more complicated, use dentry->d_parent.
735 Just be careful not to assume that fetching it more than once will yield
736 the same value - in RCU mode it could change under you.
758 dentry separately, and it now has request_mask and query_flags arguments
769 value for 'called finish_no_open(), open it yourself' case has become
783 so the caller needs to drop the inode reference it held.
818 just get rid of it. Synchronous work (e.g. the stuff that can't
822 done by ->alloc_inode(). IOW, if it's cleaning up the stuff that
828 * if ->destroy_inode() is non-NULL, it gets called
829 * if ->free_inode() is non-NULL, it gets scheduled by call_rcu()
833 Note that the callback (be it via ->free_inode() or explicit call_rcu()
837 there, but that's it. Freeing memory in the callback is fine; doing
893 whereas previously it could be paired with mnt_drop_write() as well.
901 you don't need iov_iter_advance() after it. However, if you decide to use
908 Calling conventions for file_open_root() changed; now it takes struct path *
917 no_llseek is gone; don't set .llseek to that - just leave it NULL instead.
918 Checks for "does that file have llseek(2), or should it fail with ESPIPE"
926 returning 0 or -E... it returns bool now. false means "no more" (as -E... used
936 Calling conventions for ->tmpfile() have changed. It now takes a struct
946 Calling convention for ->huge_fault has changed. It now takes a page
947 order instead of an enum page_entry_size, and it may be called without the
950 for themselves. If they do need it, they can return VM_FAULT_RETRY to
986 particularly useful. It wasn't possible to go from block device to owning
999 reuse it.
1017 is now a unique superblock and thus block devices associated with it cannot be
1029 superblock is ready the caller will simply reuse it.
1042 superblock of the filesystem type anymore then it has given up ownership of
1045 As this is a VFS level change it has no practical consequences for filesystems
1055 ->rename() - it's done by the caller now [that item should've been added in
1063 by any locks; just don't do it if the old parent is the same as the new one.