Lines Matching refs:data
90 sle64 mft_lcn; /* Cluster location of mft data. */
197 * transfer has occurred when the data was written.
235 in data attribute. If cluster size > 4kiB,
238 FILE_LogFile = 2, /* Journalling log in data attribute. */
243 FILE_AttrDef = 4, /* Array of attribute definitions in data
247 data attribute. */
248 FILE_Boot = 7, /* Boot sector (always at cluster 0) in data
251 data attribute. */
252 FILE_Secure = 9, /* Shared security descriptors in data attribute
257 characters in data attribute. */
332 * of 2, thus making more space available for more files/data. This process is
439 * multi sector transfer protection wouldn't work. As you can't protect data
441 * When reading we obviously use the data from the ntfs record header.
516 * multi sector transfer protection wouldn't work. As you can't protect data
518 * When reading we obviously use the data from the ntfs record header.
530 * present in the data attribute of the $AttrDef system file.
653 * The data attribute of FILE_AttrDef contains a sequence of attribute
704 * Only the data attribute is ever compressed in the current ntfs driver in
705 * Windows. Further, compression is only applied when the data attribute is
717 * 1) The data in the block is all zero (a sparse block):
726 * 2) The data in the block is not compressed:
729 * compressed data still occupies X clusters, then the uncompressed data
736 * 3) The data in the block is compressed:
757 * sparse entry does not follow the first data containing entry with
761 * just the right amount of data to make up a compression block, thus this data
993 /* 8*/ sle64 last_data_change_time; /* Time the data attribute was last
1046 Translate via $SII index and $SDS data stream
1202 /* 10*/ sle64 last_data_change_time; /* Time the data attribute was last
1209 for the data attribute. So for
1217 /* 30*/ sle64 data_size; /* Byte size of actual data in data
1280 * and the corresponding mft_record numbers as the index entry data parts.
1282 * The data part (defined below) also contains three other object_ids:
1624 * data depends on the ACE type.
1651 /* Right to read data from the file. (FILE) */
1656 /* Right to write data to the file. (FILE) */
1661 /* Right to append data to the file. (FILE) */
2071 * FILE_Secure contains no unnamed data attribute, i.e. it has zero length. It
2072 * does, however, contain two indexes ($SDH and $SII) as well as a named data
2079 * data attribute. The $SII index is sorted by ascending security_id.
2083 * the security descriptor's storage location within the $SDS data attribute.
2086 * new security descriptor is already present in the $SDS data stream), if a
2098 * security_id and is added to the $SDS data attribute. Then, entries
2099 * referencing the this security descriptor in the $SDS data attribute are
2109 * This header precedes each security descriptor in the $SDS data stream.
2110 * This is also the index entry data part of both the $SII and $SDH indexes.
2151 * The $SDS data stream contains the security descriptors, aligned on 16-byte
2159 * $SDS data stream and the second copy will be at offset 0x451d0.
2283 u8 data[]; /* The file's data contents. */
2426 * multi sector transfer protection wouldn't work. As you can't protect data
2428 * When reading use the data from the ntfs record header.
2442 * below. Note, that there is no index data associated with the index entries.
2501 * The $O index entry data is the user_id of the user corresponding to the SID.
2505 * The $Q index entry data is the quota control entry and is defined below.
2591 struct { /* Used for views/indexes to find the entry's data. */
2631 struct { /* Used for views/indexes to find the entry's data. */
2657 the data part of the index. */
2664 control entry in the data part of
2667 /* The (optional) index data is inserted here when creating. */
2672 vcn references the corresponding cluster in the data
2716 * bit 30: High-latency bit. If set, accessing the first byte of data will
2717 * be slow. (E.g. the data is stored on a tape drive.)
2754 le16 reparse_data_length; /* Byte size of reparse data. */
2860 * The following information is about the data structures that are contained
2867 * of multiple data decryption/recovery fields.
2869 * Each data decryption/recovery field starts with a EFS_DF_HEADER and the next
2873 * The data decryption/recovery field contains an EFS_DF_CERTIFICATE_HEADER, a
2904 /* 64*/ le32 offset_to_ddf_array;/* Offset in bytes to the array of data
2907 le32 offset_to_drf_array;/* Offset in bytes to the array of data
2923 le32 df_count; /* Number of data decryption/recovery fields in
2937 /* 0*/ le32 df_length; /* Length of this data decryption/recovery
2943 the data decryption/recovery field. */