linux-kernel - Re: Fix for genalloc locking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 21 Oct 2008 08:39:49 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Iwo Mergler <iwo@...l-direct.com.au>
Cc:	linux-kernel@...r.kernel.org, Jes Sorensen <jes@...ined-monkey.org>
Subject: Re: Fix for genalloc locking

On Fri, 17 Oct 2008 16:43:12 +1000 Iwo Mergler wrote:

> Hi,
> 
> I hit a little problem while using genalloc with a mix
> of interrupt/non-interrupt context. I believe the correct
> fix is to replace the locking calls with the _irqsave/_irqrestore
> variants. Patch follows.
> 
> Is this correct?
> 
> BTW, is there any documentation on the Lockdep warnings?
> What exactly is the meaning of {--+.} in 
> 
> (&pool->lock){--+.}, at: [<c0125d1c>] gen_pool_free+0x34/0x120

Did you read Documentation/lockdep-design.txt ?

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