From: Boaz Harrosh <bharrosh@panasas.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
stable@kernel.org
Subject: Re: [PATCH] exofs: simple_write_end does not mark_inode_dirty
Date: Tue, 05 Jan 2010 09:00:55 +0200 [thread overview]
Message-ID: <4B42E3A7.4060305@panasas.com> (raw)
In-Reply-To: <20100104154227.0be385d9.akpm@linux-foundation.org>
On 01/05/2010 01:42 AM, Andrew Morton wrote:
> On Sun, 27 Dec 2009 18:44:21 +0200
> Boaz Harrosh <bharrosh@panasas.com> wrote:
>
>>
>> exofs uses simple_write_end() for it's .write_end handler. But
>> it is not enough because simple_write_end() does not call
>> mark_inode_dirty() when it extends i_size. So even if we do
>> call mark_inode_dirty at beginning of write out, with a very
>> long IO and a saturated system we might get the .write_inode()
>> called while still extend-writing to file and miss out on the last
>> i_size updates.
>>
>> So override .write_end, call simple_write_end(), and afterwords if
>> i_size was changed call mark_inode_dirty().
>>
>> It stands to logic that since simple_write_end() was the one extending
>> i_size it should also call mark_inode_dirty(). But it looks like all
>> users of simple_write_end() are memory-bound pseudo filesystems, who
>> could careless about mark_inode_dirty(). I might submit a
>> warning-comment patch to simple_write_end() in future.
>>
>> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
>
OK, Thanks Andrew
I'll redo it ASAP before pushing to Linus
> You added this to linux-next without a "Cc: <stable@kernel.org>" to the
> changelog, so it won't be backported. However this patch should be
> backported, IMO.
>
>
Boaz
prev parent reply other threads:[~2010-01-05 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 16:44 [PATCH] exofs: simple_write_end does not mark_inode_dirty Boaz Harrosh
2010-01-04 23:42 ` Andrew Morton
2010-01-05 7:00 ` Boaz Harrosh [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=4B42E3A7.4060305@panasas.com \
--to=bharrosh@panasas.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=stable@kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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.