Fix for genalloc locking

From: Iwo Mergler
Date: Fri Oct 17 2008 - 01:43:50 EST


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

Kind regards,


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at