From mboxrd@z Thu Jan  1 00:00:00 1970
From: arvid.brodin@enea.com (Arvid Brodin)
Date: Thu, 17 Mar 2011 21:59:42 +0100
Subject: inconsistent lock state on call to kmem_cache_zalloc()
In-Reply-To: <AANLkTik-j-e0G9Eo98mynFbDF5K35GftBm334_CMaa+8@mail.gmail.com>
References: <4D824F44.8090501@enea.com>
	<AANLkTik-j-e0G9Eo98mynFbDF5K35GftBm334_CMaa+8@mail.gmail.com>
Message-ID: <4D82763E.4070903@enea.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Hi,

Daniel Baluta wrote:
> Hello,
> 
>> The call to kmem_cache_zalloc() never returns; the printk() text on the line
>> after is never displayed and the system locks up. The printk() om the line
>> before displays.
> 
> What flags are you passing to kmem_cache_zalloc?

I'm using the flags passed to the urb_enqueue() function; a printk reveals
the value is 16, which would be GFP_NOIO if I read include/linux/gfp.h correctly.

> thanks,
> Daniel.

Thanks,
Arvid Brodin
Enea Services Stockholm AB