From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm5
Date: Tue, 20 Jan 2004 10:30:20 -0800 [thread overview]
Message-ID: <20040120183020.GD23765@srv-lnx2600.matchmail.com> (raw)
In-Reply-To: <20040120000535.7fb8e683.akpm@osdl.org>
On Tue, Jan 20, 2004 at 12:05:35AM -0800, Andrew Morton wrote:
> -ext2_new_inode-cleanup.patch
> -ext2-s_next_generation-fix.patch
> -ext3-s_next_generation-fix.patch
> -ext3-journal-mode-fix.patch
What do these patches do?
> -nfsd-01-stale-filehandles-fixes.patch
> Merged
Yes!
I tested this against 2.6.1-bk2 on my knfsd server since friday, and it has
fixed my problems with stale nfs handles. Without the patch, it wouldn't
last a whole day before the errors started cropping up.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-20 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 8:05 2.6.1-mm5 Andrew Morton
2004-01-20 10:51 ` 2.6.1-mm5 dies booting, possibly network related Helge Hafting
2004-01-20 11:14 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 16:37 ` 2.6.1-mm5 Andrew Morton
2004-01-20 11:35 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 13:45 ` [PATCH] missing space in printk message (was Re: 2.6.1-mm5) Sean Neakums
2004-01-20 13:54 ` Vojtech Pavlik
2004-01-20 14:09 ` Sean Neakums
2004-01-20 16:08 ` 2.6.1-mm5 (compile stats) John Cherry
2004-01-20 21:57 ` Adrian Bunk
2004-01-20 22:15 ` John Cherry
2004-01-20 22:27 ` Adrian Bunk
2004-01-20 22:50 ` John Cherry
2004-01-20 18:30 ` Mike Fedyk [this message]
2004-01-20 18:36 ` 2.6.1-mm5 Andrew Morton
2004-01-21 0:10 ` I2C sensors error (Re: 2.6.1-mm5) Zack Winkles
2004-01-21 0:34 ` Greg KH
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=20040120183020.GD23765@srv-lnx2600.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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