All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [patch 24/51] ext3: wait on all pending commits in ext3_sync_fs
Date: Thu, 6 Nov 2008 17:42:02 -0500	[thread overview]
Message-ID: <20081106224202.GA29038@mit.edu> (raw)
In-Reply-To: <20081106142020.b64dee83.akpm@linux-foundation.org>

On Thu, Nov 06, 2008 at 02:20:20PM -0800, Andrew Morton wrote:
> On Thu, 6 Nov 2008 16:44:31 -0500
> Theodore Tso <tytso@mit.edu> wrote:
> 
> > My version of this patch also cleaned up the following comment, which
> > has been wrong since 2.5.70 or thereabouts...
> 
> oh, I didn't spot that.
> 
> I looked at the version in linux-next and saw that it was propagating
> the error value back to the VFS as well.  Or maybe that was done in a
> separate patch, dunno.  But while that's a good change, I felt that we
> should separate it from this bugfix.  I meant to mention it but I
> forgot, sorry.

Fair enough.  Propagating the return value to the VFS is also a
cleanup, although given that the VFS drops return value on the floor,
I considered it a risk-free change and included it in the ext4 version
of the patch.  But yeah, I can see why separating could be argued to
be the right thing.

So that means we'll need two cleanup patches for ext3; one to fix the
comment, and another to propagate the error code back to the VFS.

	     	     		      	    	 - Ted

  reply	other threads:[~2008-11-06 22:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 20:53 [patch 24/51] ext3: wait on all pending commits in ext3_sync_fs akpm
2008-11-06 21:44 ` Theodore Tso
2008-11-06 22:20   ` Andrew Morton
2008-11-06 22:42     ` Theodore Tso [this message]
2008-11-07 14:58       ` Arthur Jones

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=20081106224202.GA29038@mit.edu \
    --to=tytso@mit.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@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.