From: David Howells <dhowells@redhat.com>
To: Arun Raghavan <arunsr@cse.iitk.ac.in>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org, satyam@infradead.org
Subject: Re: [PATCH] [keys] Use mutex instead of rw_semaphore for __key_link() serialisation
Date: Mon, 14 Apr 2008 11:23:13 +0100 [thread overview]
Message-ID: <2320.1208168593@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804140053210.9760@peripatetic.hades>
Arun Raghavan <arunsr@cse.iitk.ac.in> wrote:
> __key_link() uses an rw_semaphore as a mutex to serialise link/link calls.
> This patch converts it to explicitly use a struct mutex.
>
> Signed-off-by: Arun Raghavan <arunsr@cse.iitk.ac.in>
> Signed-off-by: Satyam Sharma <satyam@infradead.org>
Acked-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2008-04-14 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 19:33 [PATCH] [keys] Use mutex instead of rw_semaphore for __key_link() serialisation Arun Raghavan
2008-04-14 10:23 ` David Howells [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=2320.1208168593@redhat.com \
--to=dhowells@redhat.com \
--cc=arunsr@cse.iitk.ac.in \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam@infradead.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;
as well as URLs for NNTP newsgroup(s).