Yes
> The problem: If these routines are called from a bottom half task queue
> routine then kmalloc thinks that it is being called from interrupt level
> without GFP_ATOMIC and prints a message to that effect.
Its not allowed to do this. ioremap and vremap are not callable from
bh or interrupt state.
The atomicity of the memory allocation is a minor issue to the cross CPU
coherency and deadlock issues.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/