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>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2] fat: editions to support fat_fallocate()
Date: Tue, 23 Oct 2012 16:19:14 +0900 [thread overview]
Message-ID: <877gqhk64t.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd_TaaL1-wh2UFDTRvqQ8QtWLbuiSPeXrzV_=amoT9YCyg@mail.gmail.com> (Namjae Jeon's message of "Tue, 23 Oct 2012 00:10:03 +0900")
Namjae Jeon <linkinjeon@gmail.com> writes:
>> Does this break the linux fat driver doesn't know about this
>> fallocate()? If so, it sounds like to be easy to break existent
>> drivers.
> Yes, it will break linux drivers without fallocate support. When we
> try to write to fallocated file using old drivers, it will cause write
> error and make FS read-only.
> When fallocate was implemented in other filesystem, maybe,, was there
> similar issue and concern ?
I guess it is not similar. Because other FS can change the spec (e.g. it
can be possible to use feature compat flag for it).
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2012-10-23 7:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 14:31 Namjae Jeon
2012-10-14 16:20 ` OGAWA Hirofumi
2012-10-16 4:12 ` Namjae Jeon
2012-10-16 10:14 ` OGAWA Hirofumi
2012-10-17 10:57 ` Namjae Jeon
2012-10-21 23:54 ` OGAWA Hirofumi
2012-10-22 15:10 ` Namjae Jeon
2012-10-23 7:19 ` OGAWA Hirofumi [this message]
2012-10-23 7:24 ` Namjae Jeon
2013-02-14 2:40 ` Read support for fat_fallocate()? (was [v2] fat: editions to support fat_fallocate()) Andrew Bartlett
2013-02-14 2:48 ` Andrew Bartlett
2013-02-14 6:44 ` Namjae Jeon
2013-02-14 7:07 ` Andrew Bartlett
2013-02-14 9:52 ` Namjae Jeon
2013-02-15 3:49 ` Andrew Bartlett
2013-02-18 11:36 ` OGAWA Hirofumi
2013-02-18 13:11 ` Andrew Bartlett
2013-02-18 14:25 ` Namjae Jeon
2013-02-18 14:59 ` OGAWA Hirofumi
2013-02-18 15:15 ` 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=877gqhk64t.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-fsdevel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®