On 2019/8/14 9:47, Chao Yu wrote:
> Hi Ju Hyung,
>
> On 2019/8/13 6:52, Park Ju Hyung wrote:
>> A lot of Linux users have big, cold "zip" files.
>
> In android, as I see, most zip file is small-sized log type, and will be
> removed
> after a roll-back, such as:
>
> time1: create log1.zip
>
On 2019/8/13 6:52, Park Ju Hyung wrote:
> Similar to .db files, these are randomly updated extremely frequently.
It looks android doesn't need this, how about adding them under "#ifndef
WITH_ANDROID"?
Thanks,
>
> Signed-off-by: Park Ju Hyung
> ---
> mkfs/f2fs_format.c | 5 +
> 1 file
Hi Ju Hyung,
On 2019/8/13 6:52, Park Ju Hyung wrote:
> A lot of Linux users have big, cold "zip" files.
In android, as I see, most zip file is small-sized log type, and will be removed
after a roll-back, such as:
time1: create log1.zip
time2: create log2.zip
time3: create log3.zip
time4: remove
Add a flag option to get xattr method that could have a bit flag of
XATTR_NOSECURITY passed to it. XATTR_NOSECURITY is generally then
set in the __vfs_getxattr path.
This handles the case of a union filesystem driver that is being
requested by the security layer to report back the xattr data
On 8/13/19 1:48 AM, Greg Kroah-Hartman wrote:
On Mon, Aug 12, 2019 at 12:32:49PM -0700, Mark Salyzyn wrote:
--- a/include/linux/xattr.h
+++ b/include/linux/xattr.h
@@ -30,10 +30,10 @@ struct xattr_handler {
const char *prefix;
int flags; /* fs private flags */
bool
On Mon, Aug 12, 2019 at 12:32:49PM -0700, Mark Salyzyn wrote:
> --- a/include/linux/xattr.h
> +++ b/include/linux/xattr.h
> @@ -30,10 +30,10 @@ struct xattr_handler {
> const char *prefix;
> int flags; /* fs private flags */
> bool (*list)(struct dentry *dentry);
> - int
