From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Petr Mladek <pmladek@suse.com>, Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Calvin Owens <calvinowens@fb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mel Gorman <mgorman@techsingularity.net>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: [RFC][PATCHv2 6/7] printk: report printk recursion from alt_printk flush
Date: Sat, 1 Oct 2016 00:17:57 +0900 [thread overview]
Message-ID: <20160930151758.8965-7-sergey.senozhatsky@gmail.com> (raw)
In-Reply-To: <20160930151758.8965-1-sergey.senozhatsky@gmail.com>
If we end up executing vprintk_alt() then we have a printk
recursion. Set alt_printk_ctx `ALT_PRINTK_RECURSION_MASK' bit
in vprintk_alt() to indicate that recutsion and report the
"BUG: recent printk recursion!" problem later from
__alt_printk_flush().
Example:
BUG: recent printk recursion!
------------[ cut here ]------------
WARNING: CPU: 3 PID: 366 at kernel/printk/printk.c:1803 vprintk_emit+0x139/0x38c
CPU: 3 PID: 366 Comm: bash
Call Trace:
[<ffffffff811be508>] dump_stack+0x4d/0x63
[<ffffffff81039932>] __warn+0xb8/0xd3
[<ffffffff810399b3>] warn_slowpath_null+0x18/0x1a
[<ffffffff8106bfdb>] vprintk_emit+0x139/0x38c
[<ffffffff8106c390>] vprintk_default+0x18/0x1a
[<ffffffff8106d1e6>] vprintk_func+0x65/0x67
[<ffffffff810ab27f>] printk+0x3e/0x46
[..]
[<ffffffff8145fb60>] entry_SYSCALL_64_fastpath+0x13/0x94
---[ end trace ]---
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
---
kernel/printk/alt_printk.c | 9 +++++++++
kernel/printk/internal.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/kernel/printk/alt_printk.c b/kernel/printk/alt_printk.c
index db0bfc8..0010089 100644
--- a/kernel/printk/alt_printk.c
+++ b/kernel/printk/alt_printk.c
@@ -150,6 +150,13 @@ static void __alt_printk_flush(struct irq_work *work)
more:
len = atomic_read(&s->len);
+ if (this_cpu_read(alt_printk_ctx) & ALT_PRINTK_RECURSION_MASK) {
+ const char *msg = "BUG: recent printk recursion!\n";
+
+ this_cpu_and(alt_printk_ctx, ~ALT_PRINTK_RECURSION_MASK);
+ alt_printk_flush_line(msg, strlen(msg));
+ }
+
/*
* This is just a paranoid check that nobody has manipulated
* the buffer an unexpected way. If we printed something then
@@ -290,6 +297,8 @@ static int vprintk_alt(const char *fmt, va_list args)
{
struct alt_printk_seq_buf *s = this_cpu_ptr(&alt_print_seq);
+ /* There is only one way to get here -- a printk recursion. */
+ this_cpu_or(alt_printk_ctx, ALT_PRINTK_RECURSION_MASK);
return alt_printk_log_store(s, fmt, args);
}
diff --git a/kernel/printk/internal.h b/kernel/printk/internal.h
index 6338f5b..403b6ed 100644
--- a/kernel/printk/internal.h
+++ b/kernel/printk/internal.h
@@ -37,6 +37,7 @@ static inline int get_nmi_message_lost(void)
#define ALT_PRINTK_CONTEXT_MASK 0x07ffffff
#define ALT_PRINTK_NMI_CONTEXT_MASK 0x08000000
+#define ALT_PRINTK_RECURSION_MASK 0x10000000
extern raw_spinlock_t logbuf_lock;
--
2.10.0.372.g6fe1b14
next prev parent reply other threads:[~2016-09-30 15:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 15:17 [RFC][PATCHv2 0/7] printk: use alt_printk to handle printk() recursive calls Sergey Senozhatsky
2016-09-30 15:17 ` [RFC][PATCHv2 1/7] printk: use vprintk_func in vprintk() Sergey Senozhatsky
2016-09-30 15:17 ` [RFC][PATCHv2 2/7] printk: rename nmi.c and exported api Sergey Senozhatsky
2016-09-30 15:17 ` [RFC][PATCHv2 3/7] printk: introduce per-cpu alt_print seq buffer Sergey Senozhatsky
2016-10-01 2:24 ` Sergey Senozhatsky
2016-10-06 14:56 ` Petr Mladek
2016-10-07 19:40 ` Sergey Senozhatsky
2016-10-10 11:03 ` Petr Mladek
2016-10-06 13:08 ` Petr Mladek
2016-10-07 19:33 ` Sergey Senozhatsky
2016-09-30 15:17 ` [RFC][PATCHv2 4/7] printk: make alt_printk available when config printk set Sergey Senozhatsky
2016-10-06 15:23 ` Petr Mladek
2016-10-07 19:08 ` Sergey Senozhatsky
2016-09-30 15:17 ` [RFC][PATCHv2 5/7] printk: use alternative printk buffers Sergey Senozhatsky
2016-09-30 15:17 ` Sergey Senozhatsky [this message]
2016-10-06 15:41 ` [RFC][PATCHv2 6/7] printk: report printk recursion from alt_printk flush Petr Mladek
2016-10-07 18:59 ` Sergey Senozhatsky
2016-10-10 11:02 ` Petr Mladek
2016-09-30 15:17 ` [RFC][PATCHv2 7/7] printk: remove zap_locks() function Sergey Senozhatsky
2016-10-06 15:55 ` [RFC][PATCHv2 0/7] printk: use alt_printk to handle printk() recursive calls Petr Mladek
2016-10-07 18:56 ` Sergey Senozhatsky
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=20160930151758.8965-7-sergey.senozhatsky@gmail.com \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=calvinowens@fb.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®