mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	Damien Wyart <damien.wyart@free.fr>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc2-mm2 : empty files on vfat file system
Date: Sun, 22 Oct 2006 18:11:36 +0900	[thread overview]
Message-ID: <87lkn8sojb.fsf@duaron.myhome.or.jp> (raw)
In-Reply-To: <20061022015028.GB17694@wotan.suse.de> (Nick Piggin's message of "Sun\, 22 Oct 2006 03\:50\:28 +0200")

Nick Piggin <npiggin@suse.de> writes:

> On Sun, Oct 22, 2006 at 05:38:38AM +0900, OGAWA Hirofumi wrote:
>> 
>> As I said in this thread, generic_cont_expand() uses "to == from".
>> Should we fix generic_cont_expand() instead? I don't know the
>> background of this patch.
>
> OK I have to write an RFC for various fs developers, so I'll be sure
> to include you.
>
> We want to be able to pass in a short (possibly zero) commit_write
> length if the page data can not be fully copied.

Thanks. So, if the range is zero, what should fs driver do?

> generic_cont_expand seems to be using that as a shorthand for
> "update the i_size but don't mark anything uptdoate"? If so, I think
> it would be nice to fix it. Why does it even need to go through the
> prepare/commit?

It's not only for updating ->i_size.

__generic_cont_expand() is used for expanding ->i_size by trucate(2).
In FAT case, it needs to fill the hole by zero and dirty it before
write new ->i_size. The ->prepare_write() does it, and ->commit_write()
writes ->i_size and dirty inode in __generic_cont_expand().

Anyway, if it's required, maybe we would be able to change
__generic_cont_expand().
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2006-10-22  9:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21 10:44 Damien Wyart
2006-10-21 13:24 ` OGAWA Hirofumi
2006-10-21 13:29   ` OGAWA Hirofumi
2006-10-21 17:38   ` Damien Wyart
2006-10-21 20:17     ` OGAWA Hirofumi
2006-10-21 20:19     ` Andrew Morton
2006-10-21 20:24       ` Andrew Morton
2006-10-22  1:34         ` Nick Piggin
2006-10-21 20:38       ` OGAWA Hirofumi
2006-10-22  1:50         ` Nick Piggin
2006-10-22  9:11           ` OGAWA Hirofumi [this message]
2006-10-22  9:25             ` Nick Piggin
2006-10-23 20:39     ` Mel Gorman

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=87lkn8sojb.fsf@duaron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=akpm@osdl.org \
    --cc=damien.wyart@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    /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®