public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 1/5] XFS: fix error inversion problems with data flushing
Date: Thu, 6 Nov 2008 10:39:49 -0500	[thread overview]
Message-ID: <20081106153949.GA1726@infradead.org> (raw)
In-Reply-To: <20081102225133.GI19509@disturbed>

On Mon, Nov 03, 2008 at 09:51:33AM +1100, Dave Chinner wrote:
> Yes, that's the point of the patch - we get it wrong in many
> places and this fixes them so that correctly signed error values
> are returned to the higher layers....

Well, you also introduce xfs_wait_on_pages, which should at least be
documented.  And I'd have to say I don't really like adding more of
these wrappers just for the sake of it.

  reply	other threads:[~2008-11-06 15:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31  1:15 [PATCH 0/5] Miscellaneous bug fixes Dave Chinner
2008-10-31  1:15 ` [PATCH 1/5] XFS: fix error inversion problems with data flushing Dave Chinner
2008-10-31 20:18   ` Christoph Hellwig
2008-11-02 22:51     ` Dave Chinner
2008-11-06 15:39       ` Christoph Hellwig [this message]
2008-10-31  1:15 ` [PATCH 2/5] XFS: Fix double free of log tickets Dave Chinner
2008-11-12  9:20   ` Christoph Hellwig
2008-10-31  1:15 ` [PATCH 3/5] XFS: fix uninitialised variable bug in dquot release Dave Chinner
2008-10-31 20:19   ` Christoph Hellwig
2008-10-31  1:15 ` [PATCH 4/5] XFS: fix spurious uninitialised variable warning in xfs_growfs_rt Dave Chinner
2008-10-31 20:20   ` Christoph Hellwig
2008-10-31  1:15 ` [PATCH 5/5] XFS: Avoid using inodes that haven't been completely initialised Dave Chinner
2008-10-31 20:21   ` Christoph Hellwig

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=20081106153949.GA1726@infradead.org \
    --to=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /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