From: "Chakri n" <chakriin5@gmail.com>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: OOPS in shrink_dcache_for_umount
Date: Sun, 5 Aug 2007 09:39:15 -0700 [thread overview]
Message-ID: <92cbf19b0708050939r6164474di64949e4044691951@mail.gmail.com> (raw)
In-Reply-To: <20070804120105.47ae82fc@highlander.home.lan>
Hi Malte,
Thanks for the information.
Based on your suggestion I tried the following two patches on top of
2.6.18-1.8.el5 NFS code. I had to keep the changes minimum to fix this
crash in our release.
http://linux-nfs.org/Linux-2.6.x/2.6.20-rc7/linux-2.6.20-007-fix_readdir_negative_dentry.dif
http://linux-nfs.org/Linux-2.6.x/2.6.20-rc7/linux-2.6.20-008-fix_readdir_positive_dentry.dif
The systems are running for the past 7 hours with out any issues.
Hopefully this fixes it.
Regards
--Chakri
On 8/4/07, Malte Schröder <maltesch@gmx.de> wrote:
> On Thu, 2 Aug 2007 14:27:04 -0700
> "Chakri n" <chakriin5@gmail.com> wrote:
>
> > Hi,
> >
> > We are seeing this problem while unmounting file systems. It happens
> > once in a while.
> > I am able to grab the trace and core from linux-2.6.18-1.8.el5, but I
> > have observed the same problem with linux-2.6.20.1 kernel.
> >
> > Has this problem fixed in recent kernel?
> >
>
> I had those too ... but I haven't seen one in a while.
> I currently run 2.6.22 + cfs-v19 + the Patch from
> http://linux-nfs.org/Linux-2.6.x/2.6.22/linux-2.6.22-NFS_ALL.dif
>
> --
> ---------------------------------------
> Malte Schröder
> MalteSch@gmx.de
> ICQ# 68121508
> ---------------------------------------
>
>
>
next prev parent reply other threads:[~2007-08-05 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 21:27 Chakri n
2007-08-04 10:01 ` Malte Schröder
2007-08-05 16:39 ` Chakri n [this message]
2007-08-06 19:18 ` Chakri n
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=92cbf19b0708050939r6164474di64949e4044691951@mail.gmail.com \
--to=chakriin5@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maltesch@gmx.de \
--cc=nfs@lists.sourceforge.net \
/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®