tree 865f7c9374fd2c4f072c17b97aff2225bfc06a75
parent 9451f8519c5e6d5d064c30033fc3d4ce77de321c
author Anton Altaparmakov <[EMAIL PROTECTED]> Thu, 03 Mar 2005 16:38:59 +0000
committer Anton Altaparmakov <[EMAIL PROTECTED]> Thu, 05 May 2005 11:17:08 +0100

NTFS: Add AT_EA in addition to AT_DATA to whitelist for being allowed to be
      non-resident in fs/ntfs/attrib.c::ntfs_attr_can_be_non_resident().

Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>

 fs/ntfs/ChangeLog |    2 ++
 fs/ntfs/attrib.c  |    7 ++++---
 2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/fs/ntfs/ChangeLog b/fs/ntfs/ChangeLog
--- a/fs/ntfs/ChangeLog
+++ b/fs/ntfs/ChangeLog
@@ -88,6 +88,8 @@ ToDo/Notes:
          checked and set in the ntfs inode as done for compressed files and
          the compressed size needs to be used for vfs inode->i_blocks instead
          of the allocated size, again, as done for compressed files.
+       - Add AT_EA in addition to AT_DATA to whitelist for being allowed to
+         be non-resident in fs/ntfs/attrib.c::ntfs_attr_can_be_non_resident().
 
 2.1.22 - Many bug and race fixes and error handling improvements.
 
diff --git a/fs/ntfs/attrib.c b/fs/ntfs/attrib.c
--- a/fs/ntfs/attrib.c
+++ b/fs/ntfs/attrib.c
@@ -1049,10 +1049,11 @@ int ntfs_attr_can_be_non_resident(const 
        ATTR_DEF *ad;
 
        /*
-        * $DATA is always allowed to be non-resident even if $AttrDef does not
-        * specify this in the flags of the $DATA attribute definition record.
+        * $DATA and $EA are always allowed to be non-resident even if $AttrDef
+        * does not specify this in the flags of the $DATA attribute definition
+        * record.
         */
-       if (type == AT_DATA)
+       if (type == AT_DATA || type == AT_EA)
                return 0;
        /* Find the attribute definition record in $AttrDef. */
        ad = ntfs_attr_find_in_attrdef(vol, type);
-
To unsubscribe from this list: send the line "unsubscribe bk-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to