Re: [PATCH] lock assertion macros for 2.5.30

From: Jens Axboe (axboe@suse.de)
Date: Thu Aug 08 2002 - 08:23:44 EST

Next message: Trond Myklebust: "Re: O_SYNC option doesn't work (2.4.18-3)"
Previous message: Ivan Kokshaysky: "Re: PCI<->PCI bridges, transparent resource fix"
In reply to: Joshua MacDonald: "Re: [PATCH] lock assertion macros for 2.5.30"
Next in thread: Jesse Barnes: "Re: [PATCH] lock assertion macros for 2.5.30"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Aug 08 2002, Joshua MacDonald wrote:
> In order to implement MOST_NOT_HOLD_LOCK the spinlock must contain
> some record of who holds the lock, and since the SCSI-layer apparently

Correct

> does not have such a mechanism, it appears that something is broken in
> there.

I'll restate, the SCSI layer does _not_ use ASSERT_LOCK in the kernel!
If just one of the people that keep raising this point would actually
see what it does rather than assume, we would not keep seeing this
mentioned in this discussion!

-- Jens Axboe

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Trond Myklebust: "Re: O_SYNC option doesn't work (2.4.18-3)"
Previous message: Ivan Kokshaysky: "Re: PCI<->PCI bridges, transparent resource fix"
In reply to: Joshua MacDonald: "Re: [PATCH] lock assertion macros for 2.5.30"
Next in thread: Jesse Barnes: "Re: [PATCH] lock assertion macros for 2.5.30"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:16 EST