From: David Howells <dhowells@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] AFS: Implement file locking
Date: Sun, 27 May 2007 00:55:30 +0100 [thread overview]
Message-ID: <7436.1180223730@redhat.com> (raw)
In-Reply-To: <20070526022342.GA20905@fieldses.org>
J. Bruce Fields <bfields@fieldses.org> wrote:
> > + if (!afs_lock_manager) {
> > + afs_lock_manager = create_singlethread_workqueue("kafs_lockd");
> > + if (!afs_lock_manager)
> > + return -ENOMEM;
> > + }
> > + return 0;
>
> Doesn't this need some locking?
Oops. Yes. It used to be inside the lock_kernel() section, but has since
escaped.
> Do you allow upgrades and downgrades? (Just curious.)
AFS does not, as far as I know. Upgrades are dangerous anyway as you can get
deadlock quite easily.
> > + /* if we've already got a readlock on the server and no waiting
> > + * writelocks, then we might be able to instantly grant another
>
> Is that comment correct? (You don't really test for "waiting
> writelocks", do you?)
Locally, yes. 'if (list_empty(&vnode->pending_locks))' covers it quite
handily. I can't do anything about checking the server.
David
next prev parent reply other threads:[~2007-05-26 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 16:55 [PATCH] AFS: Implement file locking David Howells
2007-05-25 7:31 ` Jiri Slaby
2007-05-26 2:23 ` J. Bruce Fields
2007-05-26 3:11 ` Kyle Moffett
2007-05-27 0:12 ` David Howells
2007-05-26 23:55 ` David Howells [this message]
2007-05-27 2:25 ` J. Bruce Fields
2007-05-27 8:51 ` David Howells
2007-05-27 16:12 ` J. Bruce Fields
2007-05-29 9:34 ` David Howells
2007-05-29 20:08 ` J. Bruce Fields
2007-05-29 12:43 ` David Howells
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=7436.1180223730@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.