933026301cb9d41b4b8b8273d892ea71c1c3d04b |
|
01-Apr-2016 |
Mohamad Ayyash <mkayyash@google.com> |
Make squashfs work on BSD and macOS Based on https://github.com/vasi/squashfs-tools Change-Id: Ia2b04541652ef4f0cf8d6ff1daf106d6db32e278 Signed-off-by: Mohamad Ayyash <mkayyash@google.com>
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
ed19eb0649f624b6aa994b9d9c387391970ee5cf |
|
29-Dec-2012 |
Phillip Lougher <phillip@squashfs.org.uk> |
unsquashfs: Improve lsetxattr errror handling Improve handling of ENOTSUP (not supported), ENOSPC and EDQUOT (out of space) errors. In particular, disable xattr output if ENOTSUP is received, and spupress out of space error message if a lot are generated. Signed-off-by: Phillip Lougher <phillip@squashfs.org.uk>
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
9d25d6b27f74956e41dd21b569ae1c934fecb62b |
|
28-Dec-2012 |
Phillip Lougher <phillip@squashfs.org.uk> |
unsquashfs: add code to only print "not superuser" error message once When running as non-superuser if unsquashfs encounters a non user.xxx xattr, it will print an error message as it cannot extract these xattrs whilst running as a normal user process. Unfortunately, for many filesystems, every file can be inadertantly tagged with a security.xxx xattr, with the direct result trying to unsquash these results in screenfulls of the same error message! The previous commit added a -user-xattr option to suppress these error messages, but this commit goes further, and adds code to suppress the error message after it printed once, and adds advice on how to prevent this one error message from being printed in the future! Signed-off-by: Phillip Lougher <phillip@squashfs.org.uk>
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
498da46ad7e6bd0a1fac0ec81d85ce1ac56bf385 |
|
28-Dec-2012 |
Phillip Lougher <phillip@squashfs.org.uk> |
unsquashfs: add -user-xattrs option to only extract user.xxx xattrs Add -user-xattrs option to Unsquashfs to signify that only user.xxx xattrs are to be extracted. This suppresses the error message that is generated if there are non-user xattrs in the filesystem, and unsquashfs is not being run as root (and so only user.xxx xattrs can be extracted). Signed-off-by: Phillip Lougher <phillip@squashfs.org.uk>
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
1bfe70795da28679fcb5305da586ce6d8118d6bb |
|
28-Dec-2012 |
Phillip Lougher <phillip@squashfs.org.uk> |
Unsquashfs: don't treat unrecognised xattr prefixes as xattr read failure There are two users for get_xattr(), Mksquashfs uses it to read the xattrs from the filesystem on appending, and Unsquashfs uses it to retrieve the xattrs for writing to disk. Unfortunately, the two users disagree on what to do with unknown xattr prefixes, Mksquashfs wants to treat this as fatal otherwise this will cause xattrs to be be lost on appending. Unsquashfs on the otherhand should want to retrieve the xattrs which are known and to ignore the rest, this allows Unsquashfs to cope more gracefully with future versions which may have unknown xattrs, as long as the general xattr structure is adhered to, Unsquashfs should be able to safely ignore unknown xattrs, and to write the ones it knows about, this is better than completely refusing to retrieve all the xattrs. So add ignore parameter. If ignore is TRUE then don't treat unknown xattr prefixes as a failure to read the xattr. Signed-off-by: Phillip Lougher <phillip@squashfs.org.uk>
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
ea0eb6395ebf08dd4d84bf24561330d9d79a6f8f |
|
28-Dec-2012 |
Phillip Lougher <phillip@squashfs.org.uk> |
unsquashfs_xattr: fix memory leak in write_xattr() Fix memory leak in write_xattr() where the xattr_list was not freed after use. Signed-off-by: Phillip Lougher <phillip@squashfs.org.uk>
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
83d42a3fc898962aa1f1e8387f2ccb1114e0d294 |
|
01-Nov-2012 |
Phillip Lougher <phillip@squashfs.org.uk> |
Update email address Signed-off-by: Phillip Lougher <phillip@squashfs.org.uk>
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
2626d20cc991c268f6be1933d464a3fd481dfb1e |
|
12-Nov-2010 |
plougher <plougher> |
Use glibc sys/xattr.h include rather than using attr/xattr.h which isn't present by default on some distributions.
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
8d9bdbd017755257fcd417c2e8e9131540a041e8 |
|
25-Aug-2010 |
plougher <plougher> |
Fix typo in error message
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
b9ffc1244e1c81eb313a396dc2038a67e8922bea |
|
25-Aug-2010 |
plougher <plougher> |
Fix file name in comment header
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|
9184cb08f2d7e5a47d0de9bffd37bc15f6370891 |
|
11-Aug-2010 |
plougher <plougher> |
Move write_xattr out of unsquashfs.c into a separate file so that it can be conditionally compiled depending on whether XATTR support is selected or not.
/external/squashfs-tools/squashfs-tools/unsquashfs_xattr.c
|