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 0/3] livepatch/stacktrace: Clean up of reliable stacktrace errors
Date: Wed, 24 Apr 2019 10:55:47 +0200 [thread overview]
Message-ID: <20190424085550.29612-1-pmladek@suse.com> (raw)
I ended with three patches in the end. The first one is the same
as before [1]. Then I added two patches for handling of the stacktrace
error messages.
[1] https://lkml.kernel.org/r/20190418112936.13295-1-pmladek@suse.com
Petr Mladek (3):
livepatch: Convert error about unsupported reliable stacktrace into a
warning
stacktrace: Remove superfluous WARN_ONCE() from
save_stack_trace_tsk_reliable()
livepatch: Cleanup message handling in klp_try_switch_task()
kernel/livepatch/core.c | 5 ++---
kernel/livepatch/transition.c | 19 ++++++++++++++-----
kernel/stacktrace.c | 1 -
3 files changed, 16 insertions(+), 9 deletions(-)
--
2.16.4
next 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 Petr Mladek [this message]
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 ` [PATCH 3/3] livepatch: Cleanup message handling in klp_try_switch_task() Petr Mladek
2019-04-24 10:41 ` 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-1-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