From: moiz kohari <moiz_kohari@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Posix record locking.
Date: Tue, 25 Nov 2003 07:19:29 -0500 [thread overview]
Message-ID: <3FC348D1.8060408@yahoo.com> (raw)
Hi,
I am looking at posix record locking with nfs and I have a couple of
questions:
1. The fcntl_setlk() calls nfs_lock() (towards the end of fcntl_setlk by
calling filp->f_op->lock), fcntl_setlk() then calls posix_lock_file()
(where all the vfs magic happens for file locks). If nfs_lock() returns
successful (server has granted the lock) but the subsequent
posix_lock_file() fails (due to deadlock, conflict or low memory), we
never go back to the server to clean up this lock. Is this a problem or
am I missing something?
2. nfs_lock() calls nlmclnt_proc() after we pick up the kernel lock
(lock_kernel()). The nlmclnt_proc() goes on to call:
nlmclnt_lock()
nlmclnt_call()
rpc...
Is this OK? Are we going over the wire while holding the kernel lock?
Best Regards,
Moiz
reply other threads:[~2003-11-25 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FC348D1.8060408@yahoo.com \
--to=moiz_kohari@yahoo.com \
--cc=linux-kernel@vger.kernel.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