From: Wu Fengguang <fengguang.wu@intel.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NFS: return -EAGAIN when skipped commit in nfs_commit_unstable_pages()
Date: Tue, 14 Jun 2011 10:30:42 +0800 [thread overview]
Message-ID: <20110614023042.GA5174@localhost> (raw)
In-Reply-To: <1307993886.5569.3.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
> > @@ -1521,7 +1521,7 @@ static int nfs_commit_unstable_pages(str
> > {
> > struct nfs_inode *nfsi = NFS_I(inode);
> > int flags = FLUSH_SYNC;
> > - int ret = 0;
> > + int ret = -EAGAIN;
> >
> > if (wbc->sync_mode == WB_SYNC_NONE) {
> > /* Don't commit yet if this is a non-blocking flush and there
>
> Looks good, but since this is a cleanup, I'm queueing it for 3.1 rather
> than pushing it in the regression-fixing window.
OK, thanks!
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NFS: return -EAGAIN when skipped commit in nfs_commit_unstable_pages()
Date: Tue, 14 Jun 2011 10:30:42 +0800 [thread overview]
Message-ID: <20110614023042.GA5174@localhost> (raw)
In-Reply-To: <1307993886.5569.3.camel@lade.trondhjem.org>
> > @@ -1521,7 +1521,7 @@ static int nfs_commit_unstable_pages(str
> > {
> > struct nfs_inode *nfsi = NFS_I(inode);
> > int flags = FLUSH_SYNC;
> > - int ret = 0;
> > + int ret = -EAGAIN;
> >
> > if (wbc->sync_mode == WB_SYNC_NONE) {
> > /* Don't commit yet if this is a non-blocking flush and there
>
> Looks good, but since this is a cleanup, I'm queueing it for 3.1 rather
> than pushing it in the regression-fixing window.
OK, thanks!
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Trond Myklebust
<Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
"linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] NFS: return -EAGAIN when skipped commit in nfs_commit_unstable_pages()
Date: Tue, 14 Jun 2011 10:30:42 +0800 [thread overview]
Message-ID: <20110614023042.GA5174@localhost> (raw)
In-Reply-To: <1307993886.5569.3.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
> > @@ -1521,7 +1521,7 @@ static int nfs_commit_unstable_pages(str
> > {
> > struct nfs_inode *nfsi = NFS_I(inode);
> > int flags = FLUSH_SYNC;
> > - int ret = 0;
> > + int ret = -EAGAIN;
> >
> > if (wbc->sync_mode == WB_SYNC_NONE) {
> > /* Don't commit yet if this is a non-blocking flush and there
>
> Looks good, but since this is a cleanup, I'm queueing it for 3.1 rather
> than pushing it in the regression-fixing window.
OK, thanks!
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-14 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 14:04 [PATCH] NFS: return -EAGAIN when skipped commit in nfs_commit_unstable_pages() Wu Fengguang
2011-06-13 19:38 ` Trond Myklebust
[not found] ` <1307993886.5569.3.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
2011-06-14 2:30 ` Wu Fengguang [this message]
2011-06-14 2:30 ` Wu Fengguang
2011-06-14 2:30 ` Wu Fengguang
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=20110614023042.GA5174@localhost \
--to=fengguang.wu@intel.com \
--cc=Trond.Myklebust@netapp.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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.