From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH v2 0/5] fat: additions to support fat_fallocate
Date: Sun, 01 Dec 2013 21:56:44 +0900 [thread overview]
Message-ID: <87siucd90z.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1384688224-2832-1-git-send-email-linkinjeon@gmail.com> (Namjae Jeon's message of "Sun, 17 Nov 2013 20:37:04 +0900")
Namjae Jeon <linkinjeon@gmail.com> writes:
> From: Namjae Jeon <namjae.jeon@samsung.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@mail.parknet.co.jp>
next prev parent reply other threads:[~2013-12-01 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 11:37 Namjae Jeon
2013-12-01 12:56 ` OGAWA Hirofumi [this message]
2013-12-05 14:21 ` Namjae Jeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87siucd90z.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome