From: Steven Rostedt <rostedt@goodmis.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Tejun Heo <tj@kernel.org>,
Calvin Owens <calvinowens@fb.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCHv7 6/8] printk: use printk_safe buffers in printk
Date: Wed, 1 Feb 2017 12:04:47 -0500 [thread overview]
Message-ID: <20170201120447.5ef79c8f@gandalf.local.home> (raw)
In-Reply-To: <20161227141611.940-7-sergey.senozhatsky@gmail.com>
On Tue, 27 Dec 2016 23:16:09 +0900
Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> Use printk_safe per-CPU buffers in printk recursion-prone blocks:
> -- around logbuf_lock protected sections in vprintk_emit() and
> console_unlock()
> -- around down_trylock_console_sem() and up_console_sem()
>
> Note that this solution addresses deadlocks caused by printk()
> recursive calls only. That is vprintk_emit() and console_unlock().
> The rest will be converted in a followup patch.
>
> Another thing to note is that we now keep lockdep enabled in printk,
> because we are protected against the printk recursion caused by
> lockdep in vprintk_emit() by the printk-safe mechanism - we first
> switch to per-CPU buffers and only then access the deadlock-prone
> locks.
>
> Examples:
>
> 1) printk() from logbuf_lock spin_lock section
>
> Assume the following code:
> printk()
> raw_spin_lock(&logbuf_lock);
> WARN_ON(1);
> raw_spin_unlock(&logbuf_lock);
>
> which now produces:
>
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 366 at kernel/printk/printk.c:1811 vprintk_emit
> CPU: 0 PID: 366 Comm: bash
> Call Trace:
> warn_slowpath_null+0x1d/0x1f
> vprintk_emit+0x1cd/0x438
> vprintk_default+0x1d/0x1f
> printk+0x48/0x50
> [..]
>
> 2) printk() from semaphore sem->lock spin_lock section
>
> Assume the following code
>
> printk()
> console_trylock()
> down_trylock()
> raw_spin_lock_irqsave(&sem->lock, flags);
> WARN_ON(1);
> raw_spin_unlock_irqrestore(&sem->lock, flags);
>
> which now produces:
>
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 363 at kernel/locking/semaphore.c:141 down_trylock
> CPU: 1 PID: 363 Comm: bash
> Call Trace:
> warn_slowpath_null+0x1d/0x1f
> down_trylock+0x3d/0x62
> ? vprintk_emit+0x3f9/0x414
> console_trylock+0x31/0xeb
> vprintk_emit+0x3f9/0x414
> vprintk_default+0x1d/0x1f
> printk+0x48/0x50
> [..]
>
> 3) printk() from console_unlock()
>
> Assume the following code:
>
> printk()
> console_unlock()
> raw_spin_lock(&logbuf_lock);
> WARN_ON(1);
> raw_spin_unlock(&logbuf_lock);
>
> which now produces:
>
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 329 at kernel/printk/printk.c:2384 console_unlock
> CPU: 1 PID: 329 Comm: bash
> Call Trace:
> warn_slowpath_null+0x18/0x1a
> console_unlock+0x12d/0x559
> ? trace_hardirqs_on_caller+0x16d/0x189
> ? trace_hardirqs_on+0xd/0xf
> vprintk_emit+0x363/0x374
> vprintk_default+0x18/0x1a
> printk+0x43/0x4b
> [..]
>
> 4) printk() from try_to_wake_up()
>
> Assume the following code:
>
> printk()
> console_unlock()
> up()
> try_to_wake_up()
> raw_spin_lock_irqsave(&p->pi_lock, flags);
> WARN_ON(1);
> raw_spin_unlock_irqrestore(&p->pi_lock, flags);
>
> which now produces:
>
> ------------[ cut here ]------------
> WARNING: CPU: 3 PID: 363 at kernel/sched/core.c:2028 try_to_wake_up
> CPU: 3 PID: 363 Comm: bash
> Call Trace:
> warn_slowpath_null+0x1d/0x1f
> try_to_wake_up+0x7f/0x4f7
> wake_up_process+0x15/0x17
> __up.isra.0+0x56/0x63
> up+0x32/0x42
> __up_console_sem+0x37/0x55
> console_unlock+0x21e/0x4c2
> vprintk_emit+0x41c/0x462
> vprintk_default+0x1d/0x1f
> printk+0x48/0x50
> [..]
>
> 5) printk() from call_console_drivers()
>
> Assume the following code:
> printk()
> console_unlock()
> call_console_drivers()
> ...
> WARN_ON(1);
>
> which now produces:
>
> ------------[ cut here ]------------
> WARNING: CPU: 2 PID: 305 at kernel/printk/printk.c:1604 call_console_drivers
> CPU: 2 PID: 305 Comm: bash
> Call Trace:
> warn_slowpath_null+0x18/0x1a
> call_console_drivers.isra.6.constprop.16+0x3a/0xb0
> console_unlock+0x471/0x48e
> vprintk_emit+0x1f4/0x206
> vprintk_default+0x18/0x1a
> vprintk_func+0x6e/0x70
> printk+0x3e/0x46
> [..]
>
> 6) unsupported placeholder in printk() format now prints an actual
> warning from vscnprintf(), instead of
> 'BUG: recent printk recursion!'.
>
> ------------[ cut here ]------------
> WARNING: CPU: 5 PID: 337 at lib/vsprintf.c:1900 format_decode
> Please remove unsupported %
> in format string
> CPU: 5 PID: 337 Comm: bash
> Call Trace:
> dump_stack+0x4f/0x65
> __warn+0xc2/0xdd
> warn_slowpath_fmt+0x4b/0x53
> format_decode+0x22c/0x308
> vsnprintf+0x89/0x3b7
> vscnprintf+0xd/0x26
> vprintk_emit+0xb4/0x238
> vprintk_default+0x1d/0x1f
> vprintk_func+0x6c/0x73
> printk+0x43/0x4b
> [..]
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
> ---
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2017-02-01 17:04 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 14:16 [PATCHv7 0/8] printk: use printk_safe to handle printk() recursive calls Sergey Senozhatsky
2016-12-27 14:16 ` [PATCHv7 1/8] printk: use vprintk_func in vprintk() Sergey Senozhatsky
2016-12-27 14:16 ` [PATCHv7 2/8] printk: rename nmi.c and exported api Sergey Senozhatsky
2017-01-04 13:07 ` Petr Mladek
2017-02-01 15:48 ` Steven Rostedt
2017-02-01 15:50 ` Steven Rostedt
2017-02-23 7:50 ` Geert Uytterhoeven
2017-02-23 8:02 ` Sergey Senozhatsky
2017-02-23 9:23 ` Geert Uytterhoeven
2016-12-27 14:16 ` [PATCHv7 3/8] printk: introduce per-cpu safe_print seq buffer Sergey Senozhatsky
2017-01-04 13:31 ` Petr Mladek
2017-01-05 1:01 ` Sergey Senozhatsky
2017-02-01 15:52 ` Steven Rostedt
2016-12-27 14:16 ` [PATCHv7 4/8] printk: always use deferred printk when flush printk_safe lines Sergey Senozhatsky
2017-02-01 16:06 ` Steven Rostedt
2017-02-02 6:05 ` Sergey Senozhatsky
2017-02-02 15:37 ` Petr Mladek
2017-02-02 15:52 ` Petr Mladek
2017-02-03 2:04 ` Sergey Senozhatsky
2017-02-03 11:18 ` Petr Mladek
2017-02-06 1:48 ` Sergey Senozhatsky
2017-02-06 2:08 ` Sergey Senozhatsky
2017-02-06 12:16 ` Petr Mladek
2017-02-06 13:27 ` Steven Rostedt
2017-02-06 16:42 ` Sergey Senozhatsky
2017-02-06 16:55 ` Steven Rostedt
2016-12-27 14:16 ` [PATCHv7 5/8] printk: report lost messages in printk safe/nmi contexts Sergey Senozhatsky
2017-01-04 14:46 ` Petr Mladek
2017-01-05 1:01 ` Sergey Senozhatsky
2017-02-01 16:37 ` Steven Rostedt
2017-02-02 2:02 ` Sergey Senozhatsky
2017-02-02 14:34 ` Steven Rostedt
2017-02-02 16:13 ` Petr Mladek
2017-02-03 1:57 ` Sergey Senozhatsky
2017-02-03 3:13 ` Steven Rostedt
2016-12-27 14:16 ` [PATCHv7 6/8] printk: use printk_safe buffers in printk Sergey Senozhatsky
2017-01-31 17:27 ` Ross Zwisler
2017-02-01 9:06 ` Jan Kara
2017-02-01 9:37 ` Peter Zijlstra
2017-02-01 15:39 ` Petr Mladek
2017-02-01 16:15 ` Peter Zijlstra
2017-02-01 16:41 ` Steven Rostedt
2017-02-02 2:11 ` Sergey Senozhatsky
2017-02-02 9:07 ` Peter Zijlstra
2017-02-02 10:03 ` Sergey Senozhatsky
2017-02-02 15:20 ` Petr Mladek
2017-02-03 2:45 ` Sergey Senozhatsky
2017-02-02 1:59 ` Sergey Senozhatsky
2017-02-01 17:04 ` Steven Rostedt [this message]
2017-02-02 2:13 ` Sergey Senozhatsky
2016-12-27 14:16 ` [PATCHv7 7/8] printk: remove zap_locks() function Sergey Senozhatsky
2016-12-27 14:16 ` [PATCHv7 8/8] printk: convert the rest to printk-safe Sergey Senozhatsky
2017-01-04 16:28 ` Petr Mladek
2017-01-05 1:00 ` Sergey Senozhatsky
2017-01-05 16:58 ` [PATCHv7 0/8] printk: use printk_safe to handle printk() recursive calls Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170201120447.5ef79c8f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=calvinowens@fb.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).