public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-kernel@vger.kernel.org, nickpiggin@yahoo.com.au, akpm@osdl.org
Subject: Re: + fs-prepare_write-fixes.patch added to -mm tree
Date: Thu, 19 Oct 2006 16:09:00 -0700	[thread overview]
Message-ID: <20061019230900.GE10128@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20061019052537.GA15687@wotan.suse.de>

On Thu, Oct 19, 2006 at 07:25:37AM +0200, Nick Piggin wrote:
> I sent an RFC to linux-fsdevel, did you get that?
Yeah, I don't think I thought of my concerns at the time.


> I was planning to cc some maintainers, including you, for those
> filesystems that are non-trivial. I just hadn't had a chance to
> test it properly last night.
Cool, I appreciate that.


> OK thanks for looking at that. If the length of the commit is greater
> than 0 (but still short), then the page is uptodate so it should be
> fine to commit what we have written, I think?
That seems to make sense to me.

 
> If the length is zero, then we probably want to roll back entirely.
The thing is, rollback might be hard (or expensive) for some file systems
with more complicated tree implementations, etc.

Do we have the option in this case of just zeroing the newly allocated
portions and writing them out? Userspace would then just be seeing
that like any other hole.
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com

  reply	other threads:[~2006-10-19 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200610182150.k9ILoLNk019702@shell0.pdx.osdl.net>
2006-10-19  1:42 ` + fs-prepare_write-fixes.patch added to -mm tree Mark Fasheh
2006-10-19  5:25   ` Nick Piggin
2006-10-19 23:09     ` Mark Fasheh [this message]
2006-10-19 23:27       ` Nick Piggin
2006-10-20 18:55         ` Mark Fasheh

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=20061019230900.GE10128@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --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