From: Namjae Jeon <linkinjeon@gmail.com>
To: hirofumi@mail.parknet.co.jp, akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Namjae Jeon <linkinjeon@gmail.com>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: [PATCH v4 0/6] fat: additions to support fat_fallocate
Date: Sun, 2 Mar 2014 23:08:28 +0900 [thread overview]
Message-ID: <1393769308-3405-1-git-send-email-linkinjeon@gmail.com> (raw)
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.
v4:
- ->i_disksize is aligned by block size in fill_inode.
- use i_disksize when computing the number of cluster for fallocate.
- make fat_get_block_bmap to avoid race issue.
- use __fat_write_inode() with inode_needs_sync() in evict.
v3:
- fix i_disksize and mmu_private comments(uninit/initialized)
- remove unneeded condition in fat_bmap.
- use mmu_private instead of fclus in fat_fallocate.
- make function mark buffer new for block in fallocated region.
- use flags for bmap.
- use mmu_private instead of i_size in direct_IO.
- use flags and remove i_mutex in bmap.
- update vfat documentation.
v2:
- remove a stary unlock(from Dan Carpenter)
- check ->mmu_private and ->i_disksize to truncate uninitialized data.
Namjae Jeon (6):
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
fat: update the limitation for fat fallocate
--
1.7.11-rc0
reply other threads:[~2014-03-02 14:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1393769308-3405-1-git-send-email-linkinjeon@gmail.com \
--to=linkinjeon@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--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
all inboxes | Powered by JetHome®