From: Jesse Barnes <jbarnes@sgi.com>
To: Jens Axboe <axboe@suse.de>
Cc: Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org, jmacd@namesys.com,
phillips@arcor.de, rml@tech9.net
Subject: Re: [PATCH] lock assertion macros for 2.5.30
Date: Thu, 8 Aug 2002 10:08:24 -0700 [thread overview]
Message-ID: <20020808170824.GA29468@sgi.com> (raw)
In-Reply-To: <20020808060045.GM2243@suse.de>
On Thu, Aug 08, 2002 at 08:00:45AM +0200, Jens Axboe wrote:
> The SCSI ASSERT_LOCK() were never used from kernel space, they are for
> the user space similator. So it was always single threaded from there
> and has no bearing on what actual kernel code does.
>
> For MUST_NOT_HOLD to work, you need to take into account which processor
> took the lock etc.
That's the only way it seems to be useful...
> > After I posted the last patch, a few people asked for MUST_NOT_HOLD so
> > I added it back in. Do you think it's a bad idea? See the last
>
> Your current version is surely worthless.
Agreed. I'll post another patch that doesn't mess with the scsi
stuff. Maybe later I can put together a useful
'lock-not-held-on-this-cpu' macro.
Thanks,
Jesse
next prev parent reply other threads:[~2002-08-08 17:04 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 ` [PATCH] lock assertion macros for 2.5.30 Daniel Phillips
2002-08-09 4:12 ` 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 [this message]
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=20020808170824.GA29468@sgi.com \
--to=jbarnes@sgi.com \
--cc=axboe@suse.de \
--cc=jmacd@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--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 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.