linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] [bz 192] Fixed Regression in NFS Direct I/O path
Date: Thu, 28 Oct 2010 08:38:59 -0400	[thread overview]
Message-ID: <20101028123859.GA28972@infradead.org> (raw)
In-Reply-To: <1288268274-9444-1-git-send-email-steved@redhat.com>

On Thu, Oct 28, 2010 at 08:17:54AM -0400, Steve Dickson wrote:
> A typo, introduced by commit f11ac8db, in the nfs_direct_write()
> routine causes writes with O_DIRECT set to fail with a ENOMEM error.

I guess someone should run xfstests on nfs more regularly :)


  parent reply	other threads:[~2010-10-28 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 12:17 [PATCH] [bz 192] Fixed Regression in NFS Direct I/O path Steve Dickson
2010-10-28 12:34 ` Jeff Layton
2010-10-28 13:55   ` Jeff Layton
2010-10-28 14:03     ` Trond Myklebust
2010-10-28 14:10       ` Jeff Layton
2010-10-28 12:38 ` Christoph Hellwig [this message]
2010-10-28 13:44   ` Trond Myklebust
2010-10-28 18:19 ` Trond Myklebust

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=20101028123859.GA28972@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.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;
as well as URLs for NNTP newsgroup(s).