Messages in this thread | | | Date | Fri, 8 Aug 2008 13:46:57 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH] printk: robustify printk |
| |
On Fri, 08 Aug 2008 22:37:39 +0200 Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Fri, 2008-08-08 at 13:32 -0700, Paul E. McKenney wrote: > > > How about if I instead add comments warning people not to put printk() > > in the relevant RCU-implementation code? That way I can be not only lazy, > > but cowardly as well! ;-) > > Well, it does spoil the party a little, we are now trading one deadlock > for another :-/ >
Yup. We could just as easily put those comments into the scheduler wakeup code.
Why are we fixing this, btw? The problem has been there forever and people who hack the wakeup code could/should know about it anyway. All they need to do is to disable klogd during development. Did the problem recently become worse for some reason?
| |