From: Joshua MacDonald <jmacd@namesys.com>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lock assertion macros for 2.5.28
Date: Fri, 26 Jul 2002 16:09:18 +0400 [thread overview]
Message-ID: <20020726120918.GA22049@reload.namesys.com> (raw)
In-Reply-To: <20020725233047.GA782991@sgi.com>
On Thu, Jul 25, 2002 at 04:30:47PM -0700, Jesse Barnes wrote:
> Here's the lastest version of the lockassert patch. It includes:
> o MUST_HOLD for all architectures
> o MUST_HOLD_RW for architectures implementing rwlock_is_locked (only
> ia64 at the moment, as part of this patch)
> o MUST_HOLD_RWSEM for arcitectures that use rwsem-spinlock.h
> o MUST_HOLD_SEM for ia64
> o a call to MUST_HOLD(&inode_lock) in inode.c:__iget().
>
> I'd be happy to take patches that implement the above routines for
> other architectures and/or patches that sprinkle the macros where
> they're needed.
>
> Thanks,
> Jesse
>
Jesse,
In reiser4 we are looking forward to having a MUST_NOT_HOLD (i.e.,
spin_is_not_locked) assertion for kernel spinlocks. Do you know if any
progress has been made in that direction?
We have implemented a user-level testing framework for our file system and we
are already using a spin_is_not_locked() method, but these assertions are
disabled when compiled into the kernel.
-josh
next prev parent reply other threads:[~2002-07-26 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 23:30 [PATCH] lock assertion macros for 2.5.28 Jesse Barnes
2002-07-26 5:11 ` Marcin Dalecki
2002-07-26 17:40 ` Jesse Barnes
2002-07-27 13:59 ` Daniel Phillips
2002-07-26 12:09 ` Joshua MacDonald [this message]
2002-07-26 17:42 ` Jesse Barnes
2002-07-26 17:54 ` Christoph Hellwig
2002-07-26 18:05 ` Jesse Barnes
2002-07-27 13:56 ` Daniel Phillips
2002-07-26 19:38 ` Robert Love
2002-08-02 15:17 ` Joshua MacDonald
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=20020726120918.GA22049@reload.namesys.com \
--to=jmacd@namesys.com \
--cc=jbarnes@sgi.com \
--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.