[lkml]   [2018]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 3/3] lockdep: Use line-buffered printk() for lockdep messages.
On Thu 2018-11-08 13:45:10, Sergey Senozhatsky wrote:
> On (11/07/18 16:19), Petr Mladek wrote:
> > I really hope that the maze of pr_cont() calls in lockdep.c is the most
> > complicated one that we would meet.
> Hmm... Yes, buffered/seq_buf printk looks like a hard-to-use API,
> when it comes to real world cases like this.
> So... here is a random and wild idea.
> We actually already have an easy-to-use buffered printk. And it's per-CPU.
> And it makes all printk-s on this CPU to behave like as if they were called
> on UP system. And it cures pr_cont(). And it doesn't require anyone to learn
> any new printk API names. And it doesn't require any additional maintenance
> work. And it doesn't require any printk->buffered_printk conversions. And
> it's already in the kernel. And we gave it a name. And it's printk_safe.
> a) lockdep reporting path should be atomic. And it's not a hot path,
> so local_irq_save/local_irq_restore will not cause a lot of trouble
> there probably.
> b) We already have some lockdep reports coming via printk_safe.
> All those
> printk->console_driver->scheduler->lockdep
> printk->console_driver->timekeeping->lockdep
> etc.
> came via printk_safe path. So it's not a complete novelty.
> c) printk_safe sections can nest.
> d) No premature flushes. Everything looks the way it was supposed to
> look.
> e) There are no out-of-line printk-s. We keep the actual order of events.
> f) We flush it on panic.
> g) Low maintenance costs.
> So, can we just do the following? /* a sketch */
> lockdep.c
> printk_safe_enter_irqsave(flags);
> lockdep_report();
> printk_safe_exit_irqrestore(flags);

All this looks nice. Let's look it also from the other side.
The following comes to my mind:

a) lockdep is not the only place when continuous lines get mixed.
This patch mentions also RCU stalls. The other patch mentions
OOM. I am sure that there will be more.

b) It is not obvious where printk_safe() would be necessary.
While buffered printk is clearly connected with continuous

c) I am not sure that disabling preemption would always be

d) We might need to increase the size of the per-CPU buffers if
they are used more widely.

e) People would need to learn a new (printk_safe) API when it is
use outside printk sources.

f) Losing the entire log is more painful than loosing one line
when the buffer never gets flushed.

Sigh, no solution is perfect. If only we could agree that one
way was better than the other.

Best Regards,

 \ /
  Last update: 2018-11-08 12:54    [W:0.167 / U:9.612 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site