Re: Regression in next with use printk_safe buffers in printk

From	Tony Lindgren <tony@atomide.com>
Newsgroups	linux.kernel
Subject	Re: Regression in next with use printk_safe buffers in printk
Date	2017-02-16 16:20 +0100
Message-ID	<tbw0F-82M-9@gated-at.bofh.it> (permalink)
References	(1 earlier) <taNPX-41e-7@gated-at.bofh.it> <tbcbD-3la-11@gated-at.bofh.it> <tbjd7-7Gj-3@gated-at.bofh.it> <tblyh-V3-1@gated-at.bofh.it> <tblRD-11D-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

* Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> [170215 20:26]:
> On (02/15/17 20:03), Tony Lindgren wrote:
> > * Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> [170215 17:32]:
> > > On (02/15/17 10:01), Tony Lindgren wrote:
> > > [..]
> > > > Below is another issue I noticed caused by commit f975237b7682 that
> > > > I noticed during booting.
> > > 
> > > do you mean that with f975237b7682 you _always_ see that illegal RCU
> > > usage warning?
> > 
> > Yeah on every boot on devices using cpuidle_coupled.
> 
> does this mean that with the printk-safe patches reverted
> (so, basically, the same conditions module 4 printk patches)
> you don't see illegal RCU usage reports? at the moment I can't
> see any connection between f975237b7682 and RCU usage from idle CPU.

Yes reverting those four patches I listed earlier also makes it go
away.

Regards,

Tony

Thread

Regression in next with use printk_safe buffers in printk Tony Lindgren <tony@atomide.com> - 2017-02-13 20:10 +0100
  Re: Regression in next with use printk_safe buffers in printk Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2017-02-14 17:10 +0100
    Re: Regression in next with use printk_safe buffers in printk Peter Zijlstra <peterz@infradead.org> - 2017-02-14 17:20 +0100
      Re: Regression in next with use printk_safe buffers in printk Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2017-02-14 18:00 +0100
        Re: Regression in next with use printk_safe buffers in printk Tony Lindgren <tony@atomide.com> - 2017-02-14 18:10 +0100
          Re: Regression in next with use printk_safe buffers in printk Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-02-15 05:50 +0100
        Re: Regression in next with use printk_safe buffers in printk Peter Zijlstra <peterz@infradead.org> - 2017-02-14 19:40 +0100
          Re: Regression in next with use printk_safe buffers in printk Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-02-15 05:50 +0100
    Re: Regression in next with use printk_safe buffers in printk Tony Lindgren <tony@atomide.com> - 2017-02-14 18:00 +0100
    Re: Regression in next with use printk_safe buffers in printk Tony Lindgren <tony@atomide.com> - 2017-02-15 19:10 +0100
      Re: Regression in next with use printk_safe buffers in printk Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-02-16 02:40 +0100
        Re: Regression in next with use printk_safe buffers in printk Tony Lindgren <tony@atomide.com> - 2017-02-16 05:10 +0100
          Re: Regression in next with use printk_safe buffers in printk Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-02-16 05:30 +0100
            Re: Regression in next with use printk_safe buffers in printk Tony Lindgren <tony@atomide.com> - 2017-02-16 16:20 +0100
              Re: Regression in next with use printk_safe buffers in printk Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2017-02-16 17:40 +0100
                Re: Regression in next with use printk_safe buffers in printk Tony Lindgren <tony@atomide.com> - 2017-02-16 20:20 +0100

csiph-web