From: Petr Mladek <pmladek@suse.com>
To: Jiri Kosina <jikos@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Miroslav Benes <mbenes@suse.cz>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Petr Mladek <pmladek@suse.com>
Subject: [PATCH 3/3] livepatch: Cleanup message handling in klp_try_switch_task()
Date: Wed, 24 Apr 2019 10:55:50 +0200 [thread overview]
Message-ID: <20190424085550.29612-4-pmladek@suse.com> (raw)
In-Reply-To: <20190424085550.29612-1-pmladek@suse.com>
WARN_ON_ONCE() could not be called safely under rq lock because
of console deadlock issues. Fortunately, simple printk_deferred()
is enough because the warning is printed from a well defined
location and context.
Also klp_try_switch_task() is called under klp_mutex.
Therefore, the buffer for debug messages could be static.
Signed-off-by: Petr Mladek <pmladek@suse.com>
---
kernel/livepatch/transition.c | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/kernel/livepatch/transition.c b/kernel/livepatch/transition.c
index 9c89ae8b337a..e8183d18227f 100644
--- a/kernel/livepatch/transition.c
+++ b/kernel/livepatch/transition.c
@@ -254,6 +254,7 @@ static int klp_check_stack_func(struct klp_func *func,
static int klp_check_stack(struct task_struct *task, char *err_buf)
{
static unsigned long entries[MAX_STACK_ENTRIES];
+ static int enosys_warned;
struct stack_trace trace;
struct klp_object *obj;
struct klp_func *func;
@@ -263,8 +264,16 @@ static int klp_check_stack(struct task_struct *task, char *err_buf)
trace.nr_entries = 0;
trace.max_entries = MAX_STACK_ENTRIES;
trace.entries = entries;
+
ret = save_stack_trace_tsk_reliable(task, &trace);
- WARN_ON_ONCE(ret == -ENOSYS);
+ if (ret == -ENOSYS) {
+ if (!enosys_warned) {
+ printk_deferred(KERN_WARNING "%s: save_stack_trace_tsk_reliable() not supported on this architecture.\n",
+ __func__);
+ enosys_warned = 1;
+ }
+ return ret;
+ }
if (ret) {
snprintf(err_buf, STACK_ERR_BUF_SIZE,
"%s: %s:%d has an unreliable stack\n",
@@ -297,11 +306,11 @@ static int klp_check_stack(struct task_struct *task, char *err_buf)
*/
static bool klp_try_switch_task(struct task_struct *task)
{
+ static char err_buf[STACK_ERR_BUF_SIZE];
struct rq *rq;
struct rq_flags flags;
int ret;
bool success = false;
- char err_buf[STACK_ERR_BUF_SIZE];
err_buf[0] = '\0';
@@ -336,15 +345,15 @@ static bool klp_try_switch_task(struct task_struct *task)
task_rq_unlock(rq, task, &flags);
/*
- * Due to console deadlock issues, pr_debug() can't be used while
- * holding the task rq lock. Instead we have to use a temporary buffer
+ * printk_deferred() need to be used under rq lock to avoid
+ * console deadlock issues. But it does not support the dynamic
+ * debug feature. Instead we have to use a temporary buffer
* and print the debug message after releasing the lock.
*/
if (err_buf[0] != '\0')
pr_debug("%s", err_buf);
return success;
-
}
/*
--
2.16.4
next prev parent reply other threads:[~2019-04-24 8:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 8:55 [PATCH 0/3] livepatch/stacktrace: Clean up of reliable stacktrace errors Petr Mladek
2019-04-24 8:55 ` [PATCH 1/3] livepatch: Convert error about unsupported reliable stacktrace into a warning Petr Mladek
2019-04-24 15:51 ` Josh Poimboeuf
2019-04-24 18:31 ` Miroslav Benes
2019-04-25 3:18 ` Kamalesh Babulal
2019-04-29 14:44 ` Petr Mladek
2019-04-24 8:55 ` [PATCH 2/3] stacktrace: Remove superfluous WARN_ONCE() from save_stack_trace_tsk_reliable() Petr Mladek
2019-04-24 9:07 ` Petr Mladek
2019-04-24 15:50 ` Josh Poimboeuf
2019-04-24 15:51 ` Josh Poimboeuf
2019-04-24 18:35 ` Miroslav Benes
2019-04-25 3:22 ` Kamalesh Babulal
2019-04-24 8:55 ` Petr Mladek [this message]
2019-04-24 10:41 ` [PATCH 3/3] livepatch: Cleanup message handling in klp_try_switch_task() Jiri Kosina
2019-04-24 12:49 ` Petr Mladek
2019-04-24 15:55 ` Josh Poimboeuf
2019-04-24 18:48 ` Miroslav Benes
2019-04-25 3:32 ` Kamalesh Babulal
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=20190424085550.29612-4-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
/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