From: Olivier Molteni <olivier@molteni.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Oops NFS Locking in 2.4.x
Date: Mon, 10 Sep 2001 23:26:25 +0200 [thread overview]
Message-ID: <3B9D3001.AF91D8B4@molteni.net> (raw)
In-Reply-To: <3B9C0D36.3EA20B24@molteni.net> <shsae03fizs.fsf@charged.uio.no>
Trond Myklebust wrote:
>
> Looks like 2 processes are trying to free the same lock. The problem
> is that both processes can call filp_close() at the same
> time (by calling sys_close()).
>
> The bug boils down to:
>
> - locks_unlock_delete() assumes that the BKL (kernel_lock()) is
> sufficient to protect against *thisfl_p from disappearing
> beneath it due to some second process.
> BUT
> - The call to lock() in locks_unlock_delete() sleeps when the
> underlying filesystem is NFS, hence 2 processes can race despite
> the BKL assumption.
>
> Cheers,
> Trond
Hi (2),
While searching on the sourceforge nfs list, I saw your message 4583160
posted on 10/31/2000 08:14:42 and concerning "[NFS] [PATCH] fix deadlocks
+ blocking in 2.4.0 pre6/7 knfsd locking..."
You give a patch modifying fs/loks.c wher, among other things, you were
added the new function locks_unlock_delete().
Do you know if all the patch had been included in the kernel or if some
part that deals with deadlocks were omited for some reasons ?
Do you think this corrections failed to definitively fix the deadlocks
problems ?
You are talking about semaphores in your post, do you think it's a
possible way to follow in order to fix the situation ?
Cheers,
Olivier.
prev parent reply other threads:[~2001-09-10 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 0:45 Oops NFS Locking in 2.4.x Olivier Molteni
2001-09-10 10:16 ` Trond Myklebust
2001-09-10 19:56 ` Olivier Molteni
2001-09-10 21:26 ` Olivier Molteni [this message]
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=3B9D3001.AF91D8B4@molteni.net \
--to=olivier@molteni.net \
--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