Lines Matching full:must

120    Processes wishing to insert folios must hold this lock in shared
122    Processes wishing to remove folios must hold this lock in exclusive
131    internal to the filesystem and must protect the file mapping data
133    The filesystem author must determine how this coordination should
145    This implies that the filesystem must have already allocated space
146    on disk as ``IOMAP_MAPPED`` and the filesystem must not place any
177    These fields must always be set by the filesystem.
182      This type must never be returned in response to an ``IOMAP_WRITE``
183      operation because writes must allocate and map space, and return
185      The ``addr`` field must be set to ``IOMAP_NULL_ADDR``.
192      ``->iomap_end`` function must delete the reservation.
193      The ``addr`` field must be set to ``IOMAP_NULL_ADDR``.
213      The ``addr`` field must be set to ``IOMAP_NULL_ADDR``.
219      Areas that will not be written to must be zeroed.
221      reservation must be deleted.
245    * **IOMAP_F_BOUNDARY**: This indicates I/O and its completion must not be
246      merged with any other I/O or completion. Filesystems must use this when
257    * **IOMAP_F_ATOMIC_BIO**: This indicates write I/O must be submitted with the
260      based on HW-offload mechanism. They must also ensure that mapping updates
261      upon the completion of the I/O must be performed in a single metadata
328 The mapping must cover at least the first byte of the supplied file
401 Filesystems must still call out to the VFS to check input parameters
448 Each filesystem author must figure out the locking for themself.