Re: [PATCH 01/16] printk: guard the amount written per line by devkmsg_read()

2015-04-20 Thread Petr Mladek
On Mon 2015-04-20 14:11:36, Petr Mladek wrote: > On Thu 2015-04-16 19:03:38, Tejun Heo wrote: > > devkmsg_read() uses 8k buffer and assumes that the formatted output > > message won't overrun which seems safe given LOG_LINE_MAX, the current > > use of dict and the escaping method being used;

Re: [PATCH 01/16] printk: guard the amount written per line by devkmsg_read()

2015-04-20 Thread Petr Mladek
On Thu 2015-04-16 19:03:38, Tejun Heo wrote: > devkmsg_read() uses 8k buffer and assumes that the formatted output > message won't overrun which seems safe given LOG_LINE_MAX, the current > use of dict and the escaping method being used; however, we're > planning to use devkmsg formatting wider

Re: [PATCH 01/16] printk: guard the amount written per line by devkmsg_read()

2015-04-20 Thread Petr Mladek
On Thu 2015-04-16 19:03:38, Tejun Heo wrote: devkmsg_read() uses 8k buffer and assumes that the formatted output message won't overrun which seems safe given LOG_LINE_MAX, the current use of dict and the escaping method being used; however, we're planning to use devkmsg formatting wider and

Re: [PATCH 01/16] printk: guard the amount written per line by devkmsg_read()

2015-04-20 Thread Petr Mladek
On Mon 2015-04-20 14:11:36, Petr Mladek wrote: On Thu 2015-04-16 19:03:38, Tejun Heo wrote: devkmsg_read() uses 8k buffer and assumes that the formatted output message won't overrun which seems safe given LOG_LINE_MAX, the current use of dict and the escaping method being used; however,