From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Damien Wyart <damien.wyart@free.fr>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
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 03:34:27 +0200 [thread overview]
Message-ID: <20061022013427.GA17694@wotan.suse.de> (raw)
In-Reply-To: <20061021132431.0ced0dc6.akpm@osdl.org>
On Sat, Oct 21, 2006 at 01:24:31PM -0700, Andrew Morton wrote:
> On Sat, 21 Oct 2006 13:19:32 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>
> > On Sat, 21 Oct 2006 19:38:49 +0200
> > Damien Wyart <damien.wyart@free.fr> wrote:
> >
> > > > --- a/fs/fat/inode.c~fs-prepare_write-fixes
> > > > +++ a/fs/fat/inode.c
> > > > @@ -150,7 +150,11 @@ static int fat_commit_write(struct file
> > > > unsigned from, unsigned to)
> > > > {
> > > > struct inode *inode = page->mapping->host;
> > > > - int err = generic_commit_write(file, page, from, to);
> > > > + int err;
> > > > + if (to - from > 0)
> > > > + return 0;
> > > > +
> >
> > That should have been
> >
> > if (to - from == 0)
> > return 0;
>
> otoh, it's still wrong that we're not updating i_size. We happen to know
> that the caller will retry without dropping i_mutex, but it's a bit
> incestuous.
It can possibly fail for example if the source buffer gets unmapped.
However in the length == 0 case, that signals a failure to write anything
so we needn't update i_size, I think?
next prev parent reply other threads:[~2006-10-22 1:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 10:44 2.6.19-rc2-mm2 : empty files on vfat file system 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 [this message]
2006-10-21 20:38 ` OGAWA Hirofumi
2006-10-22 1:50 ` Nick Piggin
2006-10-22 9:11 ` OGAWA Hirofumi
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=20061022013427.GA17694@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@osdl.org \
--cc=damien.wyart@free.fr \
--cc=hirofumi@mail.parknet.co.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.