Re: [PATCH 1/4] vfs: vfs-level fiemap interface

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ted, I think this is a really great definition.

jim

A couple of spelling/grammar fixes below.

Theodore Tso wrote:
   * FIEMAP_EXTENT_ENCODED

   This extent does not consistant of plain filesystem blocks but is
                          ^^^^^^^^^^
   encoded (e.g. encrypted or compressed).  Reading the data in this
extent via I/O to the block device will have undefined resuts.
   Note that it is *always* undefined to try to update the data
   in-place by writing to indicated location without the assistance of
                         ^^^^^^^^^^^^ to the
   the filesystem, or accessing the data using the information
                     ^^^^^^^^^^^^ or by
   returned by the FIEMAP interface while the filesystem is mounted.
   In other words, user applications may only read the extent data via
   I/O to the block device while the filesystem is unmounted, and then
   only if the FIEMAP_EXTENT_ENCODED flag is clear; user applications
   must not try reading or writing to the filesystem via the block
   device under any other circumstances.

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux