Lines Matching refs:may
25 rename_lock ->d_lock may block rcu-walk
73 all may block
89 permission: no (may not block if called in rcu-walk mode)
131 All may block [not true, see below]
171 may block
208 All except set_page_dirty and freepage may block
232 may be called from the request handler (/dev/loop).
241 "sync". These are quite different operations and the behaviour may differ
257 This may also be done to avoid internal deadlocks, but rarely.
296 written. The address_space implementation may write more (or less) pages
304 when the target page is marked as needing writeback. It may be called
319 indicate that the buffers are (or may be) freeable. If ->releasepage is zero,
325 ->launder_page() may be called prior to releasing a page if
347 inode->i_lock may block
366 inode->i_lock blocked_lock_lock may block
375 *an* inode->i_lock held. It may not be the i_lock of the inode
377 detection, since the code has to chase down the owners of locks that may
467 All may block.
542 the page may be truncated and/or invalidated, then the filesystem must lock