...
> 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.
But who is calling ioremap or vremap from a bottom half? That isn't
permitted! Device drivers are supposed to setup their mappings ahead of
time, right?
> Would any harm be done by changing this?
Yes, reliability of vmalloc/ioremap would be degraded, whereas many of the
callers expect the system to make a reasonable attempt to perform the
operation (we all know about the sound & floppy driver transient failures
due to DMA). If such a hack must be added, it should use something like
the gfp_any macro.
-ben
-
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/