From: Michael Lang <Michael.Lang@jackal-net.at>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Kernel Panic when accessing NFS share and locking files
Date: Thu, 15 May 2008 09:20:32 +0200 [thread overview]
Message-ID: <482BE440.9070206@jackal-net.at> (raw)
In-Reply-To: <20080514205528.3bf3955d@infradead.org>
Arjan van de Ven wrote:
> On Wed, 14 May 2008 20:49:32 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
>
>> On Wed, 14 May 2008 19:27:36 +0200 Michael Lang
>> <Michael.Lang@jackal-net.at> wrote:
>>
>>
>>> Hi,
>>>
>>> we encountered a serious problem, when using Solaris NFS (Server)
>>> accessing it with a CentOS5.1/RHEL5.1 client.
>>>
>
>
>
>
>> Which kernel version is being used?
>>
>
> that'll be a 2.6.18 variant ;)
>
> there have been some, but not too many, reports of a trace like this:
> http://www.kerneloops.org/search.php?search=__fput
>
thanks for your quick response ...
yes it's the hole 2.6.18+ series which is provided by RedHat, i'm
currently compiling a 2.6.25-3 to verify that the problem still persists in
the new versions. I'll try to get it running today an let you know, if
so i'll forward the code and instructions how to recreate the problem to the
enclosed recipients only ...
kind regards
Michael Lang
next prev parent reply other threads:[~2008-05-15 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 17:27 Kernel Panic when accessing NFS share and locking files Michael Lang
2008-05-15 3:49 ` Andrew Morton
2008-05-15 3:55 ` Arjan van de Ven
2008-05-15 7:20 ` Michael Lang [this message]
2008-05-15 11:30 ` Michael Lang
2008-05-19 21:13 ` J. Bruce Fields
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=482BE440.9070206@jackal-net.at \
--to=michael.lang@jackal-net.at \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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