linux-kernel - Re: [PATCH v2 0/5] fat: additions to support fat

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 01 Dec 2013 21:56:44 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Namjae Jeon <linkinjeon@...il.com>
Cc:	akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, Namjae Jeon <namjae.jeon@...sung.com>
Subject: Re: [PATCH v2 0/5] fat: additions to support fat_fallocate

Namjae Jeon <linkinjeon@...il.com> writes:

> From: Namjae Jeon <namjae.jeon@...sung.com>
>
> This patch set provides support for doing fallocate operation
> on FAT filesystem.
> After series of review for the the feature
> The complete functionality is broken down into smaller subsets.
>
> v2:
>  - remove a stary unlock(from Dan Carpenter)
>  - check ->mmu_private and ->i_disksize to truncate uninitialized data.
>
> Namjae Jeon (5):
>  fat: add i_disksize to represent uninitialized size
>  fat: add fat_fallocate operation
>  fat: zero out seek range on _fat_get_block
>  fat: fallback to buffered write in case of fallocatded region on direct IO
>  fat: permit to return phy block number by fibmap in fallocated region

Let's add document about FAT's fallocate() behavior to
Documents/filesystem/vfat.txt.

I.e. it will be truncated evict_inode(). So, user has to assume
fallocate() is only valid until last close(), and user has to re-call
fallocate() after re-open to make sure fallocate() region.
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/