| To: | Chris Wright <chrisw@xxxxxxxx> |
|---|---|
| Subject: | Re: panic - Attempting to free lock with active block list |
| From: | Jan-Frode Myklebust <Jan-Frode.Myklebust@xxxxxxxxxxx> |
| Date: | Wed, 5 Jan 2005 22:38:37 +0100 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx, Eirik Thorsnes <eithor@xxxxxxxxx>, smfrench@xxxxxxxxxxxxx, trond.myklebust@xxxxxxxxxx, matthew@xxxxxx |
| In-reply-to: | <20050105123207.J469@xxxxxxxxxxxxxxxxxx> |
| Mail-followup-to: | Chris Wright <chrisw@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx, Eirik Thorsnes <eithor@xxxxxxxxx>, smfrench@xxxxxxxxxxxxx, trond.myklebust@xxxxxxxxxx, matthew@xxxxxx |
| References: | <20050105195736.GA26989@xxxxxxxxx> <20050105123207.J469@xxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Wed, Jan 05, 2005 at 12:32:07PM -0800, Chris Wright wrote:
>
> It seems likely it's nfs related in this case since it stresses the
> fs/locks code differently than local filesystems. I recall Steve French
> reporting similar issue with cifs last month.
Also found this on the linux-cifs-client list:
http://lists.samba.org/archive/linux-cifs-client/2004-December/000617.html
Is the suggested fix also relevant for fs/nfs/file.c ?
-jf
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: panic - Attempting to free lock with active block list, Chris Wright |
|---|---|
| Next by Date: | Re: panic - Attempting to free lock with active block list, Trond Myklebust |
| Previous by Thread: | Re: panic - Attempting to free lock with active block list, Chris Wright |
| Next by Thread: | Re: panic - Attempting to free lock with active block list, Trond Myklebust |
| Indexes: | [Date] [Thread] [Top] [All Lists] |