From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Matt Bernstein <matt@theBachChoir.org.uk>
Cc: "H. Peter Anvin" <hpa@transmeta.com>, <alan@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: NFSv3 and linux-2.4.10-ac3 => oops
Date: Tue, 2 Oct 2001 14:03:23 +0200 [thread overview]
Message-ID: <15289.44299.915454.3729@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.33.0110021227340.31037-100000@nick.dcs.qmul.ac.uk>
In-Reply-To: <shszo7a4bxp.fsf@charged.uio.no> <Pine.LNX.4.33.0110021227340.31037-100000@nick.dcs.qmul.ac.uk>
>>>>> " " == Matt Bernstein <matt@theBachChoir.org.uk> writes:
> I wonder if this is related to oopses I sent in in the last two
> days? We're running 4GB setups with NFSv3 client and server on
> our fileservers, and the oopses might (don't really have strong
> correlation evidence yet) be related to when our fileservers
> push online backups to cheaper NFS servers (running the same
> kernel based on 2.4.9-ac10). Is there a last known good kernel
> I can try on my production systems while I try to reproduce the
> problem on smaller boxes? Or would you like me to try your
> patch?
Linus changed nfs_prepare_write() in his tree around 2.4.10-pre5. From
what I can see, Alan merged that particular patch into 2.4.9-ac11 (but
without merging in the related changes to linux/mm/filemap.c).
Argh. I see that in the patch I put out earlier today, I forgot to
also revert the removal of the kunmap() in nfs_commit_write() (sorry -
my coffee was particularly weak this morning).
Please apply the following patch to the 'ac' tree instead.
People who use Linus' tree should *not* apply this patch!!!!!
Cheers,
Trond
diff -u --recursive --new-file linux-2.4.10-reclaim/fs/nfs/file.c linux-2.4.10-ac4/fs/nfs/file.c
--- linux-2.4.10-reclaim/fs/nfs/file.c Sun Sep 23 18:48:01 2001
+++ linux-2.4.10-ac4/fs/nfs/file.c Tue Oct 2 13:40:58 2001
@@ -155,7 +155,12 @@
*/
static int nfs_prepare_write(struct file *file, struct page *page, unsigned offset, unsigned to)
{
- return nfs_flush_incompatible(file, page);
+ int status;
+ kmap(page);
+ status = nfs_flush_incompatible(file, page);
+ if (status)
+ kunmap(page);
+ return status;
}
static int nfs_commit_write(struct file *file, struct page *page, unsigned offset, unsigned to)
@@ -164,6 +169,7 @@
loff_t pos = ((loff_t)page->index<<PAGE_CACHE_SHIFT) + to;
struct inode *inode = page->mapping->host;
+ kunmap(page);
lock_kernel();
status = nfs_updatepage(file, page, offset, to-offset);
unlock_kernel();
next prev parent reply other threads:[~2001-10-02 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 23:40 NFSv3 and linux-2.4.10-ac3 => oops H. Peter Anvin
2001-10-02 9:40 ` Trond Myklebust
2001-10-02 11:32 ` Matt Bernstein
2001-10-02 12:03 ` Trond Myklebust [this message]
2001-10-02 13:49 ` Alan Cox
2001-10-02 14:03 ` Trond Myklebust
2001-10-02 13:47 ` Alan Cox
2001-10-02 14:02 ` Matt Bernstein
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=15289.44299.915454.3729@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=alan@kernel.org \
--cc=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@theBachChoir.org.uk \
/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.