Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Ben Myers <bpm@sgi.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] mountd: use separate lockfiles
Date: Sat, 04 Apr 2009 07:53:45 -0400	[thread overview]
Message-ID: <49D74A49.6030509@RedHat.com> (raw)
In-Reply-To: <20090319221458.GI26378@sgi.com>



Ben Myers wrote:
> Hey Trond,
> 
> On Thu, Mar 19, 2009 at 02:53:57PM -0500, Ben Myers wrote:
>> On Thu, Mar 19, 2009 at 02:01:21PM -0400, Trond Myklebust wrote:
>>> Why do you need a second call to open() in the first place?
>> I'll give it another try.
> 
> Here it is again.  It works just fine without the second open.
> 
> Thanks,
> 	Ben
> 
> 
> From 1687f7a02cd34f76d5e6c461ca7d7bb56f3826d6 Mon Sep 17 00:00:00 2001
> From: Ben Myers <bpm@sgi.com>
> Date: Thu, 19 Mar 2009 16:44:54 -0500
> Subject: [PATCH] Mountd should use separate lockfiles
> 
> Mountd keeps file descriptors used for locks separate from those used for io
> and seems to assume that the lock will only be released on close of the file
> descriptor that was used with fcntl.  Actually the lock is released when any
> file descriptor for that file is closed.  When setexportent() is called after
> xflock() he closes and reopens the io file descriptor and defeats the lock.
> 
> This patch fixes that by using a separate file for locking, cleaning them up
> when finished.
> 
> Signed-off-by: Ben Myers <bpm@sgi.com>
Committed...

steved.

      parent reply	other threads:[~2009-04-04 11:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 17:28 [PATCH] mountd: use separate lockfiles Ben Myers
2009-03-19 18:01 ` Trond Myklebust
     [not found]   ` <1237485682.7534.39.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-19 19:53     ` Ben Myers
2009-03-19 22:14       ` Ben Myers
2009-03-25 14:47         ` bpm
2009-04-04 11:53         ` Steve Dickson [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=49D74A49.6030509@RedHat.com \
    --to=steved@redhat.com \
    --cc=bpm@sgi.com \
    --cc=linux-nfs@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