From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Ravishankar N <cyberax82@gmail.com>,
Amit Sahrawat <amit.sahrawat83@gmail.com>
Subject: Re: [PATCH] fat: Support fallocate on fat.
Date: Thu, 12 Jul 2012 19:13:44 +0900 [thread overview]
Message-ID: <87r4shp9rb.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd_sWKMOQqyPyteoPbcy8_z6=e53DC8sYTcHgMX4EC10Cw@mail.gmail.com> (Namjae Jeon's message of "Wed, 11 Jul 2012 13:22:31 +0900")
Namjae Jeon <linkinjeon@gmail.com> writes:
>> I guess, if Windows truncates the above clusters than file size, it may
>> be prefer to truncate on linux too. We really need it over umount?
>> We never know the file whether corrupted or preallocated.
>>
>> And at least for now, it would be better to put under CONFIG_FAT_FALLOC
>> or such, and warn it as unofficial way to preallocation on the
>> explanation of CONFIG_FAT_FALLOC.
>>
>> Sorry, I'm still not reviewing the detail of code yet, like locking. And
>> I'm still not convinced whether we should add this hack (unofficial way)...
> Hi OGAWA.
> Sorry for late response.
> Currently I am looking for best solution for fallocate support.
> next patch will be upated like the following.
> 1. There is no security bug.
> 2. Fix issue takes long time while preallocating.
> 3. No compatibility issue.
> Let' discuss after seeing next version's patch again.
Sure, thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2012-07-12 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 3:07 [PATCH] fat: Support fallocate on fat Namjae Jeon
2012-07-08 13:06 ` OGAWA Hirofumi
2012-07-09 6:43 ` Namjae Jeon
2012-07-09 10:55 ` OGAWA Hirofumi
2012-07-09 11:14 ` Namjae Jeon
2012-07-09 11:32 ` OGAWA Hirofumi
2012-07-11 4:22 ` Namjae Jeon
2012-07-12 10:13 ` OGAWA Hirofumi [this message]
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=87r4shp9rb.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=amit.sahrawat83@gmail.com \
--cc=cyberax82@gmail.com \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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