On 07/11/14 17:16, Joe Perches wrote:
> On Fri, 2014-11-07 at 16:50 +, Daniel Thompson wrote:
>> On 07/11/14 16:04, Joe Perches wrote:
>>> why insert KERN_INFO?
>>
>> vkdb_printf() and printk() can appear either way round in a stack
>> trace. Each is capable of calling the other and a flag (kd
On Fri, 2014-11-07 at 16:50 +, Daniel Thompson wrote:
> On 07/11/14 16:04, Joe Perches wrote:
> > why insert KERN_INFO?
>
> vkdb_printf() and printk() can appear either way round in a stack
> trace. Each is capable of calling the other and a flag (kdb_trap_printk)
> is used to prevent mutual
On 07/11/14 16:04, Joe Perches wrote:
> On Fri, 2014-11-07 at 12:01 +, Daniel Thompson wrote:
>> Currently when kdb traps printk messages then the raw log level prefix
>> (consisting of '\001' followed by a numeral) does not get stripped off
>> before the message is issued to the various I/O ha
On Fri, 2014-11-07 at 12:01 +, Daniel Thompson wrote:
> Currently when kdb traps printk messages then the raw log level prefix
> (consisting of '\001' followed by a numeral) does not get stripped off
> before the message is issued to the various I/O handlers supported by
> kdb. This causes anno
4 matches
Mail list logo
