All of lore.kernel.org
 help / color / mirror / Atom feed
From: moiz kohari <moiz_kohari@yahoo.com>
To: nfs@lists.sourceforge.net
Subject: posix record locking?
Date: Mon, 24 Nov 2003 16:29:02 -0500	[thread overview]
Message-ID: <3FC2781E.4010107@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?

Thanks for your help and please cc my email on any responses.

Best Regards,

Moiz




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-11-25  0:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 21:29 moiz kohari [this message]
2003-11-26  0:50 ` posix record locking? Trond Myklebust

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=3FC2781E.4010107@yahoo.com \
    --to=moiz_kohari@yahoo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.