Lines Matching refs:and
7 sb_set_blocksize() and sb_min_blocksize().
16 New methods: ->alloc_inode() and ->destroy_inode().
31 Add foo_alloc_inode() and foo_destroy_inode() - the former should allocate
32 foo_inode_info and return the address of ->vfs_inode, the latter should free
35 Make them ->alloc_inode and ->destroy_inode in your super_operations.
38 typically between calling iget_locked() and unlocking the inode.
47 ->read_super() is no more. Ditto for DECLARE_FSTYPE and DECLARE_FSTYPE_DEV.
50 success and negative number in case of error (-EINVAL unless you have more
63 Replace DECLARE_FSTYPE... with explicit initializer and have ->get_sb set as
73 same (i.e. parents and victim are locked, etc.).
78 Now we have the exclusion between ->lookup() and directory removal (by
79 ->rmdir() and ->rename()). If you used to need that exclusion and do
88 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
90 parts do not need BKL - better yet, now you can shift lock_kernel() and
126 went in - and hadn't been documented ;-/). Just remove it from fs_flags
127 (and see ->get_sb() entry for other actions).
141 documented at its declaration in include/linux/fs.h, and in
144 Briefly it allows for the definition of decode_fh and encode_fh operations
145 to encode and decode filehandles, and allows the filesystem to use
146 a standard helper function for decode_fh, and provide file-system specific
161 iget4() and the read_inode2 callback have been superseded by iget5_locked()
173 passed as an opaque value to both test and set functions.
176 I_NEW flag set and will still be locked. The filesystem then needs to finalize
180 The filesystem is responsible for setting (and possibly testing) i_ino
182 just takes the superblock and inode number as arguments and does the
183 test and set for you.
197 should be called on the inode to render it dead, and an appropriate error
209 and let it call whatever you had as ->revlidate() + (for symlinks that
222 Audit your code and add locking if needed. Notice that any place that is
224 had been relying on BKL and that's prone to screwups. Old tree had quite
232 (see rootfs for one kind of solution and bdev/socket/pipe for another).
247 shift lock_kernel() and unlock_kernel() so that they would protect
277 block truncatation on error exit from ->write_begin, and ->direct_IO
280 ext2_write_failed and callers for an example.
287 and vmtruncate, and the reorder the vmtruncate + foofs_vmtruncate sequence to
289 size update and on finally on-disk truncation which should not fail.
290 inode_change_ok now includes the size checks for ATTR_SIZE and must be called
295 ->clear_inode() and ->delete_inode() are gone; ->evict_inode() should
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
315 NOTE: checking i_nlink in the beginning of ->write_inode() and bailing out
316 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
325 unreferenced dentries, and is now only called when the dentry refcount goes to
332 .d_compare() calling convention and locking rules are significantly
333 changed. Read updated documentation in Documentation/filesystems/vfs.txt (and
339 .d_hash() calling convention and locking rules are significantly
340 changed. Read updated documentation in Documentation/filesystems/vfs.txt (and
357 Even though i_dentry and i_rcu share storage in a union, we will
365 atomic operations and scalability hazards on dentries and inodes (see
366 Documentation/filesystems/path-lookup.txt). d_hash and d_compare changes
369 no changes are required to the filesystem. However, this is costly and loses
382 permission and check_acl are inode permission checks that are called
399 a matter of switching from calling get_sb_... to mount_... and changing the
405 ->permission() and generic_permission()have lost flags
408 has been taken to VFS and filesystems need to provide a non-NULL ->i_op->get_acl
413 If you implement your own ->llseek() you must handle SEEK_HOLE and
416 data and there is a virtual hole at the end of the file. So if the provided
417 offset is less than i_size and SEEK_DATA is specified, return the same offset.
418 If the above is true for the offset and you are given SEEK_HOLE, return the end
425 anymore, so if you require i_mutex locking you must make sure to take it and
436 The witch is dead! Well, 2/3 of it, anyway. ->d_revalidate() and
461 called with both ->i_lock and inode_hash_lock held; the former is *not*
476 never call ->read() and ->write() directly; use __vfs_{read,write} or