On Mon, 09 Jul 2012 at 08:46 GMT, Minchan Kim <minc...@kernel.org> wrote:
>>
>> WARN_ON_ONCE would tell you what is trying to satisfy the allocation.
>
> Do you mean that it would be better to use WARN_ON_ONCE rather than raw
> printk?
> If so, I would like to insist raw printk because WARN_ON_ONCE could be
> disabled
> by !CONFIG_BUG.
> If I miss something, could you elaborate it more?
>
Raw printk could be disabled by !CONFIG_PRINTK too, and given that:
config PRINTK
default y
bool "Enable support for printk" if EXPERT
config BUG
bool "BUG() support" if EXPERT
default y
they are both configurable only when ERPERT, so we don't need to
worry much. :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
