Re: [patch 16/61] lock validator: fown locking workaround

On Mon, 29 May 2006 23:24:23 +0200
Ingo Molnar <[email protected]> wrote:

> temporary workaround for the lock validator: make all uses of
> f_owner.lock irq-safe. (The real solution will be to express to
> the lock validator that f_owner.lock rules are to be generated
> per-filesystem.)

This description forgot to tell us what problem is being worked around.

This patch is a bit of a show-stopper.  How hard-n-bad is the real fix?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 16/61] lock validator: fown locking workaround
    • From: Ingo Molnar <[email protected]>

• References:
  • [patch 00/61] ANNOUNCE: lock validator -V1
    • From: Ingo Molnar <[email protected]>
  • [patch 16/61] lock validator: fown locking workaround
    • From: Ingo Molnar <[email protected]>

• Prev by Date: Re: [patch 51/61] lock validator: special locking: sock_lock_init()
• Next by Date: Re: [patch 27/61] lock validator: prove spinlock/rwlock locking correctness
• Previous by thread: [patch 16/61] lock validator: fown locking workaround
• Next by thread: Re: [patch 16/61] lock validator: fown locking workaround
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]