From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Christoph Hellwig" <hch@lst.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kill DECLARE_MUTEX_LOCKED
Date: Fri, 20 Jul 2007 10:58:34 +0530 [thread overview]
Message-ID: <a781481a0707192228r4c4e6bdfj53449d1fc67bc641@mail.gmail.com> (raw)
In-Reply-To: <20070719211135.GA32725@lst.de>
Hi Christoph,
On 7/20/07, Christoph Hellwig <hch@lst.de> wrote:
> DECLARE_MUTEX_LOCKED was used for semaphores used as completions and
> we've got rid of them.
Thanks, I'd been meaning to do this for months :-)
Had even audited the kernel for its usage ... just didn't make or
send out a patch, sorry.
> Well, except for one in libusual that the
> maintainer explicitly wants to keep as semaphore.
That comment in libusual is quite nonsensical, IMHO. Note that
usu_init_notify is declared as DECLARE_MUTEX_LOCKED and yet the
author wants us to believe (later, when he's doing that dummy
down();
/* nothing here */
up();
stuff at line no. 181) that the semaphore is somehow "counted" ...
Has anybody tried going through all the logic in that file? Looks totally
weird to me ... :-) Nothing in there that can't be serialized using proper
primitives.
> So convert that
> useage to an explicit sema_init and kill of DECLARE_MUTEX_LOCKED so that
> new code is reminded to use a completion.
and I guess nobody cares a whit for the #if 0'ed stuff in drivers/fc4/fc.c
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Well, probably not worth much, but: Ack.
Satyam
next prev parent reply other threads:[~2007-07-20 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 21:11 Christoph Hellwig
2007-07-20 5:28 ` Satyam Sharma [this message]
2007-07-20 7:17 ` Christoph Hellwig
2007-07-20 8:18 ` Satyam Sharma
2007-07-20 18:27 ` Andrew Morton
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=a781481a0707192228r4c4e6bdfj53449d1fc67bc641@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--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
all inboxes | Powered by JetHome®