From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: akpm@osdl.org
Cc: Chuck Lever <chuck.lever@oracle.com>,
Steve Dickson <SteveD@redhat.com>, Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH] MM: Remove [PATCH] invalidate_inode_pages2_range() debug
Date: Wed, 24 Jan 2007 20:32:33 -0800 [thread overview]
Message-ID: <20070125043233.16260.83569.stgit@lade.trondhjem.org> (raw)
From: Trond Myklebust <Trond.Myklebust@netapp.com>
NFS can handle the case where invalidate_inode_pages2_range() fails, so the
premise behind commit 8258d4a574d3a8c01f0ef68aa26b969398a0e140 is now gone.
Remove the WARN_ON_ONCE() which is causing users grief as we can see from
http://bugzilla.kernel.org/show_bug.cgi?id=7826
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
---
mm/truncate.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/mm/truncate.c b/mm/truncate.c
index 6c79ca4..54ae710 100644
--- a/mm/truncate.c
+++ b/mm/truncate.c
@@ -422,7 +422,6 @@ int invalidate_inode_pages2_range(struct
pagevec_release(&pvec);
cond_resched();
}
- WARN_ON_ONCE(ret);
return ret;
}
EXPORT_SYMBOL_GPL(invalidate_inode_pages2_range);
reply other threads:[~2007-01-25 4:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070125043233.16260.83569.stgit@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=SteveD@redhat.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®