public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Christoph Hellwig <hch@infradead.org>, Jesse Barnes <jbarnes@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lock assertion macros for 2.5.28
Date: Sat, 27 Jul 2002 15:56:08 +0200	[thread overview]
Message-ID: <E17YS3I-0005JB-00@starship> (raw)
In-Reply-To: <20020726185416.A18629@infradead.org>

On Friday 26 July 2002 19:54, Christoph Hellwig wrote:
> On Fri, Jul 26, 2002 at 10:42:58AM -0700, Jesse Barnes wrote:
> > On Fri, Jul 26, 2002 at 04:09:18PM +0400, Joshua MacDonald wrote:
> > > 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?
> > 
> > Well, I had that in one version of the patch, but people didn't think
> > it would be useful.  Maybe you'd like to check out Oliver's comments
> > at http://marc.theaimsgroup.com/?l=linux-kernel&m=102644431806734&w=2
> > and respond?  If there's demand for MUST_NOT_HOLD, I'd be happy to add
> > it since it should be easy.  But if you're using it to enforce lock
> > ordering as Oliver suggests, then there are probably more robust
> > solutions.
> 
> Why don't you just generalize the scsi version that already support this?
> 
> reinventing the wheel everywhere..

The scsi version is stupid.  It panics instead of oopses and it takes two
parameters.

More like improving a wheel, having observed that it works better if its
round.

-- 
Daniel

  parent reply	other threads:[~2002-07-27 13:51 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
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 [this message]
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=E17YS3I-0005JB-00@starship \
    --to=phillips@arcor.de \
    --cc=hch@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox