public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Jesse Barnes <jbarnes@sgi.com>, Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, jmacd@namesys.com, rml@tech9.net
Subject: Re: [PATCH] lock assertion macros for 2.5.30
Date: Fri, 9 Aug 2002 05:04:17 +0200	[thread overview]
Message-ID: <E17d04X-0000eD-00@starship> (raw)
In-Reply-To: <20020808172335.GA29509@sgi.com>

On Thursday 08 August 2002 19:23, Jesse Barnes wrote:
> On Wed, Aug 07, 2002 at 07:19:21PM -0300, Rik van Riel wrote:
> > Looks good to me. Would be even better if you removed MUST_NOT_HOLD ;)
> 
> Ok, here's yet another version.  I've removed the conversion of the
> scsi layer's ASSERT_LOCK macros as well as the silly version of
> MUST_NOT_HOLD.  Other things people seem interested in:
>   o sleeping function assertions
>   o lock ordering enforcement
>   o lock recursion detection
>   o more assertion checks in other parts of the kernel
> 
> Should any of the above be included in this patch?

You would just have to break the patch up again when you submit it.  You
might want create a patch that demonstrates its usage, by adding some
asserts to core code and removing comments where the assert makes them
redundant.

> If so, I can try
> to hack one or more of them together, otherwise maybe this is ok to go
> in?

It's looking good.

-- 
Daniel

  parent reply	other threads:[~2002-08-09  2:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07 20:51 [PATCH] lock assertion macros for 2.5.30 Jesse Barnes
2002-08-07 21:02 ` Rik van Riel
2002-08-07 21:08   ` Jesse Barnes
2002-08-07 21:21     ` Rik van Riel
2002-08-07 21:39       ` Jesse Barnes
2002-08-07 21:44         ` Rik van Riel
2002-08-08  7:58         ` Marcin Dalecki
2002-08-08 11:09           ` Daniel Phillips
2002-08-07 22:15       ` Jesse Barnes
2002-08-07 22:19         ` Rik van Riel
2002-08-08 17:23           ` Jesse Barnes
2002-08-08 17:36             ` Rik van Riel
2002-08-08 17:39               ` Jesse Barnes
2002-08-09  2:56                 ` Daniel Phillips
2002-08-12 21:03                   ` [PATCH] lock assertion macros for 2.5.31 Jesse Barnes
     [not found]                     ` <3D5829B9.D281B855@zip.com.au>
     [not found]                       ` <20020812223645.GB40343@sgi.com>
     [not found]                         ` <3D5840E9.89C8680C@zip.com.au>
2002-08-21 18:26                           ` Jesse Barnes
2002-08-21 18:40                             ` Andrew Morton
2002-08-21 18:46                               ` Jesse Barnes
2002-08-09  3:04             ` Daniel Phillips [this message]
2002-08-09  4:12               ` [PATCH] lock assertion macros for 2.5.30 Bernd Eckenfels
2002-08-07 22:30         ` Daniel Phillips
2002-08-07 22:41           ` Roman Zippel
2002-08-08  0:07           ` Thunder from the hill
2002-08-07 21:37     ` Oliver Xymoron
2002-08-08 12:55       ` Joshua MacDonald
2002-08-08 13:23         ` Jens Axboe
2002-08-08  6:00     ` Jens Axboe
2002-08-08 17:08       ` Jesse Barnes
2002-08-08 17:31         ` Rik van Riel
2002-08-08 17:35           ` Jesse Barnes
2002-08-08 17:43           ` Joshua MacDonald
2002-08-08 17:47             ` Rik van Riel
     [not found] <0C01A29FBAE24448A792F5C68F5EA47D2D4437@nasdaq.ms.ensim.com>
2002-08-08 18:52 ` Paul Menage
2002-08-08 19:00   ` Rik van Riel

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=E17d04X-0000eD-00@starship \
    --to=phillips@arcor.de \
    --cc=jbarnes@sgi.com \
    --cc=jmacd@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=rml@tech9.net \
    /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