Lines Matching refs:that

37 Keep in mind that now you need explicit initialization of private data
40 At some point that will become mandatory.
49 Turn your foo_read_super() into a function that would return 0 in case of
79 ->rmdir() and ->rename()).  If you used to need that exclusion and do
89 - that will guarantee the same locking you used to have.  If your method or its
91 unlock_kernel() so that they would protect exactly what needs to be
125 	FS_SINGLE is gone (actually, that had happened back when ->get_sb()
133 watch for ->i_mutex-grabbing code that might be used by your ->setattr().
149 It is planned that this will be required for exporting once the code
169 'test' is an additional function that can be used when the inode
171 should be a non-blocking function that initializes those parts of a
181 when appropriate. There is also a simpler iget_locked function that
196 Note that if the process of setting up a new inode fails, then iget_failed()
209 and let it call whatever you had as ->revlidate() + (for symlinks that
218 	* we know that parent had been locked (e.g. we are looking at
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
225 a few holes of that kind - unprotected access to ->d_parent leading to
245 return - that will guarantee the same locking you used to have.  If
247 shift lock_kernel() and unlock_kernel() so that they would protect
254 shifted into individual fs sb_op functions where it's not clear that
272 way by that code fixing will become trivial; until then nothing can be
306 simply of return 1.  Note that all actual eviction work is done by caller after
318 free the on-disk inode, you may end up doing that while ->write_inode() is writing
370 the benefits of rcu-walk mode. We will begin to add filesystem callbacks that
376 	d_revalidate is a callback that is made on every path element (if
382 	permission and check_acl are inode permission checks that are called
401 to some pointer to returning that pointer.  On errors return ERR_PTR(...).
415 support it in some way.  The generic handler assumes that the entire file is
423 filemap_write_and_wait_range() so that all dirty pages are synced out properly.
424 You must also keep in mind that ->fsync() is not called with i_mutex held
441 two, it gets "is it an O_EXCL or equivalent?" boolean argument.  Note that
442 local filesystems can ignore tha argument - they are guaranteed that the
443 object doesn't exist.  It's remote/distributed ones that might care...
462 	taken anymore, so verify that your callbacks do not rely on it (none
469 	need now.  Remember that they have opposite orders of arguments ;-/