Lines Matching refs:i_rwsem

246 inode->i_rwsem
249 ``i_rwsem`` is a read/write semaphore that serializes all changes to a particular
256 This has a complementary role to that of ``d_lock``: ``i_rwsem`` on a
259 dcache hold ``i_rwsem`` on the relevant directory inode and briefly take
262 memory pressure.  This uses ``d_lock``, but ``i_rwsem`` plays no role.
268 falls back to ``lookup_slow()`` which takes a shared lock on ``i_rwsem``, checks again that
274 sometimes need to take an exclusive lock on ``i_rwsem`` before performing the last lookup so
276 to take, or not take, ``i_rwsem`` is one of the
280 name that is not yet in the dcache - the shared lock on ``i_rwsem`` will
287 ``i_rwsem``, a thread must call ``d_alloc_parallel()``.  This allocates a
450 takes ``i_rwsem``, rechecks the cache, and then asks the filesystem
482 ``i_rwsem`` to exclude other changes while they validate and then
503 not always, take ``i_rwsem``, depending on what it finds.
807 No ``inode->i_rwsem`` or even ``rename_lock``
812 ``inode->i_rwsem`` plays no role in RCU-walk.  If some other thread does
813 take ``i_rwsem`` and modifies the directory in a way that RCU-walk needs
1215 opening a file.  Part of ``do_last()`` runs with ``i_rwsem`` held and this